Never did that but generally ros3djs seems quite easy when you get used to read the main file.

Let's gonna a try something. Based on https://wiki.ros.org/ros3djs/Tutorials/VisualizingAMarkerTopic :

Do exactly the same, but instead of

var markerClient = new ROS3D.MarkerClient({
  ros : ros,
  tfClient : tfClient,
  topic : '/visualization_marker',
  rootObject : viewer.scene
});

Do:

var markerArrayClient = new ROS3D.MarkerArrayClient({
  ros : ros,
  tfClient : tfClient,
  topicName : '/you_r_name_topic', //check the difference here. instead of topic, topicName
  rootObject : viewer.scene
});

if you want to add an specific mesh:

var markerArrayClient = new ROS3D.MarkerArrayClient({
  ros : ros,
  tfClient : tfClient,
  topicName : '/you_r_name_topic', 
  rootObject : viewer.scene,
  path: 'path_to_mesh'
});

Hi @Solrac3589 I did exactly the same, the line is not displayed on the viewer

  this.tfClient = this._ros.TFClicent({
  angularThres: 0.01,
  transThres: 0.01,
  rate: 5.0,
  fixedFrame: "/base_link",
});

this.markerArrayClient = new ROS3D.MarkerArrayClient({
  ros: this._ros.ros,
  rootObject: this.viewer.scene,
  tfClient: this.tfClient,
  topic: "/trajectory_node_list",
});

Can you tell me is there is any debug information in the browser?

No errors show up in the console, but there's an adjustment in the marker, I just changed the size property to lineWidth to adjust the THREE library, and the sceneNode showed it has children [Marker] which has children [Line], the geometry is correct, have no idea why the viewer didn't display them. This topic is working on Webviz, but it is not working in ros3djs.

Just to be sure. Did you checked in the browser? (not the terminal).

Sometimes my urdf problem not being show was caused by localhost in

var ros = new ROSLIB.Ros({
  url : 'ws://localhost:9090'
});

just try to change localhost by your IP (yes, it does not make sense, but sometimes worked for me).

The websocket is fine, I can see ros3djs generated the markers using the topic, but there's no markers and lines displayed on the viewer. If the websocket url is wrong or not connected, it will print an error message in the console

No idea then, sorry :(

No worries, thanks for helping