![]() I thought there would be some missing pieces or things out of place - I was thinking that this software might be spoofing a different model, but pulling up "About This Mac" lists out all of the correct details (this is listing Intel HD Graphics as the early 2013 is a dual GPU setup where the 650M only kicks in when needed to save power) I was expecting some hiccups in the process, but there weren't any. Anecdotally, it seems like there are more people online complaining about issues with Monterey than I see with most macOS upgrades. OCLP also has beta support for Monterey, but I decided not to shoot for the moon and just work with Big Sur for the time being. There is a wonderfully detailed step-by-step tutorial for getting everything up and running and to my amazement it works perfectly. This caused me to look into Patched Sur again, only to find that there is a newer better option called OpenCore Legacy Patcher. I tried checking and searching around but it doesn't seem that anyone bothered to make any earlier versions available online. The book is available here, but the only version available to download is for Swift 5.5. but that's not okay either because while Apple provides an ebook called The Swift Programming Language to teach the ins and outs of the language, they only seem to make the most recent version of the ebook available. That's okay, I can just use an older version of Xcode and learn a slightly older version of Swift. This would be okay except the latest version of Swift is only available on Macs running at least Big Sur. My acceptance of Catalina was going alright until my interest in learning to code brought me to Swift. Ultimately, I decided it didn't matter and just accepted that I was now running Catalina until 2028 when I decided that it was time to upgrade my hardware again. There was no support for patches directly from Apple and there were issues with wi-fi on some machines. Early efforts resulted in Patched Sur, which had some quirks to it. This is not the first time this happened in modern Intel Apple times, but it was certainly the most widespread presumably because so many fully capable machines had been ditched for no discernible reason. There's a 2020 model that's not far off from the 2013:Īlmost immediately there was a very strong community effort to get Big Sur running on unsupported models. In the same vein, here are the multi core Geekbench scores. My only guess is that it was simply a casualty because other people with this model might not have a GPU that supports Metal and it was done to simplify their listing of what models are compatible with Big Sur.īelow, you can see single core Geekbench scores and a range of models that are around the 2013 retina MacBook Pro - some of the company it keeps are 2014, 20 models that are compatible with Big Sur: It's certainly not a RAM issue and it's definitely not a processor issue, so what gives? I genuinely have no idea why this model was dropped. It would be one thing if the 650M didn't support Metal. Naturally, I was wrong and Big Sur dropped compatibility for the early 2013 retina MacBook Pro. The specs were comparable or better than most of what Apple was offering as their entry level or midrange machines at that point and I figured I'd be good on OS upgrades for a while since it was a top of the line machine for its time. While it was a 2013 it was by no means dated and is more than sufficient for the editing I was doing and as a daily driver. I settled on an early 2013 retina MacBook Pro with a 2.8ghz quad core i7 and a 1GB GeForce GT 650M. Since I hadn't gotten a new computer in ~10 years at that time (it was 2018), I decided it was time to upgrade. Since none of those were worth much, I settled on using my girlfriend's mid-2012 MacBook Pro. ![]() It is terribly specced and I just never found a use for it. At that time the Mac horde consisted of a late 2008 MacBook, an iBook G4, a G4 MDD and a 2006 or 2007 polycarbonate MacBook that has never really been used because it was given to me for free at a thrift store since they couldn't get past the password. When I started doing YouTube videos a few years ago I realized fairly quickly that I would need a much better setup for editing.
0 Comments
Leave a Reply. |