Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maya: Load VDB to Arnold keeps velocity FPS on 24.0 #6

Open
2 tasks done
BigRoy opened this issue Jun 25, 2024 · 0 comments
Open
2 tasks done

Maya: Load VDB to Arnold keeps velocity FPS on 24.0 #6

BigRoy opened this issue Jun 25, 2024 · 0 comments
Labels
type: bug Something isn't working

Comments

@BigRoy
Copy link
Contributor

BigRoy commented Jun 25, 2024

Is there an existing issue for this?

  • I have searched the existing issues

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.0

image

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:

cmds.setAttr(f"{aivolume_shape}.velocityFps", fps)

Version

1.0.0

What platform you are running on?

Windows

Steps To Reproduce:

  1. Load a 25 FPS vdbcache into a 25 FPS project.

Are there any labels you wish to add?

  • I have added the relevant labels to the bug report.

Relevant log output:

No response

Additional context:

No response

@BigRoy BigRoy transferred this issue from ynput/ayon-core Jul 3, 2024
@antirotor antirotor added the type: bug Something isn't working label Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants