-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
[Question] Can visualization markers retain the markers displayed at each step like debug_draw and provide corresponding methods to clear existing markers? #1653
Comments
Thank you for posting this. Could you help us reproduce this issue? could you share the relevant code you are using for this? Thanks. |
Sure.Here is the revised code. The raycaster has been modified, but it should not affect reproduction. The robot has been replaced with Franka. To view from the camera's perspective, you need to hide the ee_marker and finger. The workpiece needs to be replaced with a mesh that includes rigid body and collision properties. If you switch to a rigid object, the visualization effect will not be as good.
|
Question
Currently, I need to visualize at least 60,000 and increasing sphere markers and be able to record RGB information with a camera for reinforcement learning observation.
When using visualization markers, all marker coordinates need to be inputted at each step, and as the number of markers increases, the performance loss becomes greater.
When using debug_draw, only the new marker coordinates need to be inputted at each step, making rendering relatively faster.
However, the visual effect seen through the camera is very poor when using debug_draw.
I didn't quite understand the usage of point instancer in the source code.
The text was updated successfully, but these errors were encountered: