Thanks, what date is the nightly build you are reporting on?i think OCLP 0.6.3 (nightly build) will fix this bug in Safari:
OpenCore-Legacy-Patcher/CHANGELOG.md at main · dortania/OpenCore-Legacy-Patcher
Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.github.com
Apologies if this has already been answered but:
Is anyone running 13.3.1 with OCLP 0.6.2, or it the nightly .3 build needed for stability reasons? Just want to check before I update from 13.3.
It's the latest build availible. To my knowledge, there is no readily downloadible .app file so you will need to compile it.Thanks, what date is the nightly build you are reporting on?
Thanks, what date is the nightly build you are reporting on?
Look at the post 3 above yours. # 4773 latest build dated 4-8-2023 4:35AM (last I checked, may be a later version available)It's the latest build availible. To my knowledge, there is no readily downloadible .app file so you will need to compile it.
I already saw it. It's just a changelog. No downloadable content that I can see.Look at the post 3 above yours. # 4773 latest build dated 4-8-2023 4:35AM (last I checked, may be a later version available)
You can download the latest nightly build as an app here:It's the latest build availible. To my knowledge, there is no readily downloadible .app file so you will need to compile it.
Ah didn't see that page before! Thanks!You can download the latest nightly build as an app here:
OpenCore-Legacy-Patcher/SOURCE.md at main · dortania/OpenCore-Legacy-Patcher
Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.github.com
If the guys who make the patcher say there should be no direct link to the nightly, why do we go on putting it out, this after several admonitions not to do so?You can download the latest nightly build as an app here:
This isn't a direct link - just their download page which they state one can doIf the guys who make the patcher say there should be no direct link to the nightly, why do we go on putting it out, this after several admonitions not to do so?
Non-supported video card drivers are still a long way from being perfect.(Maxwell)
Yes, i have AMD 6770M 512MbNon-supported video card drivers are still a long way from being perfect.
If you don't know (apologies if you do), Maxwell cards are not supported in Mojave or newer (patched or not-patched) as they require NVIDIA Web Drivers, which Apple doesn't support anymore. While you can run these cards with newer releases of OCLP thanks to huge amounts of work being done on unsupported cards/chips, it is not polished yet and can still have some bugs.
Do you still have your original MXM card? I know it's not supported either, but it will be an AMD card, which play way better with modern macOS releases.
My advice. Just go AMD. NVIDIA is and will never be anywhere near as reliable as AMD on modern macOS releases.There are two options - either wait for Maxwell support in OCLP or replace the GPU with AMD?
I don't think it's possible, Apple is working hard on tightening the gap of possibilities to run newer macOS on older macs. I hope I am wrong.MBP11,3 + macOS Ventura 13.3.1 + OCLP 0.6.3n = Preview now correctly opens images and Blender works again: very good, indeed! Now, re-enable AMFI (and also LV, if possible)…
The OpenCore-Patcher application “replicates” itself to /Library/Application Support/Dortania (and creates an alias in /Applications) only if you install the root patches: at least, that has been my personal experience, so far…I have done an experiment:
Earlier today I rebuilt OpenCore and applied the patches using the latest nightly as of today, while remaining on 13.2.1 (since reports for 13.3.1 were positive, I was getting ready).
Right now I deleted both copies of the patcher and redownloaded it. It's in my Downloads folder, of course.
Normally I would then move it to Applications but for now I will run it as-is and see what happens.
Upon launch it verifies, then opens but does not replicate itself anywhere.
Same after moving to Applications.
I bet if I were to Build and Install OpenCore again, the patcher would replicate to Application Support, but since I already did that earlier, I won't do it again right now. And perhaps because I did exactly this earlier, that's where the same-date/same-version copy came from.
I've just asked that on Discord. Let's see if there is hope.^^^ It should hopefully be possible for AMFI (otherwise, sadly, it will be necessary to return to Monterey, for virtualisation users); as for Library Validation, they said in the beginning that they would research other patches, in order to try to mitigate the problem: so, let’s hope well also here - we’ll see, anyway…