28145 Views Previous 1 2 3 4 5 6 Next 78 Replies Latest reply: Jan 15, 2011 5:42 PM by BiG Hurt Go to original post
You have got another happy user here! Thanks.
- instead of having this ad hoc list here in the forum would it be an idea to make gfxCardStatus gather the names of apps that cause switching to Nvidia and then sending this list to some central place regularly?
- furthermore an 'expert-group' could judge which apps indeed need hardcore 3D performance and which ones do not and annotate the list as such.
- then gfxCardStatus could have another mode (e.g. "community mode") that would listen to this list rather then the apps themselves. This would greatly enhance battery life and reduce annoyance.
I have Chrome running almost all of the time, which makes me a constant Nvidia user. I do to switch manually all the time. The above scheme would be ideal for me.
Thank you H3lix! That's a wonderful tip!
Now if the Skype programmers could just get their act together and make it so that it doesn't use the nVidia stuff at all. After all, if DVD Player can operate on intel graphics, video chat should be able to.
Or, if for some reason, they need the power of the nVidia chip for their video codecs or whatever, H3lix's tip has shown that it shouldn't be that hard for them to tweak things so that the nVidia chip is only activated when a video call is actually in progress.
Here's the whole list to date, from above:
Data Rescue 3.0.2
Default Folder X 4.3.7
Drive Genius 3
Evernote (in thumbnail view only)
Fractal Clock Screen Saver
Google Voice & Video plugin
Marine Aquarium 3 (Screen Saver)
Microsoft Office 2004
Microsoft Office AutoUpdate daemon
Missing sync for symbian
MS Office Messenger 2008
Parallels 5 Desktop
Photoshop Elements 4
QuickTime Player 7
Skim (after searching)
Skype, if video is enabled
Toast Titanium v 8.0.5
VMware Fusion 3
VMWare Fusion 3 (gfx acceleration disabled)
X11 or Xquartz
It's not completely a matter of the developers of these apps getting their act together (disclosure: I am the developer of Hyperspaces). It's pretty clear to me at this point the technical reasons for the discrete graphics card being activated (it's Core Animation in most cases), but it's not as easy to solve. Apple has encouraged developers to use Core Animation extensively over the last few years, and it's not always easy to replace it with standard, non Core Animation drawing.
I know some of us have tried (and some have succeeded), but doing this in Hyperspaces almost doubled the amount of work I had to do originally - even in the "sloppy" fashion that I did. Just don't assume things "shouldn't be that hard".
In my mind, it would be better if Apple handed back some control of graphics card selection to users as with previous MacBooks - it's obviously bothering you guys, and it's quite a bit of work for some of us to go back and retrofit our apps after Apple espoused the amount of code we'd save by using Core Animation and other accelerated graphics technologies in the first place.
Auto-switching seems to be a great idea in theory, but the reality is a bit wonky.