Hello Chaos Team !
Here at Capsule Studio we recently move our pipeline of Point Cached asset to Alembic cache. To load those cache we used VrayProxies because it contains all ancestors (in opposite of 3dsmax Alembic loader) so if one object is cached to disk, one object is loaded. But during the last project we have faced a really annoying issue :
If the motion blur is activated on the Physical Camera and the VrayDisplacementMod is activated on the object it produce at rendertime some big articfacts (it's not always the case).
I've made a video to explain the problem (with a side by side with the 3dsmax alembic container) and a test scene for you to spot the issue :
https://drive.google.com/file/d/1SJB...usp=share_link
And here is the test scene to reproduce the issue :
https://drive.google.com/file/d/1r-8...usp=share_link
Hope you'll find the issue because the vrayproxy abc loader is great and we really need it in our pipeline.
Using : 3dsmax 2023.1 and Vray 5 update 2.3
Thanks.
Here at Capsule Studio we recently move our pipeline of Point Cached asset to Alembic cache. To load those cache we used VrayProxies because it contains all ancestors (in opposite of 3dsmax Alembic loader) so if one object is cached to disk, one object is loaded. But during the last project we have faced a really annoying issue :
If the motion blur is activated on the Physical Camera and the VrayDisplacementMod is activated on the object it produce at rendertime some big articfacts (it's not always the case).
I've made a video to explain the problem (with a side by side with the 3dsmax alembic container) and a test scene for you to spot the issue :
https://drive.google.com/file/d/1SJB...usp=share_link
And here is the test scene to reproduce the issue :
https://drive.google.com/file/d/1r-8...usp=share_link
Hope you'll find the issue because the vrayproxy abc loader is great and we really need it in our pipeline.
Using : 3dsmax 2023.1 and Vray 5 update 2.3
Thanks.
Comment