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

Blender exporter change #4399

Closed
wants to merge 3 commits into from

Conversation

kayomarz
Copy link

@kayomarz kayomarz commented Feb 9, 2014

Blender Exporter: Y position of camera was being explicitly negated, causing incorrect camera pos. The reason for negation was unknown, maybe it was needed in some situation.

See Issue: #4207 (comment)

# Before this fix the Y position of camera was explicitly negated, causing incorrect camera pos. The reason
# for negation was unknown, maybe it was needed in some situation. The old line was:
# "position" : generate_vec3([cameraobj.location[0], -cameraobj.location[1], cameraobj.location[2]], data["flipyz"]),
"position" : generate_vec3([cameraobj.location[0], cameraobj.location[1], cameraobj.location[2]], data["flipyz"]),
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The following is equivalent to the proposed change, no?
generate_vec3( cameraobj.location, data[ "flipyz" ] ),

@kayomarz
Copy link
Author

kayomarz commented Feb 9, 2014

@WestLangley You're right.

Now it's more certain that there must be a valid reason for this negation (It can't be a typo)

Although my app requires this fix, this fix might break some other application. My app uses FlipYZ = false (by keeping FlipYZ un-checked while exporting). I think the more common use is FlipYZ = true.

I wonder if its possible that negation is only required when FlipYZ is true.

I suppose its better to hold this PR until it is known why the negation was done in the first place.

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

Successfully merging this pull request may close these issues.

2 participants