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

USD Skel motionblur is inverted #1837

Closed
xsisupport opened this issue Jan 29, 2024 · 5 comments · Fixed by #2045
Closed

USD Skel motionblur is inverted #1837

xsisupport opened this issue Jan 29, 2024 · 5 comments · Fixed by #2045
Labels
bug Something isn't working

Comments

@xsisupport
Copy link

Describe the bug
The motion blur on a USDSkel loaded with the usd procedural does not match the motion blur on an alembic version of the same character (see screenshot below: left is usd, right is alembic)

The right character has - for my eyes - the correct motionblur since the right foot does not move what I can see in the maya UI. This one is created with a aiStandin and an alembic file exported from Houdini.
The left one is created with an aiStandIn and an USD file showing the same frame but the motionblur is somehow inverted. The characters right foot has motionblur even if it does not move.

I checked the alembic and usd in Karma in Houdini and both show the same motionblur which looks like the right character in the image. So I suppose it may be somehow related to the arnold usd procedural.

Screenshots
mb

Used Software Versions

  • Arnold: 7.2.5.1
@xsisupport xsisupport added the bug Something isn't working label Jan 29, 2024
@autodesk-oss-arnold-bot
Copy link

Issue synced internally to ARNOLD-14682

@BigRoy
Copy link
Contributor

BigRoy commented Jan 30, 2024

@xsisupport Are you able to provide the Alembic or USD file for this test?

On the USD one - could it be that the motion blur (velocity) stays the same throughout the whole frame range? E.g. it maybe samples the velocity on e.g. the start frame of the sequence? Could it be that there maybe is velocity data written along with the mesh (accidentally?) that is not timesampled?

@xsisupport
Copy link
Author

mb_problem.zip

@cpichard
Copy link
Collaborator

cpichard commented Aug 2, 2024

It looks like the transform at the intermediate keys is not used, here is an animated gif showing the samples used
motionblur

@cpichard
Copy link
Collaborator

cpichard commented Aug 2, 2024

This happens when the skinned geo is instanced, the procedural seems to use the matrices from the prototypes instead of the current prim. Uninstancing the geo fixes the issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants