OTOY Forums

neonZorglub wrote:

coilbook wrote:Hi neonZorglub,
here is the scene with 3 itoo cars scattered on 3 platforms. https://wetransfer.com/downloads/edfedc ... 756/a88455
If you just open the scene and go to octane viewport you will see itoo cars are not rendered.
As far as fire particles they worked in octane 4 but since octane 2018 they dont work anymore
All these bugs apply to 2019 version too
Thank you

Hi coilbook,
Thanks for you new scene, I could see the issue.
The cars are not rendered because the new forest pack system discard geometry that is not set as renderable.
> Solution : using the standard 3dsmax Object Properties on the 4 car objects (CITY TRAFFIC 13,16,17,3305), turn on the 'Renderable' check box.

Alternatively
-in Forest object properties (eg for '! A Body Small for A platform', set Display / Render / Mode to Meshes instead of Automatic.
(that would work, but will get a single mesh with all instances, not recommended for memory / performance..)

I'll check the fire particles soon.
For Phoenix FD 4, sorry, no extra feature supported yet, but there was some crashes when using phoenix4..so that is fixed now..
Thanks

coilbook wrote:

neonZorglub wrote:

coilbook wrote:Hi neonZorglub,
here is the scene with 3 itoo cars scattered on 3 platforms. https://wetransfer.com/downloads/edfedc ... 756/a88455
If you just open the scene and go to octane viewport you will see itoo cars are not rendered.
As far as fire particles they worked in octane 4 but since octane 2018 they dont work anymore
All these bugs apply to 2019 version too
Thank you

Hi coilbook,
Thanks for you new scene, I could see the issue.
The cars are not rendered because the new forest pack system discard geometry that is not set as renderable.
> Solution : using the standard 3dsmax Object Properties on the 4 car objects (CITY TRAFFIC 13,16,17,3305), turn on the 'Renderable' check box.

Alternatively
-in Forest object properties (eg for '! A Body Small for A platform', set Display / Render / Mode to Meshes instead of Automatic.
(that would work, but will get a single mesh with all instances, not recommended for memory / performance..)

I'll check the fire particles soon.
For Phoenix FD 4, sorry, no extra feature supported yet, but there was some crashes when using phoenix4..so that is fixed now..
Thanks

Thanks. Hopefully itoo will be fixed (octane 4 renders it fine even if source mesh is set to nonrenderable). I'll try method 1 unfortunately display mesh will kill our performance since we got hundreds of cars.
Two more things:
1. There used to be a problem with multiple phoenix fire grids that was fixed in octane 4. Now it looks like it is back. Two grids each frame take 40-50 sec to process plus no image for 20 sec it just says "rendering". The solution before was to uncheck create fire lights in phoenix rendering settings. Before it would takes seconds to process now it's back to 30-50 sec per frame. Same size sim files. Please also see the video attached. This is just one grid processing and then you will see RENDERING but nothing happens for like 10 sec. Scenes with phoenix and itoo do this a lot now. In octane 4 we never had this problem

UPDATE: Just did a test with 2 phoenix fire grids 1 min to process and 10 sec of black screen where it says rendering
Hiding both grids 1 sec to process and 5 sec of black rendering screen
Each sim per frame for each grid is 250 mb

2. please look into new volume behavior vs old. New one renders smoke too dark


Your solution a long time ago for slow phoenix eval times

viewtopic.php?f=81&t=70453&p=357949&hilit=multiple+phoenix+grids#p357949


"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"