![]() Mudbox has crashed running it's autopo and again it generally is error in the mesh. Also 3DC is not alone in crashing or failing running a autopo routine. This is true of all the software that has autopo. This does not include the decimation part, the less decimation you apply in the autopo panel, the longer it will take to calculate for the retopo mesh. 28,000 polygon autopo retopo mesh, time to completion 32 seconds. Time start of the calculation to the finish mesh, 27 seconds. System, older 8 core Amd cpu, 16 gig system ram, 770 gtx, 4 gig of ram.Īutopo- 23 million surface mode model to a 7,000 polygon retopo model. I agree there could be some more multithreading in 3DC. I've noticed that it's not always reliable/accurate though if the non-proxy version has more detailed information already. ![]() I accidentally double clicked an edge in selection mode on this 1 million triangle retopo mesh, been waiting over 30 minutes for response :P Quite a few tools that can do this in sculpt room as well.įor broader shapes you can use proxy mode with decimation and push/pull the surface into shape you want. I used AUTOPO on a 10 million triangle layer yesterday, it took about 8-10 hours to finish. For sculpting program though, would have thought it could handle size like this, and for regular sculpt brushes usually it can just fine. Granted I work on mesh size of 1-15 million triangles(surface volumes). ![]() Some tools also can be laggy, Fill Holes tool lags just switching to it for a moment. Even simple thing as delete, even if you have most of the mesh hidden you can wait a while. 3D Coat doesn't scale too well with quite a few features stuck on single thread. I have a machine with AMD ThreadRipper 1950X running at close to 4GHz 16 Cores, 32 Threads, 128GB of RAM and a 1080Ti GPU(and a 1TB NVMe M.2 SSD that can do 3.5GB/s read and 2.1GB/s write). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |