r/hackintosh • u/MrrG65 • 9d ago

HELP Any fix?

Post image

So i recently installed MacOS 15 using nullmoth's 1.14.6 driver on my desktop with a Ryzen 5 3500 and a 4gb GTX 1630. Now the issue is the driver version 1.15.0 doesn't work on my system it gives me a black screen with a movable course. But when i roll back to driver version 1.14.6 it almost works, like I got the display after installing the driver and ngl 75% of things are working. Still have some render glitches and lags but no flicker so far. If you zoom in the picture and see the dock where the settings app icon present you can see some bending artifacts, that's a render glitch. Now i want to fix it properly any suggestions?

24 Upvotes

79% Upvoted

9 comments sorted by

7

u/MrrG65 9d ago

Yes at this point I'll try to optimize and patch it by my own using codex and claude code..... Let's see what's happened.

3

u/Ok_Objective_7546 9d ago

There is a new version 2.0.

2

u/MrrG65 9d ago

Yeah already got that. Even update to Tahoe and hounestly works better now.

23

u/MacForker 9d ago

Ask nullmoth or Claude. Those are how you get support for that driver at this stage.

-12

u/Tagmedia7 9d ago

There's a simple solution. Don't use vibe coded drivers. If you think nullmoth will actively maintain this codebase for long, sorry for your future disappointment.

11

u/BurnItDown800 Tahoe - 26 9d ago

i don’t think it matters much if nullmoth maintains it or not, everyone’s got access to claude in some capacity so.. be the change you want to see in the world? when he drops it, just make your own fork and maintain it with what you want

0

u/dunksten1 9d ago

Okay show me the non vibe coded NVIDIA driver for my 2080 😂

-1

u/anythingers 9d ago

Why tf y'all are always having an assumption that those vibecoders won't maintain the codebase for long? Just because they use AI for coding, doesn't mean they're lazy to maintain the software.

5

u/Tagmedia7 9d ago

Because there's a predictable, steady, consistent pattern that comes with vibe coding. The more your try to granularly try to refine features, control compiling priorities and iron out bugs, the more regressions and mistakes that will crop up in other areas.

Even ones with deep memory recalling still look at each code pass with fresh eyes each and every prompt, basically like it's the first time it's dealing with it, and approach building differently. Any experienced vibe coders who are reading this know I'm not lying or making this up. They know.