-
-
Notifications
You must be signed in to change notification settings - Fork 35.5k
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
Blender Exporter: Camera's Y position gets negated. #4207
Comments
In what way is 5.34 a negated value? unless i'm missing something.. ? On Fri, Dec 13, 2013 at 2:52 PM, Kayomarz notifications@github.com wrote:
|
|
I'm a bit out of touch with that exporter. Maybe @joostfaassen knows what the problem is? |
After removing the explicit negative sign on line 2178 it seems ok. I wonder if it's needed in some situation or might be a typo. Line 2178: "position" : generate_vec3([cameraobj.location[0], -cameraobj.location[1], cameraobj.location[2]], data["flipyz"]) |
If you could do a few test and double check that it works, a PR with the fix would then be great :) |
The reason for explicitly negating the value is unknown. Removing the negation seems to work. Making a PR incase you would like to use it. |
The JSON Blender exporter has been removed with Also see: https://threejs.org/docs/#manual/introduction/Loading-3D-models |
Blender exporter seems to negate the value of the
y
position of the camera.Note: This is not related to the
Flip YZ
feature.Apart from this, the exporter works great.
Blender version:
2.69.0 (r60991)
Three.js revision:
63
The property pane of the default blender scene shows the camera position as:
7.48113, -6.50764, 5.34367
Blender exporter exports it as:
7.48113, 6.50764, 5.34367
Following is a snipped of the default blender scene exported using blender exporter. (Note that
Flip YZ
is enabled.)After digging into the python code, line number 2178 shows that the
y
position is explicitly negated.Wondering if there's any reason for negating it or maybe just a typo?
The text was updated successfully, but these errors were encountered: