Simulon Asset Pipeline

Your asset is processed to create proxy variants for mobile while keeping your original upload intact.

When you upload an asset to Simulon, our backend does two important things:

1. It generates a proxy version of your asset which is optimised for running on mobile.

2. It prepares your original asset for rendering in the Simulon render farm.

Auto-Generated Proxy

Simulon's proxy generation process two major things:

1. It scales all your textures to a size suitable for running on mobile.

2. It decimates your asset to reduce the amount of polygons that are needed to be rendered on mobile.

In most cases the auto-proxy generation should give satisfactory results for mobile, however in some cases a custom proxy may want to be used to apply more bespoke optimisation to your asset.

Custom Proxies

The Blender asset prep workflow gives you the ability to decide what is included and not included in the proxy version that is used on mobile. It also allows you to create bespoke proxy assets if the Simulon auto-proxy decimation is not as accurate.

Note

Simulon will still apply decimation to your proxy assets if over 150000 triangles to ensure a smooth mobile experience when using the asset.

In the Blender outliner when an object or collection is "Disabled in Viewport" (the pc monitor icon), it will be omitted from the proxy. If an object or collection is "Disabled in Render" (the camera icon) it will be omitted from the final render.

This gives creator control over what they see in mobile vs what they see in the final render. This can be especially useful for things such as complex simulations or animations that don't need to be rendered on mobile for you to capture the take correctly.