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.
Announcement
Collapse
No announcement yet.
BUG* Noise Modifier - Reproducible
Collapse
X
-
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.
anthonyhLast edited by anthonyh; 18-08-2017, 06:08 AM.
Comment
-
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.
Comment
-
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.
Comment
Comment