VERY slow processing geometry and Phoenix Ocean Tweet

[coilbook]

Hi Paridie,
could you look at this scene and render the animation. When subdivision level is set to like 4-5 render times get very very slow mostly because of initial geometry processing every frame. is this how octane does and nothing can be done?

If you can just simulate 50 frames and then render you will see slow processing times Thanks

Anyway future octane versions will start processing next frame while rendering of the first frame is happening? So we get instant rendering next frame?

Thanks

[coilbook]

1. Here is another example. Changing waves height in phoenix ocean map changes wave displacement making scene go from 1.3 gb to 5.8gb but why load time go up so much. Almost 3 min to load 6Gb of mesh to the vram? why so slow

2. 400,000 foam particles it gets even slower to load from 26 seconds to 50 because we dont have good procedural foam

3. Also selecting phoenix ocean and enabling motion blur on water (vertex mb with movable proxy) makes loading time go from 26 seconds to 1:27