there is a big phoenix fd bug that has not been fixed. I think it is related to this post viewtopic.php?f=81&t=64967 or this one where I talk about backup every 15th frame and darkline talked about glitches with phoenix viewtopic.php?f=80&t=67042&start=10
here is the link to the download scene and 2 phoenix sim frames. Also I attached MadCar plugin (once you install it you will be able to play back my animation but cannot drive the car since you dont have a license)
So when you open the file and render it will render the frame 388 but 389 it will get stuck at processing geometry for 30 min. And this happens every 24 frames. You can later resim my grid and render all 200 frames and you will see every 24th frame or so stuck at processing geometry for 30 -40 min. I really dont know what makes octane stuck at processing geometry because of phoenix fd. Thank you .
https://wetransfer.com/downloads/2223f0 ... 227/2f6b29
it looks like the problem happens when the camera is linked to the moving raft. I guess phoenix creates endless ocean in frame 389 and does something that 3ds max is stuck on processing geometry for 30 min and octane cannot process it. When you create another camera (not linked ) it works fine. Hopefully you can fix it.
please also report the problem that darkline had with flickering and wetmaps problem I had in above links all related to the backup intervals .
Looks like when camera moves (camera moves up and down, for example. noise is applied to the camera for stormy feel) it messes with Phoenix OCean making 3ds max stuck at processing geometry. Not just linked camera. Not sure if certain angle of the camera generate a lot of ocean mesh? Ocean subd is only set to 0.8