Phoenix FD 3.0 particle usage with Octane plugin 4.33 Tweet

[paride4331]

Hi darkline,
Personally I would not know if it depends on 3dsMax 2014.
Everything seems to work.
Regards
Paride

[darkline]

Thanks, but who at otoy can test this? Last time I checked Octane 3 supported Max 2014 correct? Or have you discontinued support for this version?

[paride4331]

Hi darkline,
did you use liquid simulator and liquid source Instead of phoenixFD presets?
Paride

[darkline]

No I used presets and then changed the parameters. Does that make a difference?

But I would add that I have used presets before with some success on motion blur, I just cant figure out what is making it work sometimes and others not.

EDIT : So far no motion blur either creating from scratch

[paride4331]

Hi darkline,
I'm using a demo too and sometimes preset give me crash error, before using Octane;
I don't know why but i cannot test it beacause, as you know, every time you open a demo scene, phoenix reset it all.
Try liquid creator, it seems works well.
Regards
Paride

[darkline]

not working for me. Created liquid source and simulator, activated movable proxy, vertex motion blur, and motion blur in octane settings. Made sure liquid is checked in output of phoenix; simulated a few frames and still no motion blur

[paride4331]

Hi darkline,
I will try to install 3dsMax 2014.
Regards
Paride

[darkline]

Thanks Paride,

I opened an older file which did render with motion blur (it resets all settings but keeps the simulated cache files). So I copied all the settings and resimulated for half the timeline. Again the new simulation did not have motion blur but halfway through the simulation (where it switches back to the old cache files) motion blur appeared. It's just really odd behaviour. I had it working but now can't get it back again.

[paride4331]

Hi darkline,
I tested phoenixFD in 3dsMax 2014. It seems to work.
I think you should test MB and MVB in rendering production rather than OctaneRender Viewport.
Regards
Paride

[darkline]

this is baffling. I'll try uninstalling and reinstalling the plugin