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

obj-Mesh orientations in rock-roboviz #9

Closed
hwiedPro opened this issue Feb 2, 2023 · 1 comment
Closed

obj-Mesh orientations in rock-roboviz #9

hwiedPro opened this issue Feb 2, 2023 · 1 comment

Comments

@hwiedPro
Copy link

hwiedPro commented Feb 2, 2023

This is a link to this issue: rock-simulation/mars#129

Because it also applies here.

ToDo: Review the mesh import orientations for obj

Explanation
Obj mesh orientations are interpreted unintuitively, I guess this comes from the old default how they were exported from blender by default and thus were handled in MARS.

I had a look in the behaviour of pyBullet, Gazebo, rock-roboviz and MARS using the doc/a test model.

Test procedure for pyBullet and MARS:
I created a simple urdf with a single obj-mesh which represents a coordinate frame, and this was exported with z is up x is forward.

The results:

  • Gazebo uses a right-hand coordinate system where +Z is up (vertical), +X is forward (into the screen), and +Y is to the left. (see GAZEBO Docs) (complies with stl)
  • pyBullet uses a right-hand coordinate system where +Z is up (vertical), +X is forward (into the screen), and +Y is to the left. (tested) (complies with stl)
  • MARS messes with the mesh rotation: Importing the mentioned test-urdf, the obj is placed with the x axis facing in -z, the z axis facing in x and y facing y
  • Rock-roboviz does the same as mars

This issue is somehow related to #98

I suggest for MARS adding the orientation info how the obj-meshes should be parsed in SMURF.

@hwiedPro
Copy link
Author

hwiedPro commented Feb 2, 2023

Will close this for further research on this topic and reopen later.

@hwiedPro hwiedPro closed this as not planned Won't fix, can't repro, duplicate, stale Feb 2, 2023
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

No branches or pull requests

1 participant