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

[usdAbc] Relax type-checking on position property and let any float[3] type through. #1115

Merged
merged 3 commits into from
Feb 25, 2020

Conversation

marsupial
Copy link
Contributor

Description of Change(s)

Older Alembics could have been written with .P as a Vec3f or even float[3].

Fixes Issue(s)

Resurrecting old/archived assets should just work with least amount of steps.

@jilliene
Copy link

Filed as internal issue #USD-5867

Copy link
Member

@spiffmon spiffmon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's unfortunate Alembic doesn't give us any other matching options than "strict" or "none", but I guess we can be confident that no tool is writing points as integer or string arrays :-)

Change looks good to me - thanks, @marsupial !

@c64kernal
Copy link
Contributor

@marsupial -- wondering why we didn't update _ReadCurves and _ReadPoints? Just an oversight, or is there a reason to keep the strict matching for those?

@marsupial
Copy link
Contributor Author

No other reason than the asset that triggered this was a mesh only.
Can add the same treatment to those two if you like.

@c64kernal
Copy link
Contributor

Okay great, thanks @marsupial -- no worries, we can take care of it.

@pixar-oss pixar-oss merged commit d2fae87 into PixarAnimationStudios:dev Feb 25, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants