What hardware components should be prioritized when looking to increasing polycount when working in Zbrush?On the macs at my workplace, I can get up to 40 million, though not very stable. At home, I can only get 3 million or so before it hangs up on me.
>>540238do you use sub levels or just use bare polies?
>>540239Subdivision in this case. I was able to reach 7 million polys in dynamesh at work.
>>540238My coworker talked with the Pixologic guys.While the CPU and GPU are obviously important, the primordial hardware to consider is RAM. 32gb is okay, 64gb is ideal, and 128gb is the best, especially for big productions.
>>540240You got your answer, dynamesh isnt for such high sub levelsthe higher the polycount on your lowest sub level the worse the software will run>>540246>While the CPU and GPU are obviously importantfunny that, since zbrush dosnt support gpu acceleration and uses only the cpu for renderingi can easily get to 100mln polies on my 16gbs of ramzbrus isnt really deisgned to go higher than that, in fact 100mln is the limit of a single subtool count, at 1000mln the software will start shitting itself with the memory dump times, you will spend more time waiting for strokes updates than actually sculptingso stop bullshiting
>>540249Uuuh yeah, of course there's a limit of polys at some point, but the idea is that the more RAM you have, the more freedom you get while working, otherwise some operations (especially projections) will make the software crash everytime thus restraining you to do proper work>While the CPU and GPU are obviously importantDidnt talk about acceleration, but those high polys and shading and shit still need to be displayed properly. Learn to graphicsIf you wanna call bullshit on my previous post, your loss.
>>540250>Uuuh yeah, of course there's a limit of polys at some point, but the idea is that the more RAM you have, the more freedom you get while working, otherwise some operations (especially projections) will make the software crash everytime thus restraining you to do proper workyou clearly have no clue what you talking aboutwhat projections?you mena projecting meshes, displacing alpha maps?those operations are done on a vertex per vertex basis ad use 0 ram memory>Didnt talk about acceleration, but those high polys and shading and shit still need to be displayed properly. Learn to graphicsso you were only pretending to be retarded?truly a quality post by a newfag, you will make an amazing addition to this board...
>>54023840 million at 20 frames a second. I hope they really improve this shit for 5. GPU acceleration is not the answer either as substance painter is slow as fuck also.
>>540246>tfw 4 GB
>>540274I have 8, and I feel you. Changing to 32 in not too long.
>>540250Lol zbrush does not utilize a gpu ...at all.
>>540257Try optimizing your mesh topology and maybe it'll work for you .
>>540306When I go up that high, it's for sculpting on a low poly model and baking down normal map and texture map. Some models have large flat surfaces, so I have to crank it up to get the detail I want.
>>540316that makes no sensewhy would you model the low poly first? optimizing is the final steep of a half competent workflowand even if you have a low poly before there is no reason to limit yourself to the low mesh topology has no impact on the normal bakingjust set up the cage and bake what you want
>>540341I'm talking about hard surface stuff here. Things like furniture and such that's supposed to be ready to put into a game engine, with 100-1000 polygons.