OTOY Forums

coilbook wrote:

paride4331 wrote:Hi coilbook,
MB seems to work with mesher too. Maybe I'm wrong about your issue, could you share your test?
Regards
Paride

HI Paride
here is the scene with wrong mb direction Thank you

it seems when saw moves horizontally sometimes it works sometimes it does not. Sometimes pflow works and mesher does not .

Also some frames it works and some frames it does not. Frame 371 it works and frame 372 it does not. Delete operator messes with pflow

Hi coilbook,
try to uncheck "disable Pflow mesh istances"
Octane Global Preferences > Pflow >
Regards
Paride

coilbook wrote:Hi Paride
could you tell otoy about slow load times of multiple phoenix grids. Thank you

Yes I did it.
Regards
Paride

paride4331 wrote:

coilbook wrote:

paride4331 wrote:Hi coilbook,
MB seems to work with mesher too. Maybe I'm wrong about your issue, could you share your test?
Regards
Paride

HI Paride
here is the scene with wrong mb direction Thank you

it seems when saw moves horizontally sometimes it works sometimes it does not. Sometimes pflow works and mesher does not .

Also some frames it works and some frames it does not. Frame 371 it works and frame 372 it does not. Delete operator messes with pflow

Hi coilbook,
try to uncheck "disable Pflow mesh istances"
Octane Global Preferences > Pflow >
Regards
Paride

Hi Paride
All those examples were made with pflow mesh instances already disabled. So it looks like a bug

Hi coilbook,
I do not understand, here it seems to work..

Regards
paride

paride4331 wrote:Hi coilbook,
I do not understand, here it seems to work..

Regards
paride

Hi Paride
I am sorry we had this option checked. Looks like it works with it unchecked but now all our sparks are way brighter and the reason we had it checked is slow evaluation times. Not sure if 4.40 version fixed slow eval times


Also cam they rename this button as ENABLE pflow mesh instances. That way when it is checked it is ON. Right now when it is checked it is OFF confusing



versiom 4.39

"by neonZorglub » Thu Aug 10, 2017 1:32 am



The issue comes from the new PFlow instance support
>> Please select 'Disable PFlow mesh Instances' in the Trouble shooting tab of Global Preferences <<
That should bring back the evaluation time to normal !
We currently need to parse the scene a first time (which is slow when you have many meshes..) for this PFlow instance system..
If you don't use PFlow, you should definitely disable this ..
If you use PFlow, it should still be highly beneficial to enable it, but might depend on number of particles vs non-pflow meshe count ..

Thanks

neonZorglub
OctaneRender Team
OctaneRender Team

Posts: 63
Joined: Sun Jul 31, 2016 10:08 pm

Top
"

This is about rendering phoenix fire particles. we have three logs that crashed and created sparks. Octane does not render sparks from all 3 logs. Instead, it chooses if it is a beam 1,2 or 3 depending on group index. It is just 1 grid. Why cannot it render sparks from all 3 beams.

UPDATE:

we added multiple octaneparticle modifiers and it works. I guess if you have 10 beams you will need 10 modifiers with group index 0-9. Can otoy for fire sparks make all particles renderable without having more than 1 octaneparticle modifier?

Another bug. WHen disable pflow mesh instances is unchecked it is not rendering animation. pflow is static

coilbook wrote:

paride4331 wrote:Hi coilbook,
MB seems to work with mesher too. Maybe I'm wrong about your issue, could you share your test?
Regards
Paride

HI Paride
here is the scene with wrong mb direction Thank you

it seems when saw moves horizontally sometimes it works sometimes it does not. Sometimes pflow works and mesher does not .

Also some frames it works and some frames it does not. Frame 371 it works and frame 372 it does not. Delete operator messes with pflow

Hi coilbook,
I'd like to have your opinion, could you do this test ?:
customize > units setup > system unit setup > 1 Unit = 0,0254 Meters > ok
reduce spark emission power and adjust camera effect.
what do you think about it?
you might also try on other your scenes, do you think this could be a cause of the issue?
Regards
Paride

coilbook wrote:This is about rendering phoenix fire particles. we have three logs that crashed and created sparks. Octane does not render sparks from all 3 logs. Instead, it chooses if it is a beam 1,2 or 3 depending on group index. It is just 1 grid. Why cannot it render sparks from all 3 beams.

UPDATE:

we added multiple octaneparticle modifiers and it works. I guess if you have 10 beams you will need 10 modifiers with group index 0-9. Can otoy for fire sparks make all particles renderable without having more than 1 octaneparticle modifier?

Hi coilbook,
I think a single modifier particle could prevent having several sparks in the same grid, such as a firework explosion or something like that.
https://youtu.be/Lrs1DcvkDEc
Regards
Paride

HI Paride
I will try it with units. It seems brightness is ok now. We are working in inches.

What about pflow is static when disable pflow instance meshes is unchecked. Thank you