You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
I'm rendering a moving joint URDF model, a MarkerArray (with 3 moving markers at low speed) together using ros3d in a React interface. The URDF mesh is rendered smoothly but the MarkerArray/Marker object has tangible stuck and frame drops/delay. This is very severe with a high publishing frequency of Marker(we tested at a max of 125Hz), but smoothed a little when publishing at a lower rate (~10-30 Hz).
We didn't find other message types such as Pose and PoseArray to have the same issue, but the rendering is still a little stuck at 125 Hz even for Pose and PoseArray.
Does anyone have the same issue as well?
Library Version: 1.1.0
ROS Version: ros 1 Melodic
Platform / OS: Chrome Version 102.0.5005.61+ Ubuntu 18.04.6 LTS
Setup your backend code such that you are publishing a Marker message type at 125 Hz, change it's position/rotation by a small amount at each publish (i.e. at 125Hz)
At your frontend, setup basic ros3d project, set your tfClient options as following: { angularThres: 0.001, transThres: 0.001, rate: 60.0, fixedFrame: "/base_link", }
Build your backend code and run all the packages above
Open your frontend html
Expected Behavior
The URDF and Marker are rendered
The Marker is moving smoothly without stuck/frame dropped
Actual Behavior
The URDF and Marker are rendered
The Marker is moving with frames dropped and stuck at some time
The text was updated successfully, but these errors were encountered:
Description
I'm rendering a moving joint URDF model, a MarkerArray (with 3 moving markers at low speed) together using ros3d in a React interface. The URDF mesh is rendered smoothly but the MarkerArray/Marker object has tangible stuck and frame drops/delay. This is very severe with a high publishing frequency of Marker(we tested at a max of 125Hz), but smoothed a little when publishing at a lower rate (~10-30 Hz).
We didn't find other message types such as Pose and PoseArray to have the same issue, but the rendering is still a little stuck at 125 Hz even for Pose and PoseArray.
Does anyone have the same issue as well?
Steps To Reproduce
{ angularThres: 0.001, transThres: 0.001, rate: 60.0, fixedFrame: "/base_link", }
Expected Behavior
Actual Behavior
The text was updated successfully, but these errors were encountered: