Motivation

Assemblages made in Assembler can be exported in Unity exploiting modular block structure. The aim is twofold:

to enable a live, first person exploration (even in VR)
to leverage Unity native NavMaps and NavMapAgents for circulation studies

Of course, the entire final geometries of any assemblage can always be manually dumped in Unity as a single asset (you just have to export a mesh as .OBJ or .FBX and use the file as an asset in a Unity project). However, it is possible to exploit the modular and repeated nature of assemblages coming from Assembler inside Unity, paying a price in the initial setup operations but with several advantages:

automated updating for multiple assemblages with the same parts: once the prefabs are created, exploring a new assemblage is only a matter of updating their respective .csv files;
the lightweight nature of prefab instances at playtime: you can enhance the single prefab with details, materials, refined geometry etc. and it will be automatically updated at playtime.

Unity project walkthrough

You should have an installation of Unity - if not, you can get one at https://unity.com. The Unity project in the example files uses Unity 2021.3.4 LTS. If you have a more recent LTS version, it should work anyway without issues. Downgrading to older versions should be possible, but I cannot guarantee 100% success.

Follow the instructions in this page:

Assembler to Unity

<aside> 💡 Fair warning: the entire setup is quite long, due to the time required to set up each unique geometry (at the moment such process cannot be automated - at least not by me). If your part catalog is geometrically stable, the time spent in setup will pay off significantly in easiness of exploring different assemblages with the same catalog of parts.

</aside>

Considerations

The Unity project uses the following custom script to import Rhino Plane data and instantiate prefabs:

https://gist.github.com/ale2x72/4d6b5c36be6379e1992168682fd8b007