Interesting. Care to provide some more info about your configuration? smbios system identifier (e.g. iMac 18,3), kext location, other relevant kexts, config.plist, nvidia driver version etc. might help me figure this out. Thanks!
I can confirm that the new releases of the kexts work well, with one major exception: chromium/electron/chrome, which are impossibly slow on my system, forcing me to use `--disable-gpu` for those apps. If anyone has any info (or, even better, a remedy) for this, please share.
I think there's more to this than hackintosh specific configuration. I'm getting exactly the same symptoms on a 'real' MacBook Pro and – judging by a few posts that have appeared online today, including in Apple's own discussion forums, this is not an isolated incident.
Well, from a software compatibility perspective, the OS X API/ABI hasn't changed, so I guess there is no fundamental reason why it shouldn't work, apart from hard-coded checks in the kext (or installer); then again I have no idea how nvidia's kext is built and why they keep limiting their kexts...
Be advised: sadly the 346.03.04f02 drivers still result in constant FCPX crashes, as did 346.03.04f01 and 346.03.03f02. This is not just something that occurs with Hackintoshes; there are reports of this happening with 700 and 900-series cards on various hardware configurations, including...
Be advised that these drivers, like 346.03.03f02 before them, result in always reproducible (and quite frequent) FCPX 10.2.2 crashes on the CVDisplayLink thread (CoreImage/CoreVideo) in some configurations with Maxwell cards (there are reports for 780 and 980Ti, but more may suffer from this)...
Thanks for responding.
The bug doesn't manifest itself immediately, but it consistently crashes FCPX on my box. Typically it will occur during playback when the playhead crosses a transition. Apparently I'm not the only one experiencing this, see...
Has anyone tried (managed) to use FCPX with 346.03.03f02? It consistently causes FCPX to crash on the CVDisplayLink thread. Reverting to f01 resolves this issue and FCPX is usable, but then again that was a very buggy driver in the first place. Reinstalling the driver didn't help. Uninstalling...
I understand the appeal of new hardware to everyone involved in driver creation. Yet I also think that much of the work that you and others have done has little (or in most cases I dare say nothing) to do with the whole 'selling new stuff' priorities that underpin most commercial driver...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.