Hey Aurick that is great to hear thanks!!
G3D I have a dual 3.4, 2 gigs of ram, aTI 9800 card and a 140 gig hardDrive at work and it handels 6 million polys with no problem, I have a 2.8 ghz, with 1.5 gigs of ram as my main home machine and it can deal with meshes at least 3 million polys.
I’d really like to move ahead with ZB. I know that the problem isn’t my sytsem or hardware; I’ve done ram tests till the cows come home and the ram passed every test I threw at it. What about my other questions:
Could the trouble be related to available disk space?(I have approx. 7 gigs free)
Could it be XP service pack 2?
Video drivers?
Something else?
:qu:
TIA
i hate that damned error, hehe
The problem is the 32 bit OS
and the 4 gig limit thing.
In reality, any app is only able to utilize 2 gigs of memory, whether it be RAM, the paging file, or a combo of the two.
Win XP tends to split the memory management in half giving half to RAM, and half to the paging file.
I have been doing a lot of exporting of high rez zb files, and this pushes zb to the max. As soon as i get it to 2 gigs, boom. That damn error pops up.
And when i say 2 gigs, i mean, 2 gigs of total memory usage, typically half RAM and half paging file.
if you want to test this make a 3 million poly model in zb.
then open the task manager, go into the processes tab, and in the view menu up top, choose “select columns” and pick “virtual ram.”
then click the mem usage tab so that zb stays at the top and is easier to view.
then export the model you just made as an obj.
as soon as both chunks get to about 2 gigs, boom.
it looks like it blows up right before that, but i believe what is happening is that the memory is being used in chunks, so when zb adds another chunk, it tries to go from about 1.9 gigs to something over 2, but you don’t see that in the task manager cuz that is when zb blows up.
this will be fixed when it is compiled for win 64, i believe.
-zee
oh that is interesting, I didnt know any of that, good thing I didnt buy more ram then :)Thanks Zeebit!
Hey Zeebit, I really don’t have any need to export such a hi rez mesh, but for the hell of it I gave it a shot. The model I exported was a little over 4 million polys. I have 2.5 gigs of ram. Nice little hang you found. First time I have ever had to kill the app. 
Ktaylor what is the destination app for your high poly model? Are you planning to reconstruct the surface?
sirquadalot “Ktaylor what is the destination app for your high poly model”
I was going to take it into the Nvidia Melody(freeware from Nvidia, trying to see how high of a mesh it will accept with my system specs) app to generate a normal map, something about the way Z brush compares the meshes for normal maps doesnt appeal to me so I have been exporting the High res meshes and using other apps to generate them, this is all for realTime stuff.
yeah, i use it for exactly the same thing ktaylor.
the best method i have found while we wait for win64 is to just break the mesh up using polygroups and the delete hidden function.
then gen the normal maps a chunk at a time and comp them in PS.
hope that helps
-pete
Cool thats good to hear cause that is what we are doing as well 
Thanks for all the help!