With updated nightly version, I was able to simulate 7 808 208 Voxel version completely. It's a bit too low, so I try to double it for overnight processing. I had Phoenix 5.1 version and updated to version 5.2.
Announcement
Collapse
No announcement yet.
Liquid in a cyclone
Collapse
X
-
I found out that when running the simulation with my HP ZBook 17 G5 Mobile Workstation, there is no running out of memory. It's running on Windows 11 while my main workstation HP Z640 runs on Windows 10. Is there an explanation for this running out of memory phenomenon?
Comment
-
I'm now simulating with 55 297 600 voxels. The simulation advanced to frame 188 and then crashed due to out of memory problem. I saved the scene, rebooted the workstation and restored the simulation at frame 180. It's working now frame 194, so it passed the earlier limit. It seems, I have to simulate this piece by piece to get the required amount of frames.
Comment
-
At the moment simulating frame 723. Only one crash so far. For some reason, it's not consuming memory as it used to. Maybe the answer was a reboot just before starting the simulation.
However the are some one voxel leaks. I hope they don't look too bad on renderings.
Comment
-
Hey,
As a workaround can you try to enable the "Render time only" checkbox for the Grid texture that is connected to the V-Ray material assigned to the simulator?
This will prevent the Grid texture to be evaluated during the simulation and hopefully should help with the issue.Georgi Zhekov
Phoenix Product Manager
Chaos
Comment
Comment