I don't. I only asked because there is a bug with this version and he knows it. I set it to Intel Only then view a youtube video Full screen and that automatically triggers the 330m. He said a while back a new version would be coming soon so I just thought I'd ask.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Found way to know what GPU is in use!
- Thread starter gatepc
- Start date
- Sort by reaction score
I don't. I only asked because there is a bug with this version and he knows it. I set it to Intel Only then view a youtube video Full screen and that automatically triggers the 330m. He said a while back a new version would be coming soon so I just thought I'd ask.
I have basically the same rig as you (except for the HD) and I am having the same problem...I set it for Intel Only, then I use Chrome and it reverts back to the NVIDIA and disappears from my toobar...
I am having the same problem...I set it for Intel Only, then I use Chrome and it reverts back to the NVIDIA and disappears from my toobar...
Google must have issued some update to Chrome recently, because Chrome no longer uses the Nvidia--none of its processes appear on gfxCardStatus' Dependency list anymore. It activates Intel with Dynamic Switching on.
Interesting - I always make a point to switch to the Intel GPU before I use Chrome so I haven't noticed. Hopefully it stays that way.
MattMJB0188 said:
I'll give the nebulous answer, "when it's done."
As soon as I can find the time to just sit down and actually work on it, I can release it. Today, for example...I was gone literally the entire day, until just now. I may just push out a release really quick that fixes that bug, and then push out another maintenance release shortly thereafter. There are a bunch of things on my list that I want to check out, but maybe I don't necessarily have to do them all at once. Soon, don't worry. Ronnoco said:I have basically the same rig as you (except for the HD) and I am having the same problem...I set it for Intel Only, then I use Chrome and it reverts back to the NVIDIA and disappears from my toobar...
Have you tried redownloading it? Usually that fixes problems like the disappearing you mentioned. The reverting should be fixed in the maintenance release I mentioned above.
Thanks!
Cody
One thing i just noticed - for the first time i plugged an external monitor in but closed the lid of the mbp (15" hires) and used a keyboard/mouse to wake the machine and run the external monitor (19" LG, using Apple's mini DP->vga adaptor). So it's running in 'clamshell mode'
It says there are no dependancies and still runs the nVidia.
I know if you use an external monitor with the laptop it uses the 330 but it lists 'External Display' under Dependencies. In this scenario (mbp screen off), it does not.
So when the MBP is working in clamshell mode, either:
1) It should say 'External Display' and use the nVidia or
2) The MBP should free up the 330 and use the intel HD on the external monitor.
Perhaps there's a bug in the MBP firmware which doesn't allow option '2' to work. I tried to force the intel and it didn't work, which makes me think it's option '1' above.
Sorry if this has been brought up before, but it's quite a long thread!
Thanks!
Eddie
It says there are no dependancies and still runs the nVidia.
I know if you use an external monitor with the laptop it uses the 330 but it lists 'External Display' under Dependencies. In this scenario (mbp screen off), it does not.
So when the MBP is working in clamshell mode, either:
1) It should say 'External Display' and use the nVidia or
2) The MBP should free up the 330 and use the intel HD on the external monitor.
Perhaps there's a bug in the MBP firmware which doesn't allow option '2' to work. I tried to force the intel and it didn't work, which makes me think it's option '1' above.
Sorry if this has been brought up before, but it's quite a long thread!
Thanks!
Eddie
Yeah - external monitors require the 330M regardless of whether it's in clamshell mode or not. The Mini DisplayPort output is wired exclusively to the 330M, so there's no possibility of a firmware/software fix to use the Intel GPU with external monitors. The external display thing is something I still need to fix.
On another note, I did just fix the problem where it switches back after you quit all 330M apps. At least, I haven't been able to reproduce it since I intro'd the fix, so I assume it's fixed. Should be ready to go in a couple days.
I'm also noticing that when I shut down the computer with GFX opened its somehow turning off Apple's automatic graphic switching because I always have to re check that when I restart my computer. I launch GFX and its automatically on N then once I select apple's automatic graphic switching via energy saver its fine. Is this a known bug?
I then closed the program and restarted and apple's automatic graphic switching was enabled.
I then closed the program and restarted and apple's automatic graphic switching was enabled.
Bug report:
Using v1.7 on 15" Corei7
I am seeing the same issue here. Locking the GPU to Intel and launching either of the follwing: Photoshop, Illustrator, Skype, Iphotos, VirtualBox will keep the Intel GPU on (as seen from Istat). But quiting any one of them will change GPUs to NVIDIA (Growl notification and iStat shows the switch). At which point I'll have to choose dynamic option to revert it back to Intel (confirmed from iStat again).
Thanks, no problem.
MattMJB0188 said:
The turning off of the graphics switching I'm aware of, yes, but it's not a bug - that's so OS X doesn't get confused and think that it has control, and then switches the GPU on you unsuspectingly.
There will be a pref to remember the last mode you used before quitting and use that at startup in the next version. I'm aiming for later tonight or tomorrow for a quick release. Still some stuff to fix, but I want to get a couple bugfixes out the door as well.zanax said:
Yep, this should be fixed shortly. Keep your mice positioned over the 'Check for Updates' menu item!
Thanks, no problem.
The turning off of the graphics switching I'm aware of, yes, but it's not a bug - that's so OS X doesn't get confused and think that it has control, and then switches the GPU on you unsuspectingly.
Yep, this should be fixed shortly. Keep your mice positioned over the 'Check for Updates' menu item!
Thanks!!! Greatly Appreciated
Thanks, no problem.
The turning off of the graphics switching I'm aware of, yes, but it's not a bug - that's so OS X doesn't get confused and think that it has control, and then switches the GPU on you unsuspectingly.
Yep, this should be fixed shortly. Keep your mice positioned over the 'Check for Updates' menu item!
Thanks, I am eagerly looking forward to it. Albeit the current workaround I still love the app you created.
Hey Cody, one small thing and it has nothing to do with code! You might want to put a small thin white outline around the Application icon. When you have a dark wallpaper and are in grid mode, the icon is almost invisible. When its against a white background inside of finder, the outline should look look fine too!
Attachments
Yep - it's on my list of things to do.
EDIT: Strike that, it's fixed. ~2px white stroke around the edge, subtle gradient over the whole thing.
Drum roll please...*drum roll*
v1.7.5 is out! This should fix the issue with switching back to the 330M after all dependent apps have quit. Also *properly* detects external monitors (even in clamshell mode!) using a (much) more accurate and low-level method, revised the logo (see above post), and added French localization (minus one string in the prefs). AND...it remembers the last mode you used before you quit, if you desire. Go into the prefs to turn it off if you don't want it to restore upon startup.
As always previous versions are available at http://codykrieger.com/gfxCardStatus/gfxCardStatus-<version>.zip
Comments and suggestions are welcome! Let me know how it works for everyone.
Thanks!
Cody
v1.7.5 is out! This should fix the issue with switching back to the 330M after all dependent apps have quit. Also *properly* detects external monitors (even in clamshell mode!) using a (much) more accurate and low-level method, revised the logo (see above post), and added French localization (minus one string in the prefs). AND...it remembers the last mode you used before you quit, if you desire. Go into the prefs to turn it off if you don't want it to restore upon startup.
As always previous versions are available at http://codykrieger.com/gfxCardStatus/gfxCardStatus-<version>.zip
Comments and suggestions are welcome! Let me know how it works for everyone.
Thanks!
Cody
Great update, Cody.
Just wanna add a caveat to a recent post of mine saying Chrome no longer uses the Nvidia: it uses it most times you starting downloading something. And stays that way unless you force Intel-only or restart the browser.
Just wanna add a caveat to a recent post of mine saying Chrome no longer uses the Nvidia: it uses it most times you starting downloading something. And stays that way unless you force Intel-only or restart the browser.
Drum roll please...*drum roll*
v1.7.5 is out! This should fix the issue with switching back to the 330M after all dependent apps have quit. Also *properly* detects external monitors (even in clamshell mode!) using a (much) more accurate and low-level method, revised the logo (see above post), and added French localization (minus one string in the prefs). AND...it remembers the last mode you used before you quit, if you desire. Go into the prefs to turn it off if you don't want it to restore upon startup.
As always previous versions are available at http://codykrieger.com/gfxCardStatus/gfxCardStatus-<version>.zip
Comments and suggestions are welcome! Let me know how it works for everyone.
Thanks!
Cody
Thanks so much for your hard work!
Yeh, it must be something to do with the download bar at the bottom, whenever it pops up the discrete GPU kicks in...
Thx Cody for your hard work.
New version! w00t!!
Thanks!
mixvio said:
No problemo.
Just doing what I love!aapl2010 said:
Sure thing!
I've probably missed someone posting this earlier in the thread, but how are folks determining if the 330M has actually shut off? I took a look at the voltage usage using iStat menus, but it's showing 0 for both GPUs.
http://neil.io/13Z0cf+
This is on a MBP 15", i7.
http://neil.io/13Z0cf+
This is on a MBP 15", i7.
Thank you so much for that big help for the mbp users that have 2010 spring models and previous ones, you are very good!!!
Hi Cody,
I am a new Mac user here and I love the app you made for all of us 2010 MBP users. I know the point of changing to 'Intel Only' is to increase battery time, but it's not the case for me. While using Tweetie and forcing Intel, I get a lower estimated 'battery remaining' than when i leave it at 'Dynamic Switching'. Am I doing something wrong?
I am a new Mac user here and I love the app you made for all of us 2010 MBP users. I know the point of changing to 'Intel Only' is to increase battery time, but it's not the case for me. While using Tweetie and forcing Intel, I get a lower estimated 'battery remaining' than when i leave it at 'Dynamic Switching'. Am I doing something wrong?
Just tried out forcing Intel with v1.75. In 1.70, when watching a flash video fullscreen in Safari, it would still switch over to the 330M and then stay there when you quit fullscreen mode.
Now it appears to stay on Intel all the time, but after quitting fullscreen, v-sync is disabled.
I noticed before that v-sync was always disabled when running on the nvidia graphics but enabled on Intel and somehow by forcing Intel this has disabled it there as well. (at least after running something that would normally trigger the nvidia graphics)
Anyone else noticed this?
Now it appears to stay on Intel all the time, but after quitting fullscreen, v-sync is disabled.
I noticed before that v-sync was always disabled when running on the nvidia graphics but enabled on Intel and somehow by forcing Intel this has disabled it there as well. (at least after running something that would normally trigger the nvidia graphics)
Anyone else noticed this?