OTOY Forums

The FP render now. But there is a problem with the global settings.
I set it properly in Global Settings but when I load a scene it sets it back to "legacy" support.

This is bad because I batch render scenes regularly. So when I render a bunch of older scenes my forests won't render I guess.

Global Settings should overwrite a setting when I open an old scene because it is "global" and not scene dependent. It would require an additional checkbox like it is done in "Devices" with the "scene dependent" checkbox.

After working with some scenes FP doesn't work on some Forest Objects. I had to revert and same scene was working without hassle.
Strange problem.

Hi Paride,
I guess you got my scene called bug bug bug.zip where itoo cannot be rendered still. Also phoenix fire still cannot render particles.

Do you know when they will release a patch? It's been weeks


UPDATE:
it looks like high poly meshes or distribution method in itoo cause it not to be rendered


Thanks

If i exceed vram octane viewport will crash and max can close. additional ram is added not sure why it would crash. This bug is still not fixed

Hi neonZorglub,

you mentioned in this update "Fixed Forest pack unnecessary update on frame change."

1 . it still takes 30 sec per frame to process static itoo objects like grass, trees. I sent Paride a sample scene a week ago with itoo objects and fly through camera.
in octane 4 you guys fixed it where it took only 1-2 seconds.
it looks like using lots of grass objects 1.7 mil creates slow processing time. But why? It should load all instances in vram once and dont process every frame. Plus cotane 4 had it fixed

2. Another bug in 2019 ver is long RENDERING message after geometry is processed 10-15 seconds. During this time it is a black screen. And it's not like master and slaves are already rendering in the background and an image is not there yet, No nothing is happening for 10-15 sec (usually large scenes or scenes with itoo will do it) I attached the video here

So by the time it processes all this geometry and rendering black screen that 40-45 sec wasted per frame.

Thank you

I've encountered major issues with FP (using the latest version of FP) as well. Max is suddenly hanging in a very bad way.
I went down one version and it's acting a little bit better, but not by much.

I thought it was something else at first (video card drivers, potential viruses, bad scripts, outdated software, etc.) but it seems to be pointing at the newer implementation of Octane.

Hi Paride,
Could you tell me if they will be to fix octane particle modifier for phoenix fire particles? past 4 versions could not render them

Thanks

coilbook wrote:Hi Paride,
Could you tell me if they will be to fix octane particle modifier for phoenix fire particles? past 4 versions could not render them

Thanks

Hi coilbook,
yes, they are adding fire particles modifier.
Regards
Paride

paride4331 wrote:

coilbook wrote:Hi Paride,
Could you tell me if they will be to fix octane particle modifier for phoenix fire particles? past 4 versions could not render them

Thanks

Hi coilbook,
yes, they are adding fire particles modifier.
Regards
Paride

Thanks. Can you tell them to look at new volume behavior. It renders smoke very dark. Even after changing scatter scale and absorp scale. You basically loosing nice light scatter because scale has to be reduce so smoke wont be so dark

I noticed AO dist influences volume too much. If AO is set at 10 (good for large outdoors) volume is almost black even if absorption is set to pure white. Would be nice to have a checkbox where AO dist doesnt influence volumes

Hi coilbook,
didi you check "old volume behavior" option in Kernel panel?
Regards
Paride