hello
it a simple grid with jammed all and a inital fill of 60 and after a few frames I get this! http://c2n.me/3oMzlqI.png
why? there’s nothing moving or no force at all…
and i get this error when render is finished, and the max crashes… http://c2n.me/3oMBbrK.png
it’s a nightly from oct-06-2015
best regards
themaxxer
I’m going to see if it happens with mine. It looks like its very small scale though. Got a scene to try?
To be honest I get a similar thing happening, just not as pronounced as the above. The current state of the flip solver struggles with calm/flat resting position so maybe that is the reason combined with the closed boundaries. Who knows, best wait until one of the devs answers 
I’m running 8th October build.
Also getting it when leaving an open boundary to sim on its own (not as bad though). It looks very similar to the old core in that velocities would spawn out of nowhere (used to happen in fumeFX also). THe workaround for that was to block off the sides with geometry. Anyway shall see what they say
good to know. thanks for your information.
best regards
themaxxer
as flipbook already said, it looks like small scale issue, the usual fix is to increase the spf, or to fake the scale.
the crash is caused by the conflict between vraygrid and phoenix shader, it is already fuxed, but the fix is in both the sides, so you have to upgrade vray too.
no the scale is metric and the grid is about 2m in scale…
do I have to update vray to a nightly? or is it 3.2.03?
i tried with default settings and 2m container, no problems here. can you send the scene?
about the crash, try with nightly vray, or if you prefer to not install new vray try the workaround described in the thread dedicated to the problem. it’s a simple one - delete the vray grid atmosphere, save immediately, restart max, load the scene
