@kwistenbiebel said:
In some cases it could be a benefit that export would be done in phases, in 'chunks', so the RAM can be cleared somewhere in between. The generated mesh .xml files could automatically be merged into one geometry file.
I don't know if what I describe is possible.....
What we would do is write the geometry to a file - this is what exporters like KT do - and then read the file with a separate process. So the RAM usage during export would be minimal.
However, we want to make sure that the two processes are communicating. For instance if we change brightness settings in the render window, we want to remember those settings in SketchUp so we can reuse them.
Or, If you change the view or some other setting - like sun brightness - in SketchUp you would like to modify the rendering without saving and reloading the geometry.
We are researching the best way to have two separate processes be aware of each other and communicate, and then we will run some tests - such as exporting a large model to a file - to see if it will be of value to separate the processes.
(But this thread is not just about rendering - we have similar problems in our export to 3D PDF application, in our Component Reporting application, etc.)