Motion Blur and Proxy and Denoiser Problem

[DKVISION]

Hallo
I have some problems with the denoiser and a moving camera with motion blur. All Vray proxy are randomly from frame to frame totally white or black in the defocus Amount element!
This results in strange blurring of the Vray Proxy objects.
It is quite a mess with ForestPack Pro and RailClone, because they use proxies to scatter objects!
I have attached the max(2019) file!


Windows 10 Pro, Vray Next 1.2
In all max versions 2017,2018,2019,2020

[tashko.zashev]

The issue is reproducible and I'll forward the case to our developers. Thank you for reporting!

[garipodelu]

Any update on this issue? I just experienced this today with forest objects that were using proxy objects.

[garipodelu]

forgot to mention, I am using the latest version of Vray and there were only a few cars animated outside the camera view (from a previous POV). Disabling motion blur did solved the issue.

[tashko.zashev]

It's not resolved yet unfortunately. I see this is a little bit down on the list so I'm gonna rise its priority.

[tashko.zashev]

Another workaround which can be used with the current official builds is to add a Velocity element to the scene. This will create correct Defocus amount element,
However, the issue/bug is already fixed for our internal builds and will be added to one of the next releases when all QA tests are passed.

[garipodelu]

Thanks for the tip Tashko!

[DKVISION]

Thanks, but I had the problem in scenes with animated objects, too!

[DKVISION]

I have a now problem with ForestPack Pro and RailClone. The Defocus Amout is now always at full level for FP and RC Objects with a moving camera and motion bur enabled. Could be a problem from vray or from the proxies from FP or RC!
So defocus is "killing" too much details in for example gras and trees!




Defocus-FP.zip

Max 2019 and Max 2020 Vray Next 3.1
Thanks for the help!
Dietmar

[bf_software]

Any update on this ?, it seems that this 'bug' is still existing in ray 5.00.05 with forest 6.3.1
Only adding a velocity render element 'fixes' this issue but raises others for us, so we can't always use this fix