I managed to do the same thing in the apple store, switching cards and resolutions quickly made this happen
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.
gfxcardstatus for rMBP
- Thread starter Pagga
- Start date
- Sort by reaction score
I managed to do the same thing in the apple store, switching cards and resolutions quickly made this happen
Power source-based switching is pretty buggy right now (especially in v2.2.1). I actually recommend turning it off if you're using Mountain Lion now, since the OS is much more friendly in terms of when it switches GPUs. You should just be able to use gfxCardStatus in Dynamic Switching mode and leave it there at this point, and trust that if an app kicks on the discrete GPU, it's probably doing it for good reason.
----------
Anything that accesses your iSight camera will kick the discrete GPU on as well, which is actually pretty reasonable, because the integrated GPU can struggle to keep up with iSight video + effects (if you're using Messages or Photo Booth or something).
If you keep Skype running all the time, though, I can see how it would be annoying. Truth be told I really despise Skype, so usually when people ask me to chat with it...I'll either tell them to call me, use AIM or Gtalk, or not talk to me at all. Heh.
----------
You bet.
----------
That makes a lot of sense. I'm adding something in v2.3 that makes sure only one GPU switch can be ordered at one time. It's very likely that the extremely small amount of time in between switches caused the graphical artifacts and rendering issues.
I did see in the source code pages that you had merged some code for notification center into the build. Any eta for general or beta release? I have no plans on using growl for this OS and I would love to see gfx integrated into the nc.Power source-based switching is pretty buggy right now (especially in v2.2.1). I actually recommend turning it off if you're using Mountain Lion now, since the OS is much more friendly in terms of when it switches GPUs. You should just be able to use gfxCardStatus in Dynamic Switching mode and leave it there at this point, and trust that if an app kicks on the discrete GPU, it's probably doing it for good reason.
----------
Anything that accesses your iSight camera will kick the discrete GPU on as well, which is actually pretty reasonable, because the integrated GPU can struggle to keep up with iSight video + effects (if you're using Messages or Photo Booth or something).
If you keep Skype running all the time, though, I can see how it would be annoying. Truth be told I really despise Skype, so usually when people ask me to chat with it...I'll either tell them to call me, use AIM or Gtalk, or not talk to me at all. Heh.
----------
You bet.
----------
That makes a lot of sense. I'm adding something in v2.3 that makes sure only one GPU switch can be ordered at one time. It's very likely that the extremely small amount of time in between switches caused the graphical artifacts and rendering issues.
Power source-based switching is pretty buggy right now (especially in v2.2.1). I actually recommend turning it off if you're using Mountain Lion now, since the OS is much more friendly in terms of when it switches GPUs. You should just be able to use gfxCardStatus in Dynamic Switching mode and leave it there at this point, and trust that if an app kicks on the discrete GPU, it's probably doing it for good reason.
----------
Anything that accesses your iSight camera will kick the discrete GPU on as well, which is actually pretty reasonable, because the integrated GPU can struggle to keep up with iSight video + effects (if you're using Messages or Photo Booth or something).
If you keep Skype running all the time, though, I can see how it would be annoying. Truth be told I really despise Skype, so usually when people ask me to chat with it...I'll either tell them to call me, use AIM or Gtalk, or not talk to me at all. Heh.
----------
You bet.
----------
That makes a lot of sense. I'm adding something in v2.3 that makes sure only one GPU switch can be ordered at one time. It's very likely that the extremely small amount of time in between switches caused the graphical artifacts and rendering issues.
I had to run skype for work and some of my contacts there are still using it, so I just leave it on. If its a badly written resource hog tho, I will stop running it.
gfxCardStatus was basically created on these forums way back in April/May of 2010, so I try to answer questions at least every once in a while.
----------
Tentatively this week...super, super busy right now, but there are some other fixes I need to get pushed out as well, so hopefully in the next couple of days.
----------
If it's something that you use enough, I'd definitely shoot an email to the Skype folks and tell them to get their act together and make it stop using the discrete GPU, because that's on them for not fixing it until now.
If I recall correctly, it's been an issue since day one of the automatic switching MBPs.While not widely reported, I was experiencing some sleep issues when gfxcardstatus was installed on my rMBP while running OSX 10.7. I'm happy to report that things appear to be working much better since installing 10.8 over the weekend. Can't wait for the next version to come out; the sooner I can get all my notifications to have a common appearance the better.
While not widely reported, I was experiencing some sleep issues when gfxcardstatus was installed on my rMBP while running OSX 10.7. I'm happy to report that things appear to be working much better since installing 10.8 over the weekend. Can't wait for the next version to come out; the sooner I can get all my notifications to have a common appearance the better.
use the program hiss. takes all growl notifications and turns them into notification center ones. awesome little tweak!
While not widely reported, I was experiencing some sleep issues when gfxcardstatus was installed on my rMBP while running OSX 10.7. I'm happy to report that things appear to be working much better since installing 10.8 over the weekend. Can't wait for the next version to come out; the sooner I can get all my notifications to have a common appearance the better.
I've already got Notification Center support in the code. Just need to push out the v2.3 update once I've got a few more fixes in place.
There's really no point to that, you might as well just leave it on Dynamic Switching and at least save some power and keep things cool.
I'm on discreet most of the time the MBP is plugged in, but then I have my MBP connected to an external monitor, so it needs to be on the discrete to drive that bad boy.
I find that I never really use gfxcardstatus. Its nice to have utility for just in case needs, but so far I'm happy with how the OS handles the switching.