Hi,
rendering image with RT GPU and when I do anything with camera, move, change settings, RT still render without any change at all.
And same for CPU version. Cant change depth of field etc. What happend??? ![]()
Hi,
rendering image with RT GPU and when I do anything with camera, move, change settings, RT still render without any change at all.
And same for CPU version. Cant change depth of field etc. What happend??? ![]()
Hmmm…I just tested 2.40.02/Max 2013 with a simple scene in RT/GPU. All camera parameters that I expect to function, did function properly. These included focal length, fov, zoom, f-stop, focus distance, color balance, shutter speed, and ISO. All worked fine and DoF effects appeared responsive and normal.
Perhaps you could post a file to look at?
-Alan
I think I have experienced the same problem today.
Have you tried restarting.?
I have problems with my quadro k4000m card, I get nvidia graphics driver errors using vray RT, with some larger scenes. (100-200 mb)
It starts to render correct, but suddenly it shows wrong pixels in the image and then I need to close the RT.
I can only render simply scenes without any problems. So it is to early for me to invest in a heavy GPU computer..
It needs to be more stable and similar to CPU rendering in quality and features .
If you have your production renderer locked to a specific camera, then the RT engine will stick to that camera, even if you switch to other views.
For the Quadro K4000M, try reducing the ray bundle size and samples per pixel parameters. We had issues with some low-level Kepler cards where the default parameters were too high. I’d say that you need to invest in a better GPU if you plan to use it seriously. Also, from our tests, the quality of the GPU renderer is often the same or better than that of the CPU one, due to it being pure brute force renderer. It is still based on exactly the same algorithms.
Best regards,
Vlado
Yes, I have locked camera view for the first time today
But I realize that so turn it off, but camera movement and all the settings still doesnt respond. And show cropped view when render from camera. When I switched to perspective, cropped view was ok, but still no respond from all the settings. Of course I tried close VRay RT, didnt help. Now I have 3ds max restarted, so I will test it again. But I think this shouldnt happen.
I agree, but I will need some more specific steps how to reproduce the issue.
Best regards,
Vlado
So I test it again and render from camera is still cropped, but seems all settings working.
Interesting, now after few clicks to perspective and back to VRay camera or maybe something else, and computing from VRayCamera is no longer cropped. Good, but dont know why this happend.
AND ONE MORE THINK:
Mix map work with RT GPU, but map Mask not. Is this normal? Maybe yes, just asking ![]()
Now I find out what do the cropp thing in VRay RT with rendering from VRayCamera.
When specify focus is off, its cropped. When turn it on, its ok and look exactly the same as from regular render or viewport. But I think its a bug and should not behave like that.
Thanks for the pointer; will look into it.
I’ll add the Mask map on the “to do” list.
Best regards,
Vlado
Hi Vlado
I did not think a k4000M graphics card is a bad graphics card.
It has 4gb ram and 960 cuda cores.
In my desktop computer I have two geforce 680 cards. But in my Dell laptop (m6700) I have this quadro card.
I did not say it’s a bad one
My laptop has a Quadro 2000M and it seems to work pretty well.
Best regards,
Vlado
Hi Vlado
It helped to turn down the rays per pixel and ray bundle size.
No problem now. ![]()
Martin
Good to know ![]()
Best regards,
Vlado
Thanks Vlado for info.
Look at specify focus bug and please make Mask map work in GPU. Thanks ![]()
Do you have more specific reproduction steps for this?
Best regards,
Vlado
Nothing special actually. Opened an existing scene. Put a vray domelight with EXR and vraycamera in. Turn on DOF and bokeh with 6 blades.
That’s it.
Thanks, we figured it out… it’s not a new issue, but somehow slipped our attention until now. Will fix it, but for the moment, if you turn on the “specify focus” option of the physical camera, it will be fine.
Best regards,
Vlado
So this is fixed now for the next nightly/stable build tomorrow; we will also update on the site a bit later on.
Best regards,
Vlado
Great news, thanks.