Discussion in 'Graphics' started by ElKanyeEast, Aug 17, 2012.
Yes it works fine. I think the newer ones work as well (6970) but i don't have one to test.
Did anyone successfully upgrade to the 660Ti after having previously run FakeSMC? I was running with a 460 with FakeSMC just before getting an Asus 660Ti. I could not get it to work. I tried deleting FakeSMC (was from a 5.02 multibeast install so all the plugins were in that directory), repair permissions, rebuild cache and it'd hang on one of the plugins that I supposedly deleted when I deleted FakeSMC (I double checked to make sure there weren't any orphaned plugin kexts in S/L/E nor in E/E). I restored that version of FakeSMC and just deleted the NVClock kext, rebuilt permissions, rebuilt cache; the best I could get was boot to white screen short of the login screen. Can anyone tell me how I can clear out FakeSMC without having to reload ML from scratch?
It works just fine, you need to remove the Nvidia graphics plugin though, as that will KP in ML. Try booting up in safe mode with KernelCache=No and then reboot.
Do you think the 660TI will ever work with final cut pro? It's important for me.. in the next days I will buy my hackingtosh and I just found this trouble with this card..
is it a matter of time to fix this? and find the right work around?
I wish that a solution could be found. The card works fine and accelerates in Premiere, After Effects, but it crashes the entire OS in FCPX. Tried the card with NeatVideo plugin last night. Neat gives you the option to use either the CPU or GPU or both for rendering the denoiser. Works fine (but slow, even with at new ivybridge core I7 and 16 gigs of memory) on CPU. Neat sees the 660ti for the GPU, but when I choose to use just the GPU or CPU + GPU, it does the checkerboard and locks the system. FCPX definitely has an issue with this card and effects.
Well, I am a professional user, and would like to know how's Imovie doing with this card. JK!!!! lol! Anyways, is your Final Cut using the latest version? The latest version made "compatible with the retina macbook pro" maybe that means compatible with 6xx cards (because of the 650m in the rmbp). Hopefully time will tell. The 670 just dosent seem worth it.
ok. got it working. was looking through the options and hadn't realized that graphicsenabler was enabled with nodsdt settings in multibeast. set option to No and voila! Sure beats all the frustration of trying to get the 550ti to work.
Good point! maybe it's just the latest software who only likes the 6xx cards..
I think their having the same issues with the 670 card as with the 660ti, but after reading a while, the GT640 has no issues at all.. its a slow card, but the best one out there for FCX & Adobe.. with no tweaking around and compatibility troubles... I think!
can somebody check this out?
Well, after all the Open CL Patches and multibeast fixes, how does fcpx work? Thats the question. I feel sad seeing all those builds in the forum named "graphics design build gtx 660" and asking for the final OK. Ive tried as hard as I could to warn them.
Hey guys, I'm back. I do believe that the latest FCPX update should fix the issue of the 600 series crashing on it. Hopefully someone will confirm that. And on another note I do believe the 670 is worth it, just saying
Separate names with a comma.