Before upgrading to Vray 6 we never had any issues with vrayproxy + modifiers above it + motion blur.
Now, since Vray 6 (and whatever release from it, even nightlies) if we add a modifier above the vrayproxy (for example vraydisplacement) and we have motion blur on, it completely messes with the velocity channel.
For example, we just finished a huge animation project with Vray 6 where we found out that we couldn’t add ANYTHING above the vrayproxy (where we load ALL our animations from other software). We couldn’t even add displacement modifiers (we had to import alembic with the native importer from 3dsmax). This wasn’t an issue before, for years we could edit the contents of the vrayproxy and still have correct motion blur. Now, it’s impossible and it’s a HUGE dealbreaker for us.
We tried this in max 2023, 2022, and several vray builds. We went back to Vray 5 and there’s no issues.
Here’s some ss of the issue. You can try it yourself, just import an abc with some transforms - render, all ok. Add a modifier above, and the result is completely different.
Can you please advise? Is it a known issue?
1st ss - MB after adding a modifier above.
2nd ss - MB without modifier.
3rd ss - vrayproxy settings are pretty much default (just flip axis, anim offset and force first map channel) - completely default settings also give the same result
Any feedback? Is there any way we can contact a developer directly to try and solve this issue ASAP? It completely breaks our pipeline, and i’m amazed how this hasn’t been reported before, since it breaks the vrayproxy usability when using 3dsmax as a scene assembly tool.
Hi, could you send us a scene that reproduces this issue so we can test it? Please upload it through our support contact form. Please include a link to this thread in your message so we can track and handle your issue faster.
Hi again, did you guys start looking into this issue? We got a big project coming up and we’re wondering if use Vray 6 or not, since this is a deal breaker right now.
We are happy to report this has been fixed, and it’s going to be in tomorrow’s nightlies.
The issue was with the way the proxy reacted to modifiers added to it (something it wasn’t originally built for), when an ABC file was loaded (it was ok for vrmesh proxies).
I hear you.
However, you should know it’s done out of the same passion that animates you, if restrained out of courtesy to those working on stuff, and obvious company policy.
If we manage to release what is planned, and you’ll find it underwhelming, i’ll be happy to publicly eat my hat. ^^
It should well have, but you are right, it doesn’t seem to be in there, i just had time to test the same build out.
I’ll update my posts accordingly as i’ll get more news.
So, the build with the fix is surely 31735.
Somehow, it didn’t make in the subsequent stable ones.
The above, however is tested as fixed, please PM me if you need it and don’t have access to it.
I’ll make sure to update the thread for when it’ll be in stables.
It looks like the error was on my end, we don’t have access to the nightlies, but rather to the stable versions. Could i please have access to the nightlies? There’s no 31735 on the stables.
