wasting render time on large scenes

[coilbook]

We are rendering a large scene 5.6 Gb of Vram for animation using 3ds max plugin. We have lots of cars (movable proxies that should be in vram all the time and refresh instantly), itoo forest, and terrain mesh Each frame takes 1 min 56 sec to render (20 video cards). 1 minute for each frame is just a black screen (processing geometry I guess) and 56 sec is to actually render. Why?? The whole scene is in the vram Why are we wasting more than a half of a render time just to process the geometry EACH frame/ Otoy please fix it. Please do some test with lots of instant objects and itoo forests in 3ds max. not sure how brigade demo does it in real time when you have to wait 1-2 min just to process data each frame Thank you

[Tag12345]

We are rendering a large scene 5.6 Gb of Vram for animation using 3ds max plugin. We have lots of cars (movable proxies that should be in vram all the time and refresh instantly), itoo forest, and terrain mesh Each frame takes 1 min 56 sec to render (20 video cards). 1 minute for each frame is just a black screen (processing geometry I guess) and 56 sec is to actually render. Why?? The whole scene is in the vram Why are we wasting more than a half of a render time just to process the geometry EACH frame/ Otoy please fix it. Please do some test with lots of instant objects and itoo forests in 3ds max. not sure how brigade demo does it in real time when you have to wait 1-2 min just to process data each frame Thank you

Read my thread below this. Its kinda going into alot of the issues such as this.


Mainly has to deal with VRAM usage and optimizations within Octane that need to be made either in the post process --> Better usage of CPU & VRAM or --> Better usage with Noise reduction to get times down to compensate for the load time

[bepeg4d]

Hi coilbook,
I wonder how heavy is for 3ds Max itself to handle such a scene.
Did you try to export to Standalone and render from there?
Standalone needs far less resources than a host app + plugin to handle complex scenes, maybe worths to try.
ciao beppe

[KeeWe]

Same here in c4d. as soon as a polyfx deformer kicks in, export time rises over 1 minute for 25 seconds rendering. And the best: its getting longer exponentially. Starting the rendering again reduces the time to 50 seconds, then its goging up 5 seconds per frame. pretty annoying...

[coilbook]

Hi coilbook,
I wonder how heavy is for 3ds Max itself to handle such a scene.
Did you try to export to Standalone and render from there?
Standalone needs far less resources than a host app + plugin to handle complex scenes, maybe worths to try.
ciao beppe

hi we can only use 3ds max because we use madcar and city traffic plugins, phoenix fd etc and exporting all these is such a pain. Hopefully you guys can optimize it like version 2 was. It is getting slower and slower with each version with scene evaluation. With 20 GPUs we have 70% is scene loading every frame

[J.C]

There may be three things to check again:
1. Make sure all moving or deformable objects are "Moving proxies"
2. Animation mode set to "Movable proxies" (if there is one – Blender plugin has this option)
3. Objects that have subdiv/turbosmooth modifiers should be collapsed

Exporting animation to Standalone will not help as in Standalone app there are no "Movable proxies" objects and animation will be processed every frame.

[pegot]

Exporting animation to Standalone will not help as in Standalone app there are no "Movable proxies" objects and animation will be processed every frame.

Can one of the devs confirm if this is true or not? Because I remember a year or two ago doing a complex animation in Belnder that I had to export to Stand Alone. I did various tests in changing the Movable proxies settings for various objects before exporting to SA and recall those settings being honored in SA (i.e when exported with Scatter and or Movable proxy settings the object loading time was substantially quicker than when exporting same objects as Global mesh type).

[J.C]

Check this out:
viewtopic.php?f=114&t=53344&p=268809#p268809

[bepeg4d]

Hi,
i guess it depends from the type of data that needs to be updated during time.
If you have vertex animation in your scene, the geometry exported in Alembic becomes more huge compared to plugin workflow, since the deformed mesh needs to be loaded frame by frame.
With only camera or PSR animation, Standalone is super fast in frame loading.
The recent introduction of FBX support in 3.07 goes in the direction of reducing the loading time also with vertex animation:
viewtopic.php?f=33&t=62395
ciao beppe

[J.C]

Yes, camera or PSR animation work without scene reloading every frame. No special settings are needed for this when exporting to ORBX format. No proxies are needed to setup too.