Render Job Submission Methods

Before you add the first project, you must decide how you would like to submit a rendering job to Helio. The different methods have different ups and downsides and depend on your production pipeline:

We cover the different methods below.

You can archive your project traditionally by saving the max file and preparing the folder structure. You can learn more about it here.

This process usually has significant downsides, as you need to export textures and plugin data carefully. But some established scripts help you with this process.

With the Helio Plugin / Addon for 3ds max and Blender, you can submit your scene with a few clicks from your favorite DCC tool. Overall: It takes care of most things, and you can define all your settings, e.g., in 3ds max and they are submitted to Helio. This process improves the ease of use and drastically lowers the risk for potential rendering errors.

If you're using Pulze Scene Manager, you can submit your scenes directly out of Pulze to Helio, and Pulze collects all the assets and textures and ensures all used plugins are supported on Helio.

The fastest and most lightweight option is to export your scene as .vrscene or corona standalone file. This comes with some downsides, like more data transfer or not fully supported plugins. But usually, it's the most efficient way to render.