Phoenix multiple grids and eval times Tweet

[coilbook]

Hi paride,
so there is a bug with multiple grids and eval times.
I attached 3 videos to show what the problem is.

1. The first video has 4 grids 2 of them are empty. Eval time is 2 min 50 seconds.

2. The second video. 2 grids with sim data. 2 empty grids are deleted. Eval time is 1 min 30 seconds. Vram usage 1.1 GB

3. The third video. Only one grid with sim data left. Eval time is only 30 seconds. The scene is 0.6.

Even empty phoenix grids contribute to slow down.

Can you please send this to otoy. Can they finally fix this. Thank you

[paride4331]

Hi coilbook,
I just did it.
Regards
Paride

[coilbook]

Hi coilbook,
I just did it.
Regards
Paride

Thanks.
Could you also forward this picture to them maybe it will help. With phoenix present (especially multiple grids) in the scene not only eval times are long between each frame but also GPU2 kicks in that is not even used for rendering and it is a display card only. Not sure why octane uses it since phoenix loads sim from a hard drive.

[neonZorglub]

Hi coilbook,
I'm checking one of the previous scene you sent (overlapping grid.zip), and found that all Fire simulators (PhoenixFDFire001, ..) have the Rendering set to Volumetric mode,
with Volumetric Options /Fire 'Create Fire Lights' enabled.
That creates thousands of Omni lights at evaluation time, and this is very slow, and not used by Octane..
After disabling those, the evaluation time changed from ~6 minutes to 7 seconds ! ..

Can you check if you have such lights enabled in your scene ?

I found some other issues with this scene, that could be related to motion blur sample set to more than 2..
You could try if setting '2' also improves evaluation time ..

If your scene has no Fire lights or is still slow, could you PM it to me ? (I tried some simple empty grids, but couldn't see much slowdown)

Thanks

[coilbook]

Hi coilbook,
I'm checking one of the previous scene you sent (overlapping grid.zip), and found that all Fire simulators (PhoenixFDFire001, ..) have the Rendering set to Volumetric mode,
with Volumetric Options /Fire 'Create Fire Lights' enabled.
That creates thousands of Omni lights at evaluation time, and this is very slow, and not used by Octane..
After disabling those, the evaluation time changed from ~6 minutes to 7 seconds ! ..

Can you check if you have such lights enabled in your scene ?

I found some other issues with this scene, that could be related to motion blur sample set to more than 2..
You could try if setting '2' also improves evaluation time ..

If your scene has no Fire lights or is still slow, could you PM it to me ? (I tried some simple empty grids, but couldn't see much slowdown)

Thanks

Thank you
There is a big difference now!

Should rendering be mode left at Volumetric mode? And will volumetric options ever work with octane to control smoke transparency etc?

Also this incorrect mb still exists viewtopic.php?f=81&t=70717


I will test MB and report shortly. The problem is when grid is attached to a moving object like a train smoke.

Thanks

[paride4331]

Hi coilbook,
I'm checking one of the previous scene you sent (overlapping grid.zip), and found that all Fire simulators (PhoenixFDFire001, ..) have the Rendering set to Volumetric mode,
with Volumetric Options /Fire 'Create Fire Lights' enabled.
That creates thousands of Omni lights at evaluation time, and this is very slow, and not used by Octane..
After disabling those, the evaluation time changed from ~6 minutes to 7 seconds ! ..

Can you check if you have such lights enabled in your scene ?

I found some other issues with this scene, that could be related to motion blur sample set to more than 2..
You could try if setting '2' also improves evaluation time ..

If your scene has no Fire lights or is still slow, could you PM it to me ? (I tried some simple empty grids, but couldn't see much slowdown)

Thanks

Thank you
There is a big difference now!

Should rendering be mode left at Volumetric mode? And will volumetric options ever work with octane to control smoke transparency etc?

Also this incorrect mb still exists viewtopic.php?f=81&t=70717


I will test MB and report shortly. The problem is when grid is attached to a moving object like a train smoke.

Thanks

Hi coilbook,
https://render.otoy.com/forum/viewtopic.php?f=81&t=70717
I asked you in PM to share your scene with me on Mon Feb 18, 2019, you never answered or sent it.
Regards
Paride