The new official OCLP 3.0 will not be released. Most of the developers have left, and the others are unable to continue. The unofficial version OCLP 3.1.4 remains. At the end of December, I posted a link to this or an older version. This is sufficient for Hackintosh because we can change the graphics here. For us, Wi-Fi and audio patches are the most important things. However, older Mac computers with nvidia graphics will no longer have this option.
I think that some things just can't be done with Tahoe. Due to the significantly higher system load, it is probably not a good idea to install Tahoe on very old Mac computers.
From my experience, I can say that the minimum hardware requirements for Tahoe are 6th generation processors and above. If you have a 3rd generation processor or below, you should stay on Monterey ; the lack of AVX2 support will prevent you from using certain programs.
It is more rational to focus on highly efficient PCs with 14th or 15th generation processors. A realistic alternative to MacPro . And here, installing Tahoe makes sense as a way to extend the life of the system or computer.
But we can also work for many years on macOS Sequia, which does not have such high hardware requirements.
The last system where HD4000 could be launched using spoofing method was Sequoia.anyone got graphics drivers working for the Intel hd graphics 4000 on macos Tahoe?

Do you have GPU hardware acceleration on Tahoe (with OCLP 2.4.1 or an alpha/beta version of OCLP 3.0?)While we all are very, very, very .... patiently waiting for the final release of OCLP3.x.x, I have done some further testing starting from #1.217.
This time not with the NVIDIA Geforce GTX 680 4GB but with a Gigabyte HD7950: it is recognized with the full 3GB instead of the 9MB of the Kepler.
View attachment 2603800
At least a small step forward. 😉
Not yet - I'm working on that.Do you have GPU hardware acceleration on Tahoe
Agreed. However, software still seems to be the bottleneck no matter what hardware you've got. Despite the differences in overall performance, oddly enough stock apps like Photos still run underwhelmingly bad on new hardware as well. I do compare MacMini M4 with the MBP2012, using both machines side by side on a daily basis.Mac or MacBookPro 2013 is not good hardware for Tahoe. This system has much higher hardware requirements,
as you can see . But you can use older systems just as well, or even better.
And, of course, the oldest computers will end their lives not on macOS but on Linux.
That's the natural order of things
Watching this tread of course can get a lot of people all worked up. The current build v. 2.4.1 works well as intended.BTW, the OCLP 2.5.0 nightly can be downloaded and tried rather easily: let’s hope that the final release will be out soon (2.5.0 is of course only for macOS up to Sequoia); while patiently waiting for OCLP 3.0.0 for Tahoe…
Hello friend! Perhaps you missed the news, but the great @khronokernel (co-founder of OCLP along with @dhinakg and a few others) has been hired by Apple and is now working in a security department.Watching this tread of course can get a lot of people all worked up. The current build v. 2.4.1 works well as intended.
To me, it has been the best overall and I am very grateful to the developers who have put a lot and I mean A LOT of work into this and to provide for the public a FREE solution so our "good" old Macs that still work fine are able to "still work fine" and don't become door stops or land fill. 😊
Many thanks to the developers so far.
macOS Tahoe is probably the biggest challenge that the developers have had yet to make our old legacy Intel Macs work. It WILL probably stop after maybe macOS 27 when intel support ends and I do not think that is my opinion.
If the developers can pull that off and continue further...they should work at Apple. 🤣
It is better not to tempt the developers to rush a half-baked patch like Apple did with macOS Tahoe. I personally can wait.
I do not think the developers are motivated or really "care" what the public say. They should not...they are not being paid for this. They do it for their own reasons. Don't make them mad.
I hope we all just settle and be grateful to "wait". "If" no other version comes out...it has been a good run. I hope at least they get macOS Sequoia solid in working on most old Macs, along with the other older OS's that some of the old Macs work better other than Sequoia.
If the developers can do THAT..that is a good end. EVEN If they end now, v.2.4.1 is good and we all can be happy.
Let's encourage instead of put-down or complain please. 😃
Since when was dhinakg hired by apple? I don't remember seeing that...Hello friend! Perhaps you missed the news, but the great @khronokernel, co-founder of OCLP along with @dhinakg and a few others, has been hired by Apple and is now working in a security department.
This is a positive development, as we know that a person with an honest, generous, and good spirit can be like a grain of yeast or a mustard seed that grows and influences the whole dough.
This is good to hear, I did not know. Was the recent? Maybe why the delays in OCLP?Hello friend! Perhaps you missed the news, but the great @khronokernel, co-founder of OCLP along with @dhinakg and a few others, has been hired by Apple and is now working in a security department.
This is a positive development, as we know that a person with an honest, generous, and good spirit can be like a grain of yeast or a mustard seed that grows and influences the whole dough.
It is in Mykola's blog from June 2025 https://khronokernel.com/macos/2025/06/20/OCLP-RETROSPECTIVE.html and was put into the announcements in the Discord OpenCore Patcher Paradise.This is good to hear, I did not know. Was the recent? Maybe why the delays in OCLP?
Development hasn't stopped. Some devs have chimed in, in this very thread, to confirm as much. They're working on the side (WIP code is not public) and it will be made available "when its ready"; no ETA has been given.Sorry, I'm asking because I don't understand: does this mean that oclp development has stopped or at least suffered a sudden slowdown? That would be a real shame.
macOS Tahoe is probably the biggest challenge that the developers have had yet to make our old legacy Intel Macs work. It WILL probably stop after maybe macOS 27 when intel support ends and I do not think that is my opinion.
I think you're right, but at this point it's probably not worth doing much more than polishing off the current list of work items. Intel MacOS is on borrowed time already and the barrier to entry for Mac hardware is about as low as it has ever been so putting a lot more effort into OCLP is most likely not worth it. I would say it would be better to help support linux development for Apple hardware if for no other reason than to make it slightly more likely that Apple will align its efforts with its users interests rather than just chasing monetization through subscriptions.My suggestion is to commercialize the OCLP app; it could cost $5 or $10... All in all, a small price to pay for giving old Mac models a second life ) I don't know how many potential OCLP users there are, but perhaps... tens of thousands... And that already adds up to a considerable amount for development.
"Probably" was said because if I was too direct, I get wasted arguments from others in responses (writing: where are you getting that information or it is just your opinion - give me support links etc.).Development hasn't stopped. Some devs have chimed in, in this very thread, to confirm as much. They're working on the side (WIP code is not public) and it will be made available "when its ready"; no ETA has been given.
This makes sense. If they make the code public too early, people will run with it and complain when things don't work right or they get themselves into trouble. If they give an ETA, it will just generate anticipation, and complaints if they don't happen to meet it. Even if they were to just post regular status updates, they would be hounded with "Is it done yet?", "Let me try it!", etc... This is the best way for them to operate.
Correct, and there is no "probably" here — macOS 26 is the end of the line for Intel Macs ("supported" or otherwise) and also Hackintoshes. Apple will not produce Intel builds of macOS 27, so it would take way more than fudging with drivers and the bootloader to get that to work on a system with an Intel CPU. (Well, it could be run with a full emulation solution — there is a QEMU project messing with emulated Apple Silicon VMs, for instance — but that's never going to perform great.)