Closed BigRoy closed 4 years ago
@BigRoy This is a known issue which is already tracked internally. Nice analysis about "move -rpr"! We definitely need to fix it.
Tracked as MAYA-99888 internally.
@BigRoy Can you validate, this should be already fixed (and available in dev branch)
OK, I was too quick with this one. You will need to wait for the next update to Maya 2019.
@BigRoy 2019.3 is now available, would you be able to validate and close this? :)
@santosg87 unfortunately I don't think I'll have the time to do this anytime soon. Maybe next week at the earliest. Thanks for pinging me (again) though! :) Will keep it in mind when I find myself with some time on my hands.
Marking this one as closed based on our testing. @BigRoy, feel free to re-open it if it is still a problem for you. :)
Issue
When selecting something from the USD subscene and trying to snap it to regular Maya content, e.g. a locator in the scene. It will perform snapping but will be misaligned. It does not snap using the pivot point but just applies the "translation" of the local scene on top of the original offset of the USD subscene.
For example, when trying to snap a floor tile of the example Kitchen Set it will have a similar distance to the locator as it originally had to the origin. The maya MEL command being issued from the snapping is:
The snapping makes use of the
-rotatePivotRelative
flag which seems to fail to move correctly relative to the rotate pivot but instead just does a regular move like move -300 10 50; which gives the exact same result.Once the
-rotatePivotRelative
flag will work the snapping should start to behave as expected.To reproduce
v
)Note how the snapping behaves very odd.
Specs
d0bb624
)b85ddac
)Mentioned in https://github.com/Autodesk/maya-usd/issues/51