@MetalGlass : The scene is not really heavy for the computer when I work with Blender. The main reason that pushes me to render with Octane Standalone, instead of Cycles or even Octane pluging within Blender is that at rendering time, only the render engine is running.
It requires much RAM to manage data before filling the GPUs Vram (This process is called voxelization) but very few CPU ressources.
My scene is modular : each big object in Blender is exported separately in OBJ format with a specific exporter for Octane. All complex objects that are repeated several times are exported as instances and declared in a scatter file (.csv) Objects and scatter files are seen as nodes in a peculiar node tree structure in Octane (very powerful vertical tree structure that is much more friendly and intuitive than Blender/Cycles nodes).
So, heavy scenes in Blender can be made of many independent files that can be exported in OBJ and gathered and assembled in Octane. These objects, once their materials are set up in Octane can be exported in orbx format to be reused in other Octane scenes !
Currently, with 4 cars, the scene weights 1950.9 MB in Octane and is composed of 7 586 825 triangles. Including instanced objects, the scene contains 261356 objects.
@Speed777777: Hi Shaun, I checked my brick Template, and you were right, it is a bit too big. I am currently remapping. It looks a bit weird to me as i was already used to bigger bricks…