Liquid in a cyclone

[JuhaHo]

I reduced the resolution to 10.8 million voxels and ran out of memory. I'm now reducing to 8.4 million to see if Phoenix can handle that.

[Svetlin.Nikolov]

The problem is obviously not about the grid resolution.

Btw, could you check if you have adaptive grid? If it's enabled, what would happen if you change the "Preallocate" option to "Disabled"?

[JuhaHo]

No, I don't have adaptive grid. I have never used such.

[JuhaHo]

I reduced Voxel amount to 8.5 million. I also reduced the polygons of the most complex object to half. I got the out of memory error at frame 492. I try to reduce the voxel amount even more to see what is the absolute maximum amount of Voxels Phoenix FD can handle.

[JuhaHo]

I reduced the Voxel amount to 4.2 million. Now the simulation had advanced to the frame 645 where MAX crashed. I looked at the event viewer, and there was a low memory condition at the time when Max crashed.

I would really appreciate, if someone showed me even a slight interest telling me a way to overcome this. What is the absolute maximum amount of voxels, Phoenix FD can handle if 4.2 million is too much?


Please

[JuhaHo]

With 2 million voxels, simulation ran out of memory at frame 819. Next I'll see if Phoenix FD can handle one million voxels. Should it?

[JuhaHo]

I made a new attempt with one million voxels. Max had crashed at frame 1256. So it seems Phoenix FD can't handle one million voxels. I think, I have to ko down to 500 000 voxels to see if Phoenix FD can handle that without crashing Max.

I would really appreciate support participation on this case. Would you kindly to take this request to consideration please.

[georgi.zhekov]

Hey,

Phoenix can handle billions of voxels without problems, seems like there is something specific to your scene, but without any files we have no way to reproduce the issue on our side.

If you can send over the scene via the support system - we can sign an NDA and you can be sure that if the files are confidential - they will stay this way. Without your scene we have no way of finding out where the problem is so that we can help with it.

You can use this link to submit the files here (at top right, there is a submit a request button) - https://support.chaos.com/hc/en-us

Thanks!

[JuhaHo]

I'm working on the permission. In the meantime, I can report that half a million voxels is too much for Phoenix FD to handle. Next I'll try quarter million.

[JuhaHo]

I made big changes on my Phoenix FD set up and increased the grid back to 5 million voxels. Max crashed at frame 74 due to memory consumption. It looks like Phoenix FD is capable for handling only 200 000 - 300 000 voxels, which is a problem, because the simulation looks horrible with that amount of voxels available. Any ideas on how to continue? I really need to finish this project.

[JuhaHo]

There's also one thing, that has always been a bit confusing for me. How does the surface affects to the outgoing velocity volume. Here's an example. I know the desired speed for the liquid in a pipe and have adjusted that correctly. If I want to include bigger pipe (with 3 x surface area) that feed the liquid to three pipes. What is the correct method to maintain the speed? Is it enough if I scale the emitter accordingly and multiply the outgoing velocity parameter by three? Does the outgoing emitted surface area affect to the emitted volume?

[JuhaHo]

I will continue the monologue because no one seems to care to respond.

Anyway, I isolated only the geometry that is absolutely necessary for the simulation. Then I increased the voxel amount to 10 million. I was able to run the simulation for a bit longer than earlier when I had the rendering objects hidden in the scene. However Max crashed after running out of memory. I'll reduce the voxel amount to 7.5 million to see what it does. I would really appreciate if someone had any better suggestions what else I can try.

Thanks in advance..

[fixeighted]

Well, honestly, this post is now 7 pages long and it appears you're nowhere near where you need to be.
So, you asked for a response so I'll offer one.

In the nicest possible way I would like to observe that you've essentially stated that Phoenix is not capable of simulating a tiny amount of particles, based purely on your own
experience with this particular scene. It simply isn't rational to suggest this, I would say.
It is genuinely and demonstrably untrue, evidenced by the numerous examples showing the opposite; so whilst I can understand your frustration, it is nothing to do with the core facility of the software.

Honestly, I strongly advise you to provide a scene which they can help you with.
Otherwise you are likely to remain in a cycle of disappointment, not having learned anything.

I wish you luck with this and hope that it eventually works out.

[JuhaHo]

Thanks fixeighted,

Phoenix FD in the reduced scene had crashed again with 7,8 million Voxels at frame 599. I looked the event viewer, which told that explorer.exe is consuming 214.2 GB RAM. I wonder what this is about? Explorer is not even running.

[JuhaHo]

I installed the latest nightly and seem to have lost my license in the process.

I rebooted the workstation, and it's now simulating. Lets see what happens.