Are these a) easy to find/add and b) are later versions of OCLP likely to include them? If so, I'll just wait.
Isn't that seedenrolement file related to the beta program?
Delete the .seedEnrollment.plist file. You may need to reboot after that for the beta offering to go away.
Same here! I own MBP 2015 13'' and I don't find any information about not working features. I would be very grateful if someone would write a list of non-working functions on my Mac! I want to upgrade from Monterey to Ventura to refresh my computer a bit. Is that a good idea? Will the mac run slower after that, or will the performance remain the same?
So: I would say that the performance, which in my iMac 14,2 (late 2013) had already improved dramatically with Monterey, has improved further with macOS 13 Ventura.
Thank you sooo much!! last question) in my place, would you upgrade your mbp 2015 13" to mac os Ventura? and how can I find out which functions work and don't work exactly on my Mac? thanks for the help again!So: I would say that the performance, which in my iMac 14,2 (late 2013) had already improved dramatically with Monterey, has improved further with macOS 13 Ventura.
In my iMac everything works (Stage Manager, Live Text, Remove Background, Continuity Camera, etc.) and even the third-party apps work better; First of all Adobe Photoshop, but also AutoCAD 2023.
However, I deliberately stopped at Ventura 13.2.1 since many things have changed in the System since 13.3 and a series of problems have arisen which for some have not yet been resolved, not even with the latest OCLP 0.6.8 Nightly.
Note: I'm using the Beta 4 version of OCLP AMFIPass which adapts AMFI to my iMac (AMFI must be enabled for Macs running versions of Ventura prior to 13.3).
Obviously, to use OCLP AMFIPass Beta you need to follow the instructions found in the link that contains the list of all OCLP versions (Near the "Latest" link)
Ultimately, is it worth upgrading to Ventura? Absolutely yes if you have a Mac from late 2013 onwards and if you are tenacious in trying to overcome any obstacles, by reading a lot in this Forum and in the Discord pages dedicated to Ventura in unsupported Macs.
Good luck
Using OCLP yes. I have a 11,4 mid 2015 MBP 15.4” and I’m on 13.4 with OCLP 0.6.7 and working great!
@trifero I also have an MBP11,4. BUT, it did not work well until it was spoofed to MBP14,3 - there was a reason given by the developers of OCLP about a year or so ago why one had to spoof the 11,4 and present it as 14,3... something about support but I forget. In any case, every time I do an update, I first unpatch the boot, reboot, do the macOS update, reboot, then repatch the boot. I am using MBP11,4 spoofed to seem as MBP14,3 to macOS, and I am using the OCLP AMFI pass beta 4 (that allows me to use VMWare Fusion to run Windows 11), on Ventura 13.5 Beta (Build 22G5059d). I haven't tried to use the 11,4 without spoofing; perhaps other have had success without it, I don't know.
I have a 11,5 mid 2015 MBP running Ventura 13.4 with OCLP 0.6.7 without problems.
No problems with old episodes on my MM7,1 and Ventura 13,5 beta. With vpn connection to USA also new episodes will be played - so no MORE restrictions on Apple TV.
Finally!!! I had this too, and wondered that nobody else is having those issues. However it resolved magically „by itself“ recently. Things the might help: NVRAM reset during OCLP boot, install latest OCLP and macOS releases. Do you also have two volumes (Monterey/Ventura) on one Partition?
Interesting question. I've followed closely this thread and the previous ones for Monterey & Big Sur. I don't recall anyone mentioning it but could be wrong.
Installed 13.4.1 over 13.4 on internal SSD of my MBP5,2. Using OCLP 0.6.7 release for EFI and post-install patching.Regarding the menubar, there is a new setting in the latest OCLP 0.6.3n:
defaults.py Don’t set new menubar as default · dortania/OpenCore-Legacy-Patcher@7a07a16
Experience macOS just like before. Contribute to dortania/OpenCore-Legacy-Patcher development by creating an account on GitHub.github.com
I should have read the changelog more carefully... always necessary when using nightlies, my fault!
