Motion blur vray volume grid

[joshclos]

I'm on an older version of phoenix at the moment (3.04) and vray 3.60.04 and it looks like the VrayVolumeGrid doesn't render motion blur. I'm using .aur and when I switched to a phoenix container, it works again. Anyone else experience this?

For now I can just use the phoenix containers but it's a bit tricky because I'm in a scene with like 30 containers and it hangs for a moment each time I select one (presumably the license check). Just a very minor setback is all.

[joshclos]

(Perhaps I should post in vray because this may not be a phoenix related problem)

[Svetlin.Nikolov]

Hey, if it's the VolumeGrid, this is the right place

Are you using the official 3.60.04 or a stable nightly and which revision if that is the case? The AUR format was changed a few months ago, so newly simulated caches might not open correctly with an older V-Ray, but the latest V-Ray stable nigtlies are compatible with them as well.

nikola.bozhinov , maybe we can show a warning message in this case?

In case you are already using a V-Ray stable nightly from a couple of weeks back, then would it be possible to send over the scene with the V-Ray settings as they are, one container and one cache file?

Cheers!

[nikola.bozhinov]

Hi,

These changes in the AUR file format were first added to Phoenix FD in the end of January and have first appeared in nightlies on January 30 2018 (with small fixes being added throughout the first week of February), which is 3.05 nightly and were integrated into the stable nightlies of V-Ray 3.6 in the end of February. So if the caches were simulated (or are being rendered fine) with Phoenix FD 3.04, then the problem is not in the AUR format.

Builds after the changes will open files in the older format without problems, so there is no need for a warning. However doing the opposite - opening newer cache files with an older build may cause much bigger problems and even crashes. Unfortunately there is no way for us to fix already released builds.

[joshclos]

Hey Svetlin,

Yep, the particular studio I'm with at the moment doesn't use nightlies due to their large pipeline so it's the official 3.60.04. I wish I could send over a scene and cache but we cannot remove any files from the network here (they're very strict). They are planning to update to phoenix 3.1 in a few days and at that point I'll do another sim and try the volume grid motion blur again and report back with my results. I can also test it at home with 3.1 to double check.

Thanks for such quick replies and assistance!

[Svetlin.Nikolov]

Roger that, please ping us if with a latest build it's still not okay...

Cheers!