![]() ![]() This meant that some Mac models that were supported by macOS were not supported by Fusion because their CPUs lacked certain instructions. For example in a past release VMware added a CPU requirement. VMware is also known to modify Fusion to take advantage of the hardware. And Fusion uses those more than your garden variety application. Apple continues to refine things like Metal and Hypervisor Framework, and its very, very likely that those changes have dependencies on the underlying hardware for certain functionality. If that something doesn't work on a patched Mac, but does on a supported Mac, then you need to be contacting the Open Core community because they're the only ones that have the expertise on that frankenMac.įusion is quite different than the other applications that work with Open Core in that it's highly sensitive to hardware and software capabilities. But you have to go into that world with eyes wide open and realize that there may be things that will not work. All the software I usually use works, except VMWare.īut OpenCore is still modifying the operating system as released by Apple which makes it unsupportable by Apple. On my 2012 MBP for example, Monterey works better than Catalina, bluetooth in particular is better managed. T's a shame, because many people use Open Core with great satisfaction. 2014 Mac mini with integrated Intel graphics. ![]() If it worked under Big Sur and whatever version of Fusion you had, drop back to dittos here. It's possible that VMware addressing the issues for supported Macs/macOS may help you but that's a chance you would be taking. The error message is somewhat of a "catch-all" that can have many different causes. Just because you're seeing the same symptom doesn't mean you have the same underlying cause. While the symptoms you are seeing may be the same as some (but not all) are seeing, you won't get VMware to look at a configuration that they don't officially support. (probably because Oracle is not going to make the investments in a free product to transition the macOS version to using the Apple hypervisor frameworks like VMware and Parallels are doing). If you look at Oracle's documentation, VirtualBox is not supported on Big Sur or Monterey. VirtuaBox is a totally different implementation and continues to use legacy kernel extensions. Fusion uses the Apple Hypervisor framework. P.S.Virtual Box is not Fusion and does not have the same dependencies on macOS capabilities sets that Fusion does. I know they have one for Boot Camp Windows, but nothing for ios. I was really hopeful that they would have released an amd driver update. I will definitely contact Apple soon and will update you. Exited the game and used gfxcardstatus, discrete gpu and it was once again working well. I saw the same issues again in the game (visual tearing, items missing or pixelated, significant lag, etc.). Made sure automatic graphics switching was still off and once again the graphics switched back to the integrated GPU again. ![]() I upgraded Big Sur to the latest version yesterday and went ahead and tried playing without gfxcardstatus. UPDATE: Regarding the automatic graphics switching, I did see it again. Unfortunately, I'm an Apple freak so I keep going back to them. I want to gather enough info before I contact them that they (or they'd just suggest to go back to manufacturer's settings or blame it on the game). I work in IT and honestly hate every time they give me the run around. Glad my input has helped some of you, for the time being. ![]()
0 Comments
Leave a Reply. |