Hi everyone! 
LinkForge v1.3.0 was just released! But more than a release announcement, I want to take a moment to share the bigger vision of where this project is going — because it’s grown far beyond a Blender plugin.
The Vision
LinkForge is not just a URDF exporter for Blender. The architecture is intentionally built as a Hexagonal Core, fully decoupled from any single 3D host or output format.
The mission is simple:
Bridge the gap between creative 3D design and high-fidelity robotics engineering.
Design Systems (Blender, FreeCAD, Fusion 360) ➜ LinkForge Core ➜ Simulation & Production (ROS 2, MuJoCo, Gazebo, Isaac Sim)
Because in robotics, Physics is Truth. Every inertia tensor, every joint limit, every sensor placement should be mathematically correct before it ever reaches a simulator.
What’s New in v1.3.0?
Performance
-
Depsgraph caching and NumPy-accelerated inertia calculations for large robots
-
Formal Kinematic Graph engine for cycle detection and topology validation
ros2_control Intelligence
-
Joint sync, XACRO modularity improvements, and 100% core test coverage for the control pipeline
-
ros2_controlhardware interfaces now auto-generated from the dashboard with enhanced joint model (safety/calibration support)
Key Bug Fixes
-
Resolved XACRO import failures for
ros2-style robot descriptions (e.g.,$(find pkg)/...macro resolution) -
Robust mesh import cleanup and improved XACRO empty-placeholder pruning
Component Search
- Added a component search filter to the component browser — makes large, multi-link robots much easier to navigate
Looking for Contributors
The upcoming roadmap includes SRDF Support, the linkforge_ros package, and a Composer API for modular robot assemblies.
If you work in ROS 2, enjoy Python or Rust, or have ideas on how to improve the URDF/XACRO workflow, come say hi:
What is your biggest URDF/XACRO pain point today? I’d love to know what the community needs most as we plan the next milestone! 
