Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Export lights to dae #228
Export lights to dae #228
Changes from all commits
1fe0fef
76976f1
5e93ad6
0350c58
f6e2f92
1b7602b
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I commented on gazebosim/gz-sim#912 (comment), we should use the light's full
math::Pose3d
and apply a direction on top of that.Now that this has been released, we can't extend this struct though. That's why we prefer full classes with getters and setters using the PIMPL pattern; they involve a lot more boilerplate, but at least they can be extended without breaking ABI.
I think the solution will have to be calculating the
direction
field based on the light's pose orientation together with the light's direction.For directional lights, the position doesn't affect how they light up the scene, but it's often useful to set so we choose where the light's visual representation shows up on the GUI.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for the delayed reply, was pushing some deadlines.
If I may ask, why so? Is there some technical reason?
This struct is specifically used for collada exporting - I tried to make it stick as close as possible to collada specifications. Most notably their
<light>
tag is omitting information on all orientations and direction - meaning that I have to push the transform data to it's parent node that instantiates the light under<node>
.We can usemath::Pose3d
but it's orientation component has it's members set to private as seen here, and in addition there's another problem where the collada specification's<rotate>
tag is not be the same as a quaternion.Reference https://www.khronos.org/files/collada_spec_1_4.pdf, search for
<light>
This does mean if anyone decides to use it for something else they are taking on certain risks. It's something I would expect not many users to be using.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ABI compatibility 😕
I think you may have solved the issue in gazebosim/gz-sim#912 (comment)