I'll forward that to my colleagues working with the robotics group.

I am wondering how it compares to e.g. the QML6 ROS2 plugin ?

I didn't know about it until now. (oops) It's good to see the Creator integration.

But it looks like an imperative dynamically-typed API; we are building a declarative API by generating code at build time from the ROS IDL (msg, ...) files. See this for an example of binding subscriber properties rather than handling messages as they come: https://github.com/ec1oud/qt-presentations/blob/robotics/presentation/simpleSubscriber.qml or this, for some declarative publisher examples: https://github.com/TheQtCompanyRnD/dogzilla/blob/main/dogzillad/qml/main.qml#L25 (although some stuff nearer the bottom of that file still needs work to use more elegant patterns)

But it does look like there have been some different approaches in the actual implementation, and the new module includes a URDF-to-Qt Quick 3D import since that was one key thing we have seen as a blocker for a lot of "digital twin" projects.

That looks pretty neat !
I am wondering how it compares to e.g. the QML6 ROS2 plugin ?