VRay is M1 native but does not utilise the GPU for rendering. Twinmotion is pretty much all GPU as its realtime and shares the same very fast memory pool as the CPU.Įpic / Twinmotion team say they are working on an M1 native version for release later in the year. Saving and opening large projects are significantly quicker on M1 due to the fast SSD. Twinmotion (although still running under Rosetta) seems to work very well for me, and apart from a small annoyance over the pointer click targets in relation to some UI elements (there seems to be a 10 pixel discrepancy), Output speeds are vastly quicker than my previous machine (i7 8700k, 64Gb RAM, Nvidia GTX1080Ti). I moved to a MacPro M1 Max (32Gb) from a desktop Hackintosh, I do a fair bit of visualisation and have used VRay and Twinmotion for a number of years. That gap will likely shrink as they optimize the code for Metal in future releases, but anyone looking primarily for a rendering machine is (so far) better off on Windows.Įdited to add: TwinMotion had originally indicated that a M1 native version would be released in the fall of last year, but are no longer committing to a release date, though it appears that they are working on it:ĭon’t know if the Epic / Apple App Store legal feud has been a factor in the slow walk on the M1 version, or if it’s more down to technical issues. Though your larger point remains true: even with the new release, render times are still much faster on Windows machines. I’ve yet to hear of a rendering program that allows processing to be shared by the gpu on Mac machines.īlender’s latest release now enables both CPU and GPU rendering natively (using Metal) for Apple Silicon:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |