-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Can't not display compressed RGB/Depth in RViz #3111
Comments
I just found that when I monitor the FPS with |
Hi @pengzhenghao It is not a dumb question at all, so don't worry. :) Does it make a positive difference to FPS if you set RViz to use compressed data in the 'Create visualization' settings, as described at #1903 (comment) |
As you are using a router and a network connection, are you using wireless wi-fi communication instead of a wired connection to the router? If you are on wi-fi, IntelRealSense/librealsense#10730 (comment) has advice. It also refers to how nearby wireless devices such as a wireless mouse can negatively impact performance. |
Hi @pengzhenghao Do you require further assistance with this case, please? Thanks! |
Case closed due to no further comments received. |
Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):
All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)
Issue Description
<Describe your issue / question / feature request / etc..>
Hi, I want to display the compressed RGB stream in RViz and it says:
Expecting Camera Info on topic [/camera/depth/image_rect_raw/camera_info]. No CameraInfo received. Topic may not exist.
But I found that the camera info is already there.
I can display the video stream with raw, but not compressed. If using raw video stream, the fluency seems to be identical to the image stream. Is there any recommandation way to visualize? Thanks!
The text was updated successfully, but these errors were encountered: