My systems have all been trouble-free, virus-free, come with quality software, never require costly updates.
But, if you are willing to pay a bit more for not letting the MS skunk in the house, an M1MAX system may be the way to go. If FPS and gaming are the only thing you're after, an Intel/Nvidia rig is probably what you are looking for. As for the eGPU business, there are multiple posts of people who returned them in disappointment. Depending on the scenario (aircraft, scenery, settings, etc), the MacOS version of X-Plane ran 5-15% faster on the iMac, than the Windows version of the same X-Plane running on BootCamp, all on the same iMac. I also installed a BootCamp partition on the iMac a few years ago, to test it, out of curiosity. I bought a 32-core M1MAX MacBook Pro and it runs X-Plane about twice as fast as my i7 iMac. i recommend not getting an m1 mac, and for gaming i recommend installing bootcamp and getting a decent egpu(1650 ti or better or amd equivelent) No offense but macs are not made for gaming or flight sims.
Thanks! I wasn't sure if 'supports' can be considered equal to runs natively. You can also read this threadto be reassured. We are building our own test plugins and working with our third party developers to make sure these new pathways have been tested experimentally. In X-Plane 11, the first plugin to run CEF would ‘own’ it this new setup allows X-Plane and all plugins to share CEF and should make it easier for plugins that need to access web pages to do so. In X-Plane 12 we run Chromium Embedded Framework (CEF) at startup.
We are making the FMOD API available to plugins (in a few different ways) so that plugins that generate sound can interact with the full 3-d sound environment. Plugins that use OpenAL in X-Plane 12 will need to package OpenAL themselves. X-Plane itself hasn’t used OpenAL in years, and we are in no position to support it. The X-Plane SDK supports the new ARM M1 Macs. With the new major version we are making some changes to the plugin environment:
0 kommentar(er)
