-
Notifications
You must be signed in to change notification settings - Fork 58
Lower severity level for ogre2 visibility mask msgs and unavailable render passes #830
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
Conversation
Signed-off-by: Ian Chen <[email protected]>
Codecov Report
@@ Coverage Diff @@
## ign-rendering6 #830 +/- ##
===============================================
Coverage 79.61% 79.61%
===============================================
Files 146 146
Lines 13444 13445 +1
===============================================
+ Hits 10703 10704 +1
Misses 2741 2741
... and 1 file with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
I've got the same error but on gazebo garden and right after that error I have another one related to camera sensor too:
The simulation keeps working normally. |
The second error msg is correct and lets users know an actual error. Distortion hasn't been ported to ogre2 yet (default render engine used in gz sim) so any distortions that've been specified in SDF are currently not applied to cameras sensors. |
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.
I've also wondered about the RenderPass of typeid 'N2gz9rendering2v714DistortionPassE' is not registered
error. It would be nice if it just said "Distortion is not yet supported in Ogre2" or something to that effect.
ogre2/src/Ogre2Camera.cc
Outdated
<< " are set but will be ignored by ogre2 backend." << std::endl; | ||
ignwarn << "Ogre2Camera::SetVisibilityMask: Mask bits " << std::hex | ||
<< ~Ogre::VisibilityFlags::RESERVED_VISIBILITY_FLAGS << std::dec | ||
<< " are set but will be ignored by ogre2 backend." << std::endl; |
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.
Is it ignored because we don't support these flags yet or for some other reason? If it's the former, it would be nice to mention that.
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.
updated comment to explain that they are ignored because of conflict with internal reserved bits used by ogre2. 5445026
Signed-off-by: Ian Chen <[email protected]>
There should be another msg printed immediately afterwards to say that distortion is not supported in ogre2 here: The difference I see is that one is a warning and the other is an error so the user may not associate that these 2 msgs are related. We could either change this msg in gz-rendering to a warning or the one gz-sensors to an error? |
Do we even need the message with |
if we remove this msg, it's then a silent failure for users of the gz-rendering library (those who are using it without sensors/sim). The render passes (distortion, gaussian noise, etc) register themselves using their |
I see. Ideally, users should be checking that the returned pointer is null and print their own warning/error, but if you think that would be a breaking change, let's not remove it. Perhaps we can just make it a warning then? |
sounds good. I've just made the change in this PR. I'll ticket an issue about printing a more friendly msg. |
🦟 Bug fix
Summary
Currently when gazebo is launched with camera sensors in the scene, it gets scary red error msgs:
[Err] [Ogre2Camera.cc:390] Ogre2Camera::SetVisibilityMask: Mask bits c0000000 are set but will be ignored by ogre2 backend.
This should not be an error but a warning as gz-rendering will continue to work and just ignore the reserved mask bits.
To test
Test with gazebo and check the msgs printed in the console:
The msg should now be an warning istead of error.
Checklist
codecheck
passed (See contributing)Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining
Signed-off-by
messages.