I have 8 GB of RAM, when I subdivide into 7 divisions, the standard female head model (which comes with the program) 8 GB is enough for 50 million polygons and still has 20% of the space, but when I import my head, which has the same amount polygons (even a little less), then there is not enough memory, even if you delete the entire history of cancellations, although everything works fine with a standard head. Yes, I understand that 8 GB is not enough, but with a standard head butt but enough, but for some reason not for my head. Why is that? I have suspicions that the developers did it on purpose, but why it is not clear.
Why do you say “there isn’t enough memory”? Are you seeing some sort of error message when importing the file? Is the program telling you that it must delete Undo History entries when you try to perform an operation?
A 50 million polygon mesh is quite dense and would result in a very large file. This will require a lot of memory to simply keep it loaded and will experience some performance related issues on any system. Please remember that ZBrush is not the only thing using memory on your system. We highly recommend 16GB of RAM or greater to work with models of that density.
RAM: 16 GB for working with multi-million poly models (32+ GB preferred.)
-
If you are having trouble opening a specific file, there may be an issue with the content in the file. Please contact Support for any technical issues with ZBrush.
-
If the file has simply become too large to work with on your system, try using Preferences> Undo History> Skip Loading to purge the file of Undo History before opening it. Disable the saving of History and purge any unnecessary tools or subtools from the file. Try to get the file size and preferably the density of the mesh down.
-
It is expected that you may see the program start to delete Undo History entries when working with a mesh of that density. If this is the issue you’re experiencing you can control how much memory ZBrush reserves for the Undo History in Preferences > Undo History.
-
If you are running out of storage space on the drive where ZBrush’s scratch disk is installed (100 GB free space recommended) AND you are working with mesh of this density on a system that is under recommended spec, you can expect memory related issues.
Please contact Support for further assistance with this matter.
Thank you!
with an imported model, after subdividing up to 50 million polygons, the program works for a couple of seconds and crashes, but the optional head perfectly subdivides up to 53 million polygons and does not crash
Check the imported model for issues with Geometry> Mesh Integrity> Check Mesh. If it has serious enough problems it may crash when you try to do anything with it.
One 50 million polygon mesh is not the same as another in terms of file size or performance. There are many variables depending on the state of the model and the active features being used in the file.
There is no getting around that your system is under the recommended system specs for what you are trying to do, however. That could easily be the problem. You would need to contact Support and provide license and system information to troubleshoot a potential problem with the file. However nothing we can do there will allow an under spec system to work more easily with meshes of that polycount.
A mesh of that density is ambitious for a system with only 8 GB of RAM, a chunk of which will be taken up by the OS and other running processes. Modern OS may use as much as 4GB just for its own purposes. The minimum specs for ZBrush are simply what you need in order to operate the program with minimal performance needs. To work with meshes of that size more comfortably you need 16GB, though 32 GB would be better.
I’m going to close the thread because I don’t want you to feel like you’re being ignored when you don’t receive further replies here. Technical support involves the exchange of sensitive information and can’t be conducted over the public forums. I’d like to encourage you to contact us where we can better assist you.
Thank you!