You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When loading a VDB cache that is created in a 25 FPS project and loaded into a 25 FPS file the loaded aiVolume via pipeline remains at the default "velocity scale" of 24.0
Not entirely sure if that as erroneous effects but it seems confusing at least. According to the Arnold docs:
Velocity FPS
Factor which divides the velocity channel values in order to convert from (assumed) units of distance per second to units of distance per frame, as required for shutter times in frame units.
Expected Behavior:
It should match the FPS of the loaded file, and otherwise fall back to the FPS of current task if publish doesn't have any fps data.
The attribute is called velocityFps so it should be along the lines of:
Is there an existing issue for this?
Current Behavior:
When loading a VDB cache that is created in a 25 FPS project and loaded into a 25 FPS file the loaded
aiVolume
via pipeline remains at the default "velocity scale" of 24.0Not entirely sure if that as erroneous effects but it seems confusing at least. According to the Arnold docs:
Expected Behavior:
It should match the FPS of the loaded file, and otherwise fall back to the FPS of current task if publish doesn't have any fps data.
The attribute is called
velocityFps
so it should be along the lines of:Version
1.0.0
What platform you are running on?
Windows
Steps To Reproduce:
Are there any labels you wish to add?
Relevant log output:
No response
Additional context:
No response
The text was updated successfully, but these errors were encountered: