Hi Bepe,
The scene contains no animation.
Have you done everything possible to reduce the VRAM consumption, optimizing the scene as much as possible?This is not a typical scene, we actually want to highlight problematic geometry. The company I work for (VIMAEC.COM) specializes in super-optimizing the geometry of Revit files for rendering. I'm not sure if you know, but Revit (3d architecture software) exports terrible geometry to 3ds Max and it slows everything down. What we do is completely rebuild this geometry from scratch using 3D modelling best practice. So a FBX export may have 10 million triangles and be unworkable for renders, animation,s VR, AR, etc. Meanwhile that same model would come in around 2-4 million triangles if exported through VIM. We want to show that difference, which means we have to process the bad FBX model as is for comparison.
Here is an example:
VIM import into 3ds Max is 38,301,246 triangles and took 5 minutes to import - Results in a very responsive file
FBX import into 3ds Max is 100,049,099 triangles and took 15 hours to import - Results in unresponsive file
For the materials, I just used a single standard material to override everything as some random elements we transparent.
So far I've not had any issues rendering the VIM files, but the FBX files are such a pain and fail in most situations.
-
I will go through all your comments and try again. I appreciate the knowledge and wisdom!!