Unity Robotics Hub: the docs repository behind Simulation Pro robotics simulation

What Unity Robotics Hub actually is now

The repository describes itself as a central place for tools, tutorials, resources and documentation for robotic simulation in Unity. That framing is accurate but incomplete. The README has been rewritten around Simulation Pro, Unity's newer robotics package, and the older material has been moved aside: the README states that archived content on unsupported packages lives in ARCHIVE.md.

So the audience has narrowed. This is for engineers who already know the Unity Editor and can read and write C#. The README rates the course difficulty as intermediate and says no robotics or ROS 2 experience is assumed, because those concepts are introduced as they come up. If you have never opened Unity, the five-module course is not the entry point you want.

The repository is not a runtime you install into a robot. It is a course, a set of sample assets and a documentation tree. The actual robotics functionality arrives through Simulation Pro, which is installed separately through the Unity Package Manager.

The four capabilities inside Simulation Pro

The README lists four capabilities that Simulation Pro consolidates from what it calls previously disparate features and workflows. First, a URDF importer that provides a drag-and-drop experience for URDF files imported directly into Unity. Second, sensor simulation for Lidar, RGB-D and IMU sensors out of the box. Third, ROS 2 support for communicating with ROS-based hardware directly from Unity. Fourth, a Headless Linux Build Target aimed at parallel simulation across whatever hardware stack you have.

Read that list as a scope statement. The importer handles model ingestion, the sensors generate data, the ROS 2 layer moves messages, and the headless target lets you run many simulations without a display. Everything the course teaches sits inside one of those four buckets. Module 1 imports a Panda arm from URDF. Module 3 configures camera, fisheye, stereo depth, time of flight, three LiDAR implementations and an IMU. Module 4 connects to a live ROS 2 environment. Module 5 exports images, point clouds and CSV logs.

The claim worth noting is the consolidation itself. The README frames Simulation Pro as replacing a set of separate workflows, which implies the older packages each solved a slice of this and did not share a coherent surface. That is a plausible reading of the archive note, but the README does not enumerate what changed at the API level.

Installing Simulation Pro and importing a robot from URDF

The README does not give a command-line install. It says Simulation Pro is installed through the Package Manager and points to Module 1, section 2, for the procedure. The requirements table lists the Unity version as 6.3 or newer, and states that Simulation Pro is supported for production on Unity 6.3 and newer.

Two samples are named as required: Simulation Pro Basic and Prebuilt LiDAR Sensors. Alongside them the course needs the Panda URDF, a material fixer script, an AMR prefab and ROS 2 test files. Those are the assets the modules build on, so a project without them will not match the instructions.

The first concrete outcome is a Unity 6 project with SimPro installed and a Panda arm imported from URDF, configured for stable physics. The README does not document rollback if that import goes wrong, and it does not list a version number for the package itself. Recent tagged releases stop at v0.7.0 from 2022-02-03, so the tags do not track the Simulation Pro line described in the README.

For the ROS 2 half, the course assumes a specific environment: Ubuntu 26.04 with ROS 2 Lyrical Luth on a virtual machine, used in Modules 4 and 5 only. The README is explicit that installing or configuring ROS 2 and the Unity TCP endpoint is out of scope, and that readers who want to run those modules on their own environment should consult the ROS 2 documentation.

ROS 2 messaging, sensors and data capture in the course flow

Module 2 covers nodes, topics, the publisher/subscriber pattern, SimPro message types and TF broadcasting. The stated outcome is a publisher and subscriber exchanging messages over a Dummy Connection, plus transform data broadcast for every joint on the arm. The Dummy Connection is the useful detail here: it lets you validate the messaging layer before any ROS 2 process is involved, which separates wiring mistakes from environment mistakes.

Module 3 is the sensor tour. Camera, fisheye, stereo depth, time of flight, three LiDAR implementations and an IMU, each configured and inspected by hand. Three LiDAR variants is a lot of surface for one module, and the README does not say which one to pick for a given use case. Expect to make that call yourself.

Module 4 is where the pieces meet: simulation time, coordinate systems, the ROS Endpoint Connector and differential drive, ending in a live ROS 2 connection with an rclpy node navigating the robot using LiDAR and odometry. Module 5 exports images, point clouds and CSV logs. The repository includes an example.csv at the top level, which is the only concrete artifact of that export path visible in the file listing.

Work through the modules in order. The README states each one builds on the project state left by the previous module, so skipping ahead means reconstructing state the course never explains.

Where this repository is the wrong tool

The clearest boundary is the Unity version. Simulation Pro is supported for production on Unity 6.3 and newer. If your team is pinned to an earlier Unity release, the supported path in this repository does not exist for you, and the fallback is the archived material the README marks as unsupported packages.

The second boundary is ROS 2 itself. The README states that setting up ROS 2 is out of scope. If you do not already have a working ROS 2 environment, Modules 4 and 5 are not self-contained, and the course will not get you there. The README also assumes a virtual machine running Ubuntu 26.04 with ROS 2 Lyrical Luth, which is a narrow target to reproduce.

The third is licensing and access. Simulation Pro is described as a package with early access open to Unity Industry developers, and the README links to a contact form to register interest. That is a sales conversation, not a package download. If you need something you can pull and run today without talking to anyone, this repository's current recommended path does not offer it.

Finally, the README gives no performance numbers, no supported robot list beyond the Panda arm used in the course, and no guidance on simulation fidelity. Anyone treating it as a validated simulator for control work will need to establish that themselves.

Alternatives and the difference in approach

The most direct alternative for ROS 2 users is Gazebo, which is the simulation tool most ROS 2 tutorials assume. The difference in approach is architectural: Gazebo is a standalone simulator that ROS 2 nodes connect to, while Simulation Pro adds robotics functionality directly to the Unity Editor, as the README puts it. In practice that means your environment is built from Unity prefabs and your scene authoring happens in a game engine with a mature asset pipeline. That is an advantage if your team already ships Unity content and a cost if it does not, since the README rates the course intermediate and assumes C# fluency.

A second alternative is running the robot software against recorded or synthetic data without a full physics scene. That skips the URDF import, the sensor configuration and the headless build target entirely. It is cheaper, and it is the wrong choice the moment you need to change the environment and re-run the same robot code, which is the reason the README gives for simulating in Unity at all.

A third is staying on the archived Unity robotics packages. The README still points to ARCHIVE.md for that content, so the option is acknowledged rather than removed. The trade-off is explicit in the wording: those packages are unsupported.

Maintenance, licensing and what the tags tell you

The repository is not archived, and the last push was on 2026-09-22, so the documentation tree is being touched. The tagged releases tell a different story: v0.7.0 dates from 2022-02-03, v0.6.0 from 2021-10-04 and v0.5.0 from 2021-07-16. Nothing has been tagged since. If you track this repository by release tags, you are tracking a line that stopped four years before the README was rewritten around Simulation Pro.

The licence badge in the README reads Apache-2.0, and the repository metadata reports the licence as NOASSERTION, meaning the automated classifier could not confirm a standard identifier. LICENSE.md is present at the top level, so the text is there to read. Note the split: the repository's own contents are one thing, and Simulation Pro, distributed through the Unity Package Manager under Unity's own terms, is another. The README does not state the licence for Simulation Pro. Check that separately before you build a product around it.

Upgrade cost is dominated by the Unity version. The README ties production support to Unity 6.3 and newer, so an engine upgrade is part of adopting the current path. There is also a Third Party Notices.md at the top level, and a .gitmodules file, which means the repository pulls in external content that carries its own terms.

Editorial conclusion

Adopt Unity Robotics Hub if you already work in the Unity Editor, can read and write C#, and want to follow the five-module course toward a Python node navigating a robot by LiDAR over a live ROS 2 connection. Do not adopt it if you need a supported package on Unity versions older than 6.3, or if you expect the repository itself to install ROS 2 for you, since the README states that setting up ROS 2 is out of scope. Before committing, verify three things: which Unity version you are on, whether Simulation Pro is available to you through the Package Manager or only through the early access registration link, and whether the archived packages under ARCHIVE.md cover the features you need, because the repository states they are unsupported.

Frequently asked questions

Official sources

1. Issues
2. README
3. Releases
4. Unity-Technologies/Unity-Robotics-Hub on GitHub