A fork's triage of upstream fixes for the SolidWorks to URDF exporter. One upstream change, the output coordinate system option, merged cleanly and passed tests but failed a live check on SolidWorks 2023: meshes stay in the global frame. Another ported fix had to wait for complete STL files before export.
Recurring agent failure issue in solidworks_urdf_exporter (ycpss91255-research)
What engineers report
A recurring agent failure problem in solidworks_urdf_exporter (ycpss91255-research) that mostly hits the mechanical designer.
Failure pattern: validation / failure
Analyst note
From the Grok pain-radar digests, Nov 10-11 2026 (Nov 10 8:41 AM ET through Nov 11 7:41 AM ET digests plus the Haitch editions). Verified live 2026-11-11: issue/PR read; title and state confirmed.
What it costs a team
Modeled annual cost
$30,000
For a team of 5
Prototype delay
3 days
Modeled schedule slip per occurrence
Time lost
240 min
Per engineer per month, about 1 incidents
How the cost is modeled
240 min/month × 5 engineers × 12 months = 240 hours × $125/hour = $30,000
A modeled estimate with medium confidence. Swap in your own team size and loaded rate to size it for your team.
Engineering tools that address it
No engineering tool profile lists this error yet. Browse tools that connect to solidworks_urdf_exporter (ycpss91255-research).
Evidence
More recurring errors in solidworks_urdf_exporter (ycpss91255-research)
- SolidWorks to URDF to Isaac Sim gives colliders that fill every pocket and a pallet weighing 79 kg instead of 20. The simulator's default collider is a convex hull per mesh, so fork pockets, wheel arches and chassis interiors become solid, mass from solid CAD came out 4x too heavy, and multi-part link inertia was combined wrongly upstream.MCAD · impact 74
- A SolidWorks to URDF exporter writes a robot file pointing at meshes that failed to save, and reports success. The STL and 3DXML save calls only log a warning on error, so the URDF gets mesh filenames anyway and the export dialog finishes normally.MCAD · impact 66
- The SolidWorks to URDF part exporter writes wrong signs for the products of inertia. SolidWorks uses the opposite sign convention, the exporter converts once, rotates the tensor the wrong way round (R I R^T instead of R^T I R), then negates the products a second time. Computed from the exported STL, iyz is +2.01e-8, but the exporter writes -1.99e-8, and the committed example in the repo is wrong too, so robot sims downstream would run on bad dynamics without complaining.MCAD · impact 66
- URDF export settings were one shared attribute, so two configurations of the same assembly could not hold different link trees. Renaming a configuration still orphans its settings.MCAD · impact 66
Sourced from public community reports. Costs and delays are modeled estimates, not measurements. Know a better source or a fix? Tell us at hello@productflo.io.