While trying to render over a network with 2 nodes, I’ve found a bug with the noise modifier in 3dsmax. When I animate the noise over time, it doesn’t animate a smooth motion, but skips around as if the noise suddendly jumps to a different phase. This only happens in the rendered sequence and not the viewport. I’ll include an example here.
VrayBugTest_20170818_V01_LP.zip (57.4 KB)
This also happens when animating the Phase of a Noise Map in 3dsmax for a Displacement modifier. The phase skips all over in the rendered images.
hi,
without testing, it`s not in world coordinates rather than object ?
just a guess.
anthonyh
I’m not sure how it’s possible to apply the Noise modifier in world coordinates. Although the displacement version I tested (with animated noise map) was not in world.
sorry, i thought you meant a noise map, you said modifier.
I`ve tested through backburner 2016 and (2018 locally only) and it`s fine. Unfortunately I`ve not got 2017 to test so maybe someone else can test.
have both machines got the same service pack ? i doubt it`s that but you never know.
anthonyh
All machines are identical with newest Vray and 3dsmax 2017 on Win 7 Pro with latest service pack and Nvidia driver 376.33 (one of the recommended for VRay GPU). I haven’t been able to find a solution yet.
Can any devs please check to verify this? This also is happening in general with animated sequences. I’ve currently rendered a sequence with a rigged/skinned character and the renders are causing the model to jump all over the place. I’m going to downgrade back to a stable 3.5 and will report on the results.
Returning to 3.504 and rerendering the same sequence worked as expected. It seems there are problems with the current version of Vray and my OS/Hardware/Network setup.
Hi,
You are rendering with RT actually. Allright, the issue is reproducible with the latest 3.6 builds and I’m going to log it in our system. Thank you for this report.
Is there an ETA on when this will be fixed? Going through the nightlies readme I wasn’t able to find it listed. It’s quite a crippling bug for network use of RT and as such is holding us off from upgrading (back) to 3.6.
We don’t have an ETA on a fix yet, sorry. We’ll update this thread when we have any news.
After updating all systems to 3dsmax 2018 with the latest Vray, this problem continues to occur. Particle Flow and various modifiers (ie. FFBox, Noise, Displace, etc.) are causing discrepencies between the renders of our render nodes. Is there anyone else using the latest 2017-2018 3dsmax and Vray to render animations with RT over a GPU network? Is this problem only on the side of Vray or does it have something to do with our setup? Is this problem going to be addressed sometime soon as it’s now been almost 3 months since it’s been logged.
This is fixed in the Beta.
Will it be fixed in the official 3.6(or higher) or is it only planned for Vray Next?
We will try to add it to 3.x, too. It’s already in the released V-Ray Next 1.
It’s in the stable 3.6 nightlies.
Thanks, I’ll do some testing in the next days/weeks.
First test has given an error. The scene was already rendered in 3.5, now in 3.6 stable nightlies over Backburner on a network with this:
3dsmax adapter error: Autodesk 20.3 reported error: [V-Ray] ./src/ocl_tracedevice.cpp(2041) : CUDA error 999 :an unknown internal error has occured
I’ve reverted back down to 3.5 and it renders fine. Haven’t had time yet to troubleshoot.
You can always send it to me.
Unfortunately, I am not allowed to send this project. Although upon testing my original test file here, there is still another BUG in the latest stable. When rendering a sequence through the network, the file is not able to save. This happens because Vray is trying to save the sequential naming (Filename.0001.exr, Filename.0002.exr, etc.) along with an extra Filename.exr. Although the Filename.exr is redundant. So when 2 render nodes are trying to save the Filename.exr at the same time, an error occurs and it cannot write the file. Why is this redundant file being saved out for every frame? This does not happen with version 3.5.