![]() ![]() 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. How can a 2,8Mil polygon model run out of memory when a 20Mil polygon model worked fine? 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. 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. I suppose there is a bug or something because it makes no sense to me.Īs 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. I have posted the below example at the Keyshot forum. That was the reason for buying Keyshoot, using RAM instead and not having to worry about if a scene would fit in memory or not.īut I have found that some simple things can take forever to transfer and waste all of my 16Gb RAM. With Octane I’m limited to 4Gb VRAM (as I think VideoCards with more memory than that getts silly expensive). Some things work fine and I do like the skin material.īut somewhat I wished I used the money for 16Gb extra memory or a second VideoCard to get faster renders with Octane instead. I have a lot of like / dislike experience as well. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |