ros-sharp VS ROSIntegration

User_App_ROS_UnitySimulationExample · siemens/ros-sharp Wiki (github.com)

RosSharp looks like can handle the visualization in Unity: https://github.com/siemens/ros-sharp/tree/master/Unity3D/Assets/RosSharp/Scripts/RosBridgeClient/SensorDataVisualization

For ROS1 - check out https://github.com/siemens/ros-sharp

The Microsoft ROS Landing page includes setup instructions for ROS natively on Windows. Additionally, if you are writing a Windows application, you can use ROS#, which includes .net bindings for ROS using the ROS Bridge.

The tools in the Unity Robotics Hub provide a URDF importer (derived from ROS# https://github.com/siemens/ros-sharp) and a low level TCP communications bridge to ROS.

There are several ways of using Unity for robotics. Robotics for Unity is a new field and support is still custom made. Most of the applications out there are proprietary software created by private companies and not easily accessible or configurable by others. ROS support has been recently introduced by Unity itself, and it is a fork from a previous library from Siemens' RosSharp. In my setup, I used the Unity ROS library which works with the latest ArticulationBody types.

I've recently been working with ROSIntegration, does anyone have any examples of it's use? My publishers haven't been working as well as expected.

I've been trying to publish controller locations from an Oculus device to a Baxter running ROS Kinetic. While I found a decent plugin that seems to work on a basic level, the subscriber isn't reading it correctly. Is anyone familiar with ROSIntegration? Even just some examples of functional code using that plugin would be very helpful.

I would say this still depends on your use-case. Unity provides potentially high visual fidelity for image based learning etc. (like Unreal, for which there is this: https://github.com/code-iai/ROSIntegration ). The physics engine may be a bit simpler than in dedicated simulators to keep real-time > 60Hz up. (Unreal also uses PhysX)