I have 3 computers which have a quadro 1700, 3500 and 4000 in them. I have downloaded the latest drivers for all, but it doesn’t work!
1700 - Is found and activated in the “Select OpenCL devices for V-Ray RT GPU” When I submit a job for DR vray rt server just says waiting for command… then vray stand alone crashes.
3500 - Is not found and is not activate in the “Select OpenCL devices for V-Ray RT GPU” When I submit a job for DR vray rt server just says waiting for command…
4000 - Is found and activated in the “Select OpenCL devices for V-Ray RT GPU” When I submit a job for DR vray rt server just says waiting for command… then vray stand alone crashes.
I tried to find the *.clbin file in the temporary folder for all computers and it doesn’t exist, on WIN XP 64. I am using a trial version 30 days full access of Vray 2.0. Would this cause any problems?
Its all working I had 275.36-Quadro-winxp-64bit-international-whql installed. I installed 270.61-Quadro-winxp-64bit-international-whql and it is all working fine for all 3 cards. Thanks for the help. I guess it is down to the CUDA version being different?
I still seem to be having issues with this, using distributed rendering and the GPU. I hit render and I have excluded my own PC from the rendering. I have set the render to be only 500 samples, I hit render and on the render slave takes ages to start actually doing anything it says new data index is… and it counts up for about 5 minutes and then starts rendering.
But if I set the render to be timed as 3 minutes, the render progress bar starts going and finished after 3 minutes. But the render hasn’t even started, because it takes the render slave at least 5 minutes to start rendering. If I submit the job via Back burner with distributed rendering off, it starts much faster almost instant.
What am I doing wrong? Why does it take so long to get started?
Also tried to render a scene on the Quadro 4000 via back burner and it said new data index is… and it wouldn’t start rendering at all. The render window started but did nothing. I think I made it fall over as the scene was quite heavy, see attached the scene I tried to render.
Any suggestions on this? I also sent the job to the CPU using RT as a production renderer, and it just hangs saying rendering image. The RT server says preparing ray server. It seems scenes like the one above just cant be rendered using RT.
Yeah I have done that, I have even restarted PC and just sent the job straight away to backburner and rendered locally and it just hangs. Is it possible the scene size is just too large?
sometimes we need to start vray rt server by hand to make production render start.
On the main computer , but also on the nodes if you don’t use distributed rendering with RT but Backburner.
Nope, it still just hangs. If I render for x amount of time in active shade it renders fine. But if I use RT as a production renderer and submit over backburner it doesn’t actually get going.
Also I set the max paths per pixel to 10 for active shade and its now on 12 it doesn’t stop. ahhhhhhhh!!
I guess it would be best to email us to vray@chaosgroup.com and schedule an online session with our support guys to try and figure out what’s the problem.
Hey
Just some feedback - I have a Quadro FX 1800 with the latest drivers (Win 7 Ultimate, Vray 2.1). I’m finding that the sometimes the GPU will work roughly 50% of the time (in the same session). If I start activeshade sometimes it will just sit there waiting for image data. Other times it will start rendering straight away. Still other times it will apply the wrong gamma to the GPU, but not the CPU. I’m talking about a very simple test scene here. The problems seem quite random, and essentially makes GPU RT unuseable for production on my system.
Perhaps its an issue with Nvidia drivers as mentioned…
I just tried a completely new scene with just a teapot and it still doesn’t stop at the given value. rendering for 1 minute stops at 54.6 seconds and rendering 500 paths per pixel renders 508. So I now know its not my scene. But my scene still does take an age to load, but then it is a 500mb scene file so maybe it takes a while to get going on the GPU?
Grrr!!! I just added a new PC to the server and Vray RT render server keeps crashing, has same qaudro 4000 with same drivers as the other machines that are working.
It still takes ages for the active shade to start going. Using default settings in Vray RT I just hit render. On the local machine it says waiting for image data for about 5 minutes and on the render slaves the vrayRT server says new data index is and it just keeps counting for about 5 minutes. Then it starts.
So why does this happen and what could be causing the newly added PC/ VrayRT sever to keep crashing? If I can get this working I have 3 Qaudro 4000’s and Quadro 3500 to test but I cant seem to get it all up and running
What driver version do you have on the newer machine? The latest drivers crash with the V-Ray RT OpenCL code; however the 270.x drivers work fine. I know we covered this earlier in the topic, but I just thought I’d ask.
Sorry just read that the driver version is the same. Can you get me the crash dump from the V-Ray RT render server?
It seems to be working now, I just kept re-starting it and it eventually worked, so no idea why it didn’t first time round.
But the Quadro FX 3500 is not working. It has the same 270.61 driver as the others but when you go to select OpenCL devices for V-Ray RT GPU the selection box has no graphics card in it. But I have just looked here http://en.wikipedia.org/wiki/Nvidia\_Quadro and it doesn’t list CUDA cores, perhaps it doesn’t have any
The bench mark scene started straight away using DR but a scene I am testing still takes ages to get started, using same RT settings as the bench mark scene. Its not particularly heavy, couple of cars and a back wall.
I had 275.36-Quadro-winxp-64bit-international-whql installed. I installed 270.61-Quadro-winxp-64bit-international-whql and it is all working fine for all 3 cards. Thanks for the help. I guess it is down to the CUDA version being different?
it doesn’t stop. ahhhhhhhh!!
