-
Notifications
You must be signed in to change notification settings - Fork 466
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
Melodic release #1414
Comments
@simonschmeisser, can you please verify whether the visual regression is due to your #1365? |
it worked after #1387 , will test further but first fix the crash |
So the crash is here:
text_ being 0
|
@v4hn, this issue might be related to your #1275 as well, not defining the text marker anymore if there is some issue (e.g. an empty text?). @simonschmeisser, can you please provide a yaml or rosbag record of your marker message? |
@rhaschke it is indeed due to my commit #1365 , I found that the rviz/src/rviz/ogre_helpers/stl_loader.cpp Line 236 in 6135ee2
will now check if something similar gets set with the assimp code path |
ok, changing the following Line 379 in 325e74c
to
fixes STL coloring, this should of course be dependent on some property of the mesh, not sure which |
as a test-case you could use https://github.com/ros-industrial/fanuc and then run
it should show a bright and friendly orange instead of the gloom dark one |
about the crash, it appears that Also the name |
Would be great, of course, if you could figure out this. Regarding the crash, @v4hn introduced this white-space-only check in #1275, because they noticed Ogre would crash with such text. Thus, setting an empty text should delete the marker on an update. |
I'll try to investigate sometime later this week what's the difference between a collada mesh and a stl mesh after it has been parsed by assimp. Alternatively we could copy the old behavior and set the material based on file extension |
There are two parts to the coloring issue:
So it appears we need to do some magic based on file extensions? |
Release prepared: ros/rosdistro#22320 |
I would like to prepare a new release into Melodic asap. However, because there are many new commits, I would like to get some feedback from the community first to resolve potential regressions. Particularly, @wjwwood, @simonschmeisser, @VictorLamoine, @v4hn could you please use the
melodic-devel
branch on a daily basis and report (new) issues?The text was updated successfully, but these errors were encountered: