Tweet
Hi,
When using animated alembics via vrayproxy and scattered via forest pack (animation mode, follow geo, or random samples) and when using LC as secondary GI, with motion blur on, there's an infinite LC calculation, basically it doesn't go through the first samples pass.
After 2 days trying to debug, i found out that if i import the abc via 3dsmax, there's no issue when rendering. So i assume it's a vrayproxy problem. Not only that but using vrmesh it's a complete pain (ultra slow to export, fails constantly in the render farm due to faulty voxels bug, etc).
Since we do a lot of environments that require animation, this is a huge issue.
In the past this issue was present but then fixed a few years ago, now it seems to be back. I tried several FP versions and several Vray versions, all on 2024. The bug persists.
So right now im in the process of manually converting dozens of abcs instead of vrayproxy to deliver a project.
I feel like VrayProxy (and vrmesh) reallllllyyyy need to be upgraded. It has been super slow for several years and 99% of the bugs we find it's due to it. But since it's an integral part of our workflow, we have to somehow live with it.
When using animated alembics via vrayproxy and scattered via forest pack (animation mode, follow geo, or random samples) and when using LC as secondary GI, with motion blur on, there's an infinite LC calculation, basically it doesn't go through the first samples pass.
After 2 days trying to debug, i found out that if i import the abc via 3dsmax, there's no issue when rendering. So i assume it's a vrayproxy problem. Not only that but using vrmesh it's a complete pain (ultra slow to export, fails constantly in the render farm due to faulty voxels bug, etc).
Since we do a lot of environments that require animation, this is a huge issue.
In the past this issue was present but then fixed a few years ago, now it seems to be back. I tried several FP versions and several Vray versions, all on 2024. The bug persists.
So right now im in the process of manually converting dozens of abcs instead of vrayproxy to deliver a project.
I feel like VrayProxy (and vrmesh) reallllllyyyy need to be upgraded. It has been super slow for several years and 99% of the bugs we find it's due to it. But since it's an integral part of our workflow, we have to somehow live with it.
Comment