Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Guys please don't hijack this thread to a different topic! Thanks !
 
Guys please don't hijack this thread to a different topic! Thanks !

apologies,

i would be concerned about dGPU though on principle, and first gen, and a bad history

i think discrete retinas had issues, and non retina discrete too, no?

There seems to be a reason Iris Pro was the 15" until this gen again, that and they couldn't get Iris Pro from Intel cause of Skylake or maybe an agreement or something? haven't kept up too well
 
dont mean to derail this thread completely, but how much slower is base 13" 540 Iris graphics over Iris Pro in 2014 and 2015 15"?

And what about the 550 in the touchbar 13" models?

15" old style retina is seeming like more and more of a good deal

15W versus 28W CPU is what I would be concerned with for the base 13" 2016 MBP with no "Touchy Feely Bar" Base model as far as I can see is a replacement for the 13" MBA, not the 2015 MBP...

Q-6
[doublepost=1477855173][/doublepost]
apologies,

i would be concerned about dGPU though on principle, and first gen, and a bad history

i think discrete retinas had issues, and non retina discrete too, no?

There seems to be a reason Iris Pro was the 15" until this gen again, that and they couldn't get Iris Pro from Intel cause of Skylake or maybe an agreement or something? haven't kept up too well

Just think that Intel is not able to deliver the quantiles required as the yield rate is far to low. Far as as I can see Kaby Lake is dropping IRIS, also only Apple really has interest in iGPU which really hung up their hardware releases, equally the Windows OEM`s worked round it....

Also explains Apple`s choice of CPU for the 2015 15" MBP, pity it was released months & months ago.

Q-6
 
15W versus 28W CPU is what I would be concerned with for the base 13" 2016 MBP with no "Touchy Feely Bar" Base model as far as I can see is a replacement for the 13" MBA, not the 2015 MBP...

Q-6
[doublepost=1477855173][/doublepost]

Just think that Intel is not able to deliver the quantiles required as the yield rate is far to low. Far as as I can see Kaby Lake is dropping IRIS, also only Apple really has interest in iGPU which really hung up their hardware releases, equally the Windows OEM`s worked round it....

Also explains Apple`s choice of CPU for the 2015 15" MBP, pity it was released months & months ago.

Q-6

What is the Windows OEM working around it, they too use discrete gpu and they too are prone to failure?

i legit dont know, curious! thanks
 
I currently use a 2012 15" MBP with a dGPU and I've never once had an issue with the dGPU. I think 2011's are the only ones that had any major issues with them and I don't really see that as a reason to doubt all the other model years that never experienced issues. Also its worth noting that Apple went above and beyond to repair 2011's for free.
 
What is the Windows OEM working around it, they too use discrete gpu and they too are prone to failure?

i legit dont know, curious! thanks

Well that`s what I mean, the OEM`s are using the 15W dual cores or some are using the quad core heavy hitters, in conjunction with dGPU. To me the OEM`s are not interested in IRIS graphics. Am only aware of VALIO using the 28W CPU, so understandable why Intel is not pushing it.

Apple`s dream of computing is very much isolated to Apple and Apple is way of the mark on number,s same as Apple Intel will follow the $$$$ :)

Q-6
 
also why would the base 13" be a MBA successor? doesn't it bench very comparably to 2015 base 13" retina?

i see what you mean though, on paper, with a ULV proc

--

related to dGPU in thread, wouldnt integrated and dedicated sacrifice battery v. integrated all the time? seems gfxcardstatus may not work on macOS sierra from reading around

this all would be a concern of mine relative to the dGPU burning out
 
It is interesting to note that the dGPU was designed to work within a 35W power envelope. That is not bad at all and has eased my fears and it will run to hot.
 
i am still on a late 2011 15-inch model here and mine suffered from radeongate in it's third year. i had mostly used it plugged in and in dGPU mode. the failed component was repaired but confidence is gone and i restrict the system to the iGPU most of the time now. will not again consider a dGPU in such a machine so focused on looking slim, especially not another model from AMD.

the difference between i- and dGPU in my experience has been a drastically reduced overall level of heat emission and noise (time before the fans kick in) when relying mostly on the iGPU.

also i'm not too fond of the GPU switching tech and how it makes connecting external displays a bit of a gamble. had lots of issues with mine where it would take quite a while to find the display (and sometimes fail to do so), set up the proper resolution, then not always move the content across. on the other hand this stuff works totally reliable with only one card present (experience with an older macbook).

so, my only upgrade path seems to be the old-style 15-inch. bit of a pill to swallow but as a bonus it does have some useful connectors, unlike the new one. ;) hope they kept magsafe on that model, too. a lifesaver!
 
Well I am not using it but since you are using it you may be correct but on the GFXCARDSTATUS website it also says that "Power source-based switching has been removed" ! What is that ?
That's automatic switch to dGPU when you connect power adapter and to iGPU when you disconnect it.

2.3 still allows you to force either iGPU or dGPU and when selected no software will override it. But once dGPU is selected and you run apps with dependency, you can't force a switch to iGPU before quitting those apps. 2.2.1 doesn't care and can switch any time
 
also why would the base 13" be a MBA successor? doesn't it bench very comparably to 2015 base 13" retina?

i see what you mean though, on paper, with a ULV proc

--

related to dGPU in thread, wouldnt integrated and dedicated sacrifice battery v. integrated all the time? seems gfxcardstatus may not work on macOS sierra from reading around

this all would be a concern of mine relative to the dGPU burning out

Honesty I don't know, however I don't see a 15W CPU competing with a 28W CPU.13: Air is done, replaced by the base MBP sans the "Touchy Feely Bar"

Moving back to gfxcardstatus, I don't see any need for it these days, even the Dev pretty much acknowledges the same. There is clearly room for concern reading the MBO & dGPU, equally options are simple;
  • Purchase MBP & enjoy
  • Purchase MBP & enjoy, concerned so insures against another potential Radeongate
  • Too scared to make a decision, buy`s 13" always wishes had bought the 15" before the massive price hike in 2020
  • Paralysed by thought of unproven hardware failing, asks continuous questions about unproven hardware to people who have no experience of the same hardware, never buys a high end MBP
Roll the dice & live a little :p

Q-6
 
Hi Guys,

Long I have been made to understand that if I want longevity out of my Macbook Pro, If I want the Macbook Pro to last longer I should avoid buying a machine with a dedicated GPU there are too many GPU failures and the fact that it generates too much of heat for the other components to fail on the Motherboard. I am contemplating buying a 15" rMBP one which is the entry level for 2016. But Apple has put me in a Cache 22 situation by only making a 15' rMBP with dedicated GPU. I am now in a fix I dont wanna give up on a 15' rMBP because of the Screen Real Estate. is my fear Justified ? Will My Fear come true ? I am looking to use my Macbook Pro for 5+ Years. Do you guys think the current 15' rMBP with the dedicated GPU may fail or generate too much heat to cause problems for other components on the motherboard to fail. It has happened to me in the past where my Sony Vaio discreet GPU caused my display to go corrupt. Any thoughts ?
I have a 2013 rMBP 15" conected to a Dell 27" monitor and plugged in to power 80% of the time. I have automatic switching turned off unless I go mobile which isn't that often and I honestly have not had any problems. I do however try to keep the ambient room temperature as low as possible throughout the year and in the summer months a make sure to redirect some of my ac air flow towards my MacBook.

I believe if you take care of it and be mindful of your climate and ambient temps (which I think a lot of people disregard) you'll be fine. That being said I've only used Nvidia GPUs in my PCs and just so happens the MacBook Pros I've bought had them too so I can't speak about AMD with any authority.
 
  • Like
Reactions: Queen6
I really wouldn't worry about this. Buy what you actually need.

Sure, the graphics could go bad, but when? I have two mac laptops with discrete gpus and never had a problem, have never monitored anything, and run FCPX and Motion frequently and hard. Sure, that's anecdotal, but since I've never seen anybody present the statistics concerning the actual failure rates of gpu's in Apple laptops, there's really nothing else to compare it to. Anecdotes drive both the good and the bad in this case. If the fail rate is high enough, there will be a recall / replacement program.

Sometimes buying the first generation has its benefits. Things might go wrong but Apple seems very willing to correct it. The original 2012 rMBP had a number of replacement programs that resulted in new motherboards, new screens, etc.
 
  • Like
Reactions: Queen6
I think 2011's are the only ones that had any major issues with them and I don't really see that as a reason to doubt all the other model years that never experienced issues.

There were out-of-warranty "specials" for 2007, 2010, 2011-2013 MBPs with overcooked dGPUs. There's a lot of reasons to doubt LOL
 
That's automatic switch to dGPU when you connect power adapter and to iGPU when you disconnect it.

2.3 still allows you to force either iGPU or dGPU and when selected no software will override it. But once dGPU is selected and you run apps with dependency, you can't force a switch to iGPU before quitting those apps. 2.2.1 doesn't care and can switch any time

So Ver 2.3 of GFXCARDSTATUS will still let me switch between iGPU and dGPU it is just that when I am running some APPs which are on the dependencies list and I switch on to dGPU I cannot again go back to iGPU unless I quit those APPS that's what you are saying right ? Can you give some examples of such APPs which are on the dependency list ? Also is Ver 2.2.1 available for download now ?
 
If you don't need it. Don't buy it. Maybe they'll offer a igpu only 15" variant along with a price drop when the intel igpus are more capable.

As for me. I've only owned MBPs with dgpus and have had no issues.

My workload is pretty GPU intensive and was set to only dgpu for most of the time.
 
examples would be VLC (video player), handbrake, photoshop (when hardware acceleration is enabled), maya, ...

That's sad even for a VLC or a Photoshop a dGPU gets fired up ? That's shocking !!
 
well, you can use the aforementioned utility gfxcardstatus to prevent the system from switching to the dGPU before launching the application of course. with a dGPU present in the system however this also means external displays can not be used until you unlock the dGPU again since it's the one hard wired for video out. iGPU only powers the internal screen on machines that have more than one GPU.
 
well, you can use the aforementioned utility gfxcardstatus to prevent the system from switching to the dGPU before launching the application of course. with a dGPU present in the system however this also means external displays can not be used until you unlock the dGPU again since it's the one hard wired for video out. iGPU only powers the internal screen on machines that have more than one GPU.

That's ok I don't think I would be plugging in an external display to my Mac most of the times.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.