3D assets preparation and specifications

performance and compatibility considerations

RAUM software runs primary on mobile vr hardware with limited system performance in terms of available memory (VRAM) and graphical computation (GPU).

Consider the weakest device of your team when using 3D assets. Therefore, keep your geometry and texture data on the lowest possible file size.

You will find an introduction here.

general preparation recommendations

Collider: Prepare hull objects to offload performance upon physics calculations like collisions, grab and glue areas.

Animations: Transform and joint animation are supported – no constraints. Not supported are blendshape animation

Textures: Minimize the amount of shaders used for your object, ideally to 1. Use PBR textures with a max. resolution of 1k for best look vs performance tradeoff.

Geometry: Avoid many objects within one file. Combine all geometry into one or a few objects to obtain good performance.

Hierarchy: Avoid unnecessary hierarchy and groups. Deep hierarchy causes decreasing performance. keep flatten hierarchies in your models to obtain maximum performance.

Meta Data: Adjust wrong import or behaviour of your uploaded models.

Y or Z up: Change up-orientation of your models coordinate system. RAUM is Y-up, therefore it is likely you need to adjust orientation when importing CAD models.

Pre Scale Factor: Use pre-scale if your models comes e.g. in 1:10 scale. If models are not provided in 1:1 scale or different units, you can use the pre-scale factor to define their real size. RAUM uses meters as unit scale.