-
Notifications
You must be signed in to change notification settings - Fork 274
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
Positioning external .obj 3D objects on Marker #8
Comments
There is also a setup for multiple markers which takes the current camera rotation translation and calculates the markers world position and translation instead of changing the camera rotation and translation. so the marker will be placed in the world instead of being the center of the world. maybe this code might help you? Try to use only the rotation or only the position for the object to figure out which one is the problem. |
Thanks for your reply. Meanwhile, I tried scaling down the object to about 5% of its current size in all dimensions and it seemed to do the trick. Seems like the camera was getting placed inside the object because of its size. The 3D object was prepared in Blender and exported as a .obj file. I will try out your suggestion about the multiple marker setup and share the results. |
Sounds good :) If you want also share some screenshots ;) On Fri, Jul 5, 2013 at 12:01 PM, bharatparikh [email protected]:
|
I am using ModelLoaderAdapter, ARMarker along with DroidAR to load external .obj models. The model is loaded fine long with its texture but is not positioned on the Marker. Loading a simple cube positions it fine on the Marker but in the same code when I replace the cube with a .obj model the positioning goes off. I tried manually positioning the object by creating a Vec() object for position and rotation but couldn't position it correctly on the Marker (also not sure if this is the correct way to do it).
Following is a snippet of code being used (trimmed for brevity):
What is that I am doing wrong here? Please help.
The text was updated successfully, but these errors were encountered: