Keyshot 10 for zbrush8/3/2023 ![]() ![]() ![]() Then the setup part starts and when it reaches about 80% of the progress bar memory starts to rise and tops at 15,7Gb and after 10 minutes or so from starting the transfer I get a message that warns for instability due to low memory resources.Īfter that point nothing more seems to happen so I closed down Keyshot. Memory usage varies a little but climbs slowly to about 10Gb. When Keyshot loads and starts to load the data memory usage rises to about 8Gb. When I start the transfer System and zBrush uses about 4Gb of my memory. Removed averything except the fiber hair from the model and got it down to 3.3Mil polygons. If I consider the almost 4Gb RAM that zBrush used then the bridge and / or Keyshot is using more than 12Gb. I understand that in the transfer to Keyshot textures are created as well but that can hardly explain why so much more memory is used. I can see that the polygon data only uses 0,5Gb VRAM. In order to figure out how much resources are used, I loaded the same parts into my Octane render engine, expecting it to crash as I only have 4Gb VRAM. How can a 2,8Mil polygon model run out of memory when a 20Mil polygon model worked fine? This transfer took even longer and in the end Keyshot crashed with an out of memory message. Just as the previous model it had fibers, about twice as much but the total model was of modest 2,8Mil polygons. Memory usage run at about 10Gb with a peek up to 15Gb (I have 16Gb) and after completed transfer it leveled out at about 13Gb. So I transferred a close to 20Mil polygon model and while it took a long time to transfer it worked really well once it was finished.īoth Keyshot and zBrush running along just fine. ![]() As Keyshot don't support HD geometry from zBrush I did some tests to instead go higher on ordinary in subdivision in zBrush as it now supports 64bit, it should be possible. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |