-
Notifications
You must be signed in to change notification settings - Fork 201
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
EMSUSD-947 units conversion for USD import #3941
Conversation
pierrebai-adsk
commented
Oct 2, 2024
- Add -unit (-unt) option to the import command.
- Document it.
- Add unit option to the job import argument structure.
- Parse the unit option.
- Expose it to Python.
- Add check-box UI to the import UI.
- Add private structure to the import read job class to hold all conversion info.
- Remove old warning about unit conversion not being implemented.
- Refactor the code for up-axis conversion to also handle the units conversion.
- Change prefs for units if requested and needed.
- Add unit tests.
d5db7ef
to
6321743
Compare
6321743
to
887c600
Compare
- Add -unit (-unt) option to the import command. - Document it. - Add unit option to the job import argument structure. - Parse the unit option. - Expose it to Python. - Add check-box UI to the import UI. - Add private structure to the import read job class to hold all conversion info. - Remove old warning about unit conversion not being implemented. - Refactor the code for up-axis conversion to also handle the units conversion. - Change prefs for units if requested and needed. - Add unit tests.
887c600
to
4174814
Compare
@@ -152,6 +152,11 @@ double ConvertMDistanceUnitToUsdGeomLinearUnit(const MDistance::Unit mdistanceUn | |||
MAYAUSD_CORE_PUBLIC | |||
MDistance::Unit ConvertUsdGeomLinearUnitToMDistanceUnit(const double linearUnit); | |||
|
|||
/// Convert the given \p mdistanceYnit into its text representation suitable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
small typo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will be fixed in next PR about units and up-axis in USD stages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. My only concern is with skinned data: Skel and morphers. Specially when importing then re-exporting it (concerned about bone scaling)
Anything specific? You can log issues in Jira if you think something cold be broken. |
I have some bad experiences when implementing the import/export when converting different units. Scaling was the biggest culprit of bad things happening.. Animations wouldn't translate properly due to mesh have different matrices and so on.. Hence why I mentioned scaling in particular.. I guess we'll see with tests.. |