PHXFoam and Pflow unknown exception

[omere]

just found out that if i have in the scene PHXFoam and pflow (even if the pflow is not connected to the PHXFoam) max through "Unexpected exception"

you can test it by creating a PHXFoam object, create a Preset Flow in Pflow and thn hit render.
the error will pop up.

[flipbook]

Works fine here, my version of phoenix is from late March I think.

[georgi.zhekov]

Seems to be working here as well. What build are you using? Do you render with V-Ray(which version) or Scanline?

[omere]

my version is from 20.4.16 and before that i've tested this with 11.4.16.
this problem is happening both with VRay 3 and with scanline

[omere]

also i should add that i'm using 3Ds Max 2014 and windows 7

[Svetlozar Draganov]

It would be better if you could attach the scene you are working on so we could investigate what's going on.

[omere]

sure thing.
here is a link to download the scene:

https://we.tl/6jlfgkwsQ8

[Svetlin.Nikolov]

Very strange, couldn't blow it up on several different machines.

Would you be able to post here the phoenix_maxver2014.log file you can find on your C:\PhoenixFD immediately after the crash?

[omere]

sure:

[Svetlin.Nikolov]

Hey,

I think I have an idea of what's going on - in your scene, in the environment and effects dialogue there should be a couple of atmospheres - one of them is PhoenixFD, and the other one is the V-Ray VoulmeGrid's atmosphere. If you delete the volume grid, it should be okay. We fixed this a while back in both Phoenix and V-Ray. Which V-Ray version do you use? In 3.30 it should be okay.

[omere]

oh!
we are using in the studio VRay ver 3.20.02.
i have noticed the VolumeGrid Atmosphere. but every time that i delete it, it is automatically being added back

[Svetlin.Nikolov]

Yup, that was fixed too - now the volume grid atmos shouldn't be created for no reason.

[omere]

great. thank you very much for your help