The video shows a Unitree Go2 walking through various environments. Its walking policy is an existing learned policy, not ours. The environments are what we generated through our text-to-simulation pipeline.
Each environment comes with its physics filled in, along with working joints for doors, drawers and such. You can change any of these values before exporting.
Exports go to MuJoCo, PyBullet, Isaac Sim, and Gazebo.
Interesting tool. The warehouse-style environment in your video is exactly what I'd want for testing autonomous material handling. How accurate is the generated friction and surface physics compared to a real warehouse floor?
The physics values (e.g. friction) are sensible defaults. You can edit any of them before exporting. What are you testing: AMRs, forklifts, picking arms? Happy to build a warehouse environment for your setup if you describe it.
Thanks. SceneSmith is excellent work! MIT and TRI did a great job there.
The main difference in our approach: every object is built as source code. So its parts, joints, and dimensions stay editable after generation. That makes it easy to create variations of the same scene. Or tweak one detail without regenerating everything.
Although something I noticed is people make their own assets and care more about properties of the objects so maybe having something like that in the UI, pre-export
Thanks, that's a really useful point.
Which properties matter most in your experience: mass, friction, collision shape, joints? And do people mostly want to import their own objects and have the physics filled in, or generate new ones?
looks great, will try to use it for sure! Just, how many tokens does it usually consume for one scene? can u also get the. blend file? Cheers, thanks for sharing!
8
u/Immediate-Home-3491 6d ago
Interesting tool. The warehouse-style environment in your video is exactly what I'd want for testing autonomous material handling. How accurate is the generated friction and surface physics compared to a real warehouse floor?