It’s only in the last few years that Apple seems to have realized that 3D is even a thing, probably because of iOS and iPadOS game development, something that they weren’t really ever interested in on macOS. It’s a far more niche thing to do stuff in 3D with a much steeper learning curve than for instance casual Lightroom/Photoshop editing or cutting family videos in iMovie, which effectively means that there are far less people that you can sell your wares to. When it comes to 3D, things are wildly different. Intel and AMD chips have similar features too, but often to a lesser degree, or only in their upper tier. They have a whole panoply of hardware video encoders and decoders in the new M1 chips (hardware-accelerated H.264, HEVC, ProRes, and ProRes RAW). Yes, but the film industry and YouTube influencer crowd mean big business for Apple, and they always make sure that video and photo are amongst the things that works best. The m1 mac mini handles high resolution video far beyond to what mine can do, so why not also handling a few meshes better than before So having all that information it makes me believe the mac mini could be actually plenty in these regards if i dont want to make real time raytracing matrix style. The m1 mac mini handles high resolution video far beyond to what mine can do, so why not also handling a few meshes better than before, i now have a 2 gb video card, that is even considering the transfer rate might have been/still is with faster video memory if that is true at all still quite a difference. it is claimed that RAM now simply has less relevancy, specifically since the data ping pong became so tightly and readily integrated. i am not a computer scientist so what i say has to be taken with a grain of salt. Well the truth is a bit more complex than that and different to what we are used to. Rosetta 2 does a great job of translation to get Intel based builds running pretty darn fast.Yes, but as I pointed out above, you probably have to split that in half, which in case of the 16GB configuration, would mean 8GB for the CPU - which isn’t great for any CG work, even 2D - and 8GB for the GPU, which also is only mediocre at best. Having a silicon build will help as well, but probably not that much. Rhino 8 will be significantly faster than Rhino 7, but that is almost entirely due to our transition to Metal instead of OpenGL. I can’t promise everything will be fast enough for your purposes by the time your 90 day evaluation period ends. This is being done in Rhino 7 and will show up in our service releases in the coming months, We are also thinking of alternative approaches to drawing geometry to eliminate going down paths where we know things are slower. We are making changes to work around these bugs in other cases. We are finding bugs with this and reporting them to Apple (which are in turn getting fixed in MacOS updates). There are bugs and there are areas where things are slower. The problem is that Apple’s OpenGL implementation on M1 is quite different than what it was on Intel based Macs. This is not an issue with requiring a silicon native build of Rhino. There is misinformation going on in this thread as to why Rhino 7 is slow on silicon based Macs.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |