Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Nice! Thanks!!

Now, I'm just curious: What are the 3 icons to the right of your adium in your menubar? I'm always interested in what cool apps are out there that I don't know...

which gives me an idea for a new thread...

Adium, TinyGrab, LittleSnapper.
 
Maybe you should start listing the Apps that DO NOT trigger the 330M.

That looks like a seriously flawed Auto-Switching. They really need to implement an only integrated option in the control panel. It really looks like whenever an application uses any OpenGL or similar API the 330M switches on but in almost all cases the Intel HD will still be sufficient.
VLC or some Mediaplayer that plays XVID, DVD or even h264 does not need 330M. The Intel HD does just fine in everything that does not need heavy 3D power or GPGPU aka OpenCL resources.
If they cannot get it right they should offer a manual option, where you can manage a list of apps that will trigger the 330M maybe select on install if it does trigger any of the APIs.

I hope somebody comes up with a hack that enables manual switching.
 
Maybe you should start listing the Apps that DO NOT trigger the 330M.

That looks like a seriously flawed Auto-Switching. They really need to implement an only integrated option in the control panel. It really looks like whenever an application uses any OpenGL or similar API the 330M switches on but in almost all cases the Intel HD will still be sufficient.
VLC or some Mediaplayer that plays XVID, DVD or even h264 does not need 330M. The Intel HD does just fine in everything that does not need heavy 3D power or GPGPU aka OpenCL resources.
If they cannot get it right they should offer a manual option, where you can manage a list of apps that will trigger the 330M maybe select on install if it does trigger any of the APIs.

I hope somebody comes up with a hack that enables manual switching.

Yeah, it's pretty messy. For example, Espresso doesn't immediately trigger the 330m, but when I was doing "find in files" and scrolling through the results, it would hang for a split second, toggle the 330m on, and never turn it off again until the app quit.
 
iTunes triggers the discrete card when you're using some of the visualizers. Not for all of them, though.
 
I have tried preview and it doesn't pop the 330m for me. It stays on the Intel graphics chip. Someone else may want to do some more testing. There may be something in there that toggles it based on what it is displaying.

Cinch causes the 330m to be loaded almost instantly. Sad, because it is a handy program and I wouldn't think it would take that much video resources.

Not Cinch! :/ please Apple fix this now. And add a settings for Intel HD usage only when on Battery.
 
Not Cinch! :/ please Apple fix this now. And add a settings for Intel HD usage only when on Battery.

The best thing you can do is go to Apple's bug reporter (bugreporter.apple.com) and file an enhancement request.
 
Can anyone confirm if ALL Rosetta apps kick on the discrete?

I still use a PowerPC based graphing app called Graphpad Prism; that automagically turns on the 330M too.
 
When I see all those apps which trigger the discrete gpu even if they are not really graphical intesif apps, I think Apple's implementation of the switching needs some serious updates.
 
someone needs to make a program that forces the use of the internal graphics card. I would gladly pay for that app too..
 
@Tegeril

What is the name of the app or widget that diplays the temp and fan speed on top of your desktop? Thanks.
 
Can a software update solve the problem though?

As Sneakz suggested, what I was really getting at was that it would be best to file an enhancement request to Apple to change the way graphics switching is currently implemented. Sure, an individual application developer can change their code to make fewer calls to the GPU, but the best bet lies with Apple.

This does bring up a bit of a conflict of interest though. Apple is really interested in using the GPU to offload tasks from the CPU to improve performance that the CPU is not designed to perform. What would really be best in my mind is that the current switching method remain with one additional setting, a switch to change between 'favor performance' and 'favor battery life' that would change the criteria that triggers the GPU from a set of GPU calls to a subset of those calls when you choose battery life.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.