|
|
Post by mikethebigo on Aug 29, 2020 23:21:55 GMT
Have you considered the general IT call you get is not from the same type of person that browses a custom GPU firmware site? I’m not going to keep arguing with your ego. I have, multiple times, installed correctly. January worked. April and August have not. Page 1 of this thread is full of people who you say can’t figure out safe mode who are clearly doing DDU on the fly driver swaps. For whatever reason, it isn’t working on some machines. I would not trust anyone in technical support who genuinely believed that a driver working on one particular machine and configuration means it MUST work on all. You are missing the point. If its broke for you, then you are doing something wrong. Not me. Its working on my W10 pro 2004. So my ego and my technical skills seem to be superior since its working for me. I bet you $1000 I could scratch load W10 pro on your machine and have the August drivers working flawlessly within 20 minutes. Have you tried that?? Because thats what I would do and have done. When dealing with custom software like this, always be ready to reload at a moments notice. I could help you solve your issues if you want... I did do fresh install with April drivers, twice, without success. Others have as well. I have not had time to do a fully fresh Windows install (and game installation) yet with these. I will give it a go. But again, when dealing with something as complex as computer drivers it is absolutely insane (and rather toxic) to say the only possible point of failure is the intelligence of the user, and not an issue elsewhere with hardware or software. I won't argue further today, I don't feel like this is productive. |
|
|
|
Post by stallhagen on Aug 29, 2020 23:23:41 GMT
Mat. I've watched all those videos and tried all those tweaks. I really wanted this to be my all around gaming machine, but its just flawed to the core. Im sitting here watching my AB overlay showing the GPU only getting 20w and its sitting at 500mhz in GTAV. WHY is it doing that? The temp is 74c and its 99% maxed out utilization. This is a 55w GPU and should be pegged at 50+ watts and 1200mhz or more when its within its temp range. Yet for some reason its not. This is the problem and I just dont know how to fix it. Man I wish I could talk to an apple engineer about this. The best solution I've found for throttling so far is to go to Power Options and set it to Balanced mode with Max Processor at 80%. Played Warzone for 3 hours last night without any throttling and that game is both CPU and GPU heavy so they both run hot which heats up the VRMs too. Setting it to 80% will decrease CPU performance but not affect gaming in a significant way. My Heaven benchmark went from 2270 to 2245. I also have the fans at full blast and a small desk fan pointed at the vents the whole time. Will try with the new drivers tonight. |
|
|
|
Post by zxmustang on Aug 29, 2020 23:56:47 GMT
Mat heres a question. When are we going to get the GPU scheduler option in windows with your drivers? It doesnt appear even with your new Red drivers, that option still doesnt show up. This would help a lot with the performance of the 4gb and less VRAM cards. Its only available with 2004 windows and the latest AMD driver.  |
|
|
|
Post by mikethebigo on Aug 30, 2020 2:01:27 GMT
Have you considered the general IT call you get is not from the same type of person that browses a custom GPU firmware site? I’m not going to keep arguing with your ego. I have, multiple times, installed correctly. January worked. April and August have not. Page 1 of this thread is full of people who you say can’t figure out safe mode who are clearly doing DDU on the fly driver swaps. For whatever reason, it isn’t working on some machines. I would not trust anyone in technical support who genuinely believed that a driver working on one particular machine and configuration means it MUST work on all. You are missing the point. If its broke for you, then you are doing something wrong. Not me. Its working on my W10 pro 2004. So my ego and my technical skills seem to be superior since its working for me. I bet you $1000 I could scratch load W10 pro on your machine and have the August drivers working flawlessly within 20 minutes. Have you tried that?? Because thats what I would do and have done. When dealing with custom software like this, always be ready to reload at a moments notice. I could help you solve your issues if you want... OK, just did the whole thing, again. Procedure: - Downloaded Win 10 64 bit from Microsoft site - Ran Boot Camp Assistant. Selected space, correct ISO. Ran the program. - Booted into Windows installation, picked Windows 10 Pro, completed the entire setup process - Installed Boot Camp software, rebooted - Went to Windows Update, downloaded all, installed, rebooted - Went straight to this site, downloaded the driver. - Extracted the driver into folder - Ran DDU and made sure no update available - Rebooted while holding shift, selected correct startup options - After reboot, selected "4" for Safe Mode, booted in - Found folder, ran DDU, followed all checkbox instructions from video on the front page of bootcampdrivers.com - Ran x 3, twice was clean and no reboot, third clean and reboot. They fully completed all 3 cycles - Booted back into W10. Ran setup.exe. Installed the driver. Rebooted. - Downloaded Steam. Downloaded Destiny 2. Launched. Initially ran, and then the first time I tried to change resolution in settings: black screen, total crash to shutdown. So, where along this process did I not follow the correct steps? |
|
|
|
Post by sourkimchi on Aug 30, 2020 2:02:04 GMT
You are missing the point. If its broke for you, then you are doing something wrong. Not me. Its working on my W10 pro 2004. So my ego and my technical skills seem to be superior since its working for me. I bet you $1000 I could scratch load W10 pro on your machine and have the August drivers working flawlessly within 20 minutes. Have you tried that?? Because thats what I would do and have done. When dealing with custom software like this, always be ready to reload at a moments notice. I could help you solve your issues if you want... I did do fresh install with April drivers, twice, without success. Others have as well. I have not had time to do a fully fresh Windows install (and game installation) yet with these. I will give it a go. But again, when dealing with something as complex as computer drivers it is absolutely insane (and rather toxic) to say the only possible point of failure is the intelligence of the user, and not an issue elsewhere with hardware or software. I won't argue further today, I don't feel like this is productive. To put an end to this discussion once and for all: I have a MacBook pro 16" 5500m 4gb and I always ran into the black screen problem with April Red/Blue drivers. The logic board failed on me a month ago and I sent it into apple to fix it and they put in a brand new logic board. Now the April Red/Blue drivers run flawlessly. I believe some 5500m cannot run the 1500mhz the memory clock is set at on the April drivers (silicon lottery). I believe the Jan Red/Blue drivers have the memory clock set at 1482mhz or something. |
|
|
|
Post by mikethebigo on Aug 30, 2020 2:05:53 GMT
I did do fresh install with April drivers, twice, without success. Others have as well. I have not had time to do a fully fresh Windows install (and game installation) yet with these. I will give it a go. But again, when dealing with something as complex as computer drivers it is absolutely insane (and rather toxic) to say the only possible point of failure is the intelligence of the user, and not an issue elsewhere with hardware or software. I won't argue further today, I don't feel like this is productive. To put an end to this discussion once and for all: I have a MacBook pro 16" 5500m 4gb and I always ran into the black screen problem with April Red/Blue drivers. The logic board failed on me a month ago and I sent it into apple to fix it and they put in a brand new logic board. Now the April Red/Blue drivers run flawlessly. I believe some 5500m cannot run the 1500mhz the memory clock is set at on the April drivers (silicon lottery). I believe the Jan Red/Blue drivers have the memory clock set at 1482mhz or something. Impossible. He has 20 years of IT experience and he knows it couldn't be hardware variation. You must have just been doing it wrong, every time, with the old motherboard. Only possible answer. Also, if it were the memory clock speed, would it make sense that I could boot fine into Destiny 2 when it launched at full native res, but then changing to something like 1920x1200 would immediately crash it? If anything I would expect that to alleviate memory pressure. |
|
|
|
Post by sourkimchi on Aug 30, 2020 2:22:41 GMT
To put an end to this discussion once and for all: I have a MacBook pro 16" 5500m 4gb and I always ran into the black screen problem with April Red/Blue drivers. The logic board failed on me a month ago and I sent it into apple to fix it and they put in a brand new logic board. Now the April Red/Blue drivers run flawlessly. I believe some 5500m cannot run the 1500mhz the memory clock is set at on the April drivers (silicon lottery). I believe the Jan Red/Blue drivers have the memory clock set at 1482mhz or something. Impossible. He has 20 years of IT experience and he knows it couldn't be hardware variation. You must have just been doing it wrong, every time, with the old motherboard. Only possible answer. Also, if it were the memory clock speed, would it make sense that I could boot fine into Destiny 2 when it launched at full native res, but then changing to something like 1920x1200 would immediately crash it? If anything I would expect that to alleviate memory pressure. Yea, it could be something completely different! I just noticed one thing that was different, but I'm no expert. |
|
|
|
Post by mark on Aug 30, 2020 2:27:56 GMT
Never got the Red version working with my iMac 2017 with the RX580, but they are working on the iMac 2020 with the 5700, and got a nice boost on 3dMark from the 6000s to the 7000s over the default bootcamp drivers. Thanks! |
|
|
|
Post by zxmustang on Aug 30, 2020 2:32:35 GMT
You are missing the point. If its broke for you, then you are doing something wrong. Not me. Its working on my W10 pro 2004. So my ego and my technical skills seem to be superior since its working for me. I bet you $1000 I could scratch load W10 pro on your machine and have the August drivers working flawlessly within 20 minutes. Have you tried that?? Because thats what I would do and have done. When dealing with custom software like this, always be ready to reload at a moments notice. I could help you solve your issues if you want... OK, just did the whole thing, again. Procedure: - Downloaded Win 10 64 bit from Microsoft site - Ran Boot Camp Assistant. Selected space, correct ISO. Ran the program. - Booted into Windows installation, picked Windows 10 Pro, completed the entire setup process - Installed Boot Camp software, rebooted - Went to Windows Update, downloaded all, installed, rebooted - Went straight to this site, downloaded the driver. - Extracted the driver into folder - Ran DDU and made sure no update available - Rebooted while holding shift, selected correct startup options - After reboot, selected "4" for Safe Mode, booted in - Found folder, ran DDU, followed all checkbox instructions from video on the front page of bootcampdrivers.com - Ran x 3, twice was clean and no reboot, third clean and reboot. They fully completed all 3 cycles - Booted back into W10. Ran setup.exe. Installed the driver. Rebooted. - Downloaded Steam. Downloaded Destiny 2. Launched. Initially ran, and then the first time I tried to change resolution in settings: black screen, total crash to shutdown. So, where along this process did I not follow the correct steps? You didnt run DDU in windows safe mode... Edit: No I see you did. I miss read your steps. All I can think of is putting your system in 1920x1200 native. Thats what I do. There is no sense in putting windows in native. It will scale it by default unless you put it back to 100% scale, and no game unless its an old or very low resource ask game is going to run at anything worth playing at native resolution. Im only asking my machine for 1920x1200@60fps. I have been willing to lower settings to achieve this, but it just throttles and throttles as I play after 15-20 minutes. So I keep lowering until then I have to lower the resolution scale in game where available. But I would set windows to 1920x1200 and make it 100% scale. And I asked, but who knows if he'll answer about being able to use the GPU scheduling option in windows when you are using the most current AMD driver. |
|
|
|
Post by mikethebigo on Aug 30, 2020 2:39:10 GMT
OK, just did the whole thing, again. Procedure: - Downloaded Win 10 64 bit from Microsoft site - Ran Boot Camp Assistant. Selected space, correct ISO. Ran the program. - Booted into Windows installation, picked Windows 10 Pro, completed the entire setup process - Installed Boot Camp software, rebooted - Went to Windows Update, downloaded all, installed, rebooted - Went straight to this site, downloaded the driver. - Extracted the driver into folder - Ran DDU and made sure no update available - Rebooted while holding shift, selected correct startup options - After reboot, selected "4" for Safe Mode, booted in - Found folder, ran DDU, followed all checkbox instructions from video on the front page of bootcampdrivers.com - Ran x 3, twice was clean and no reboot, third clean and reboot. They fully completed all 3 cycles - Booted back into W10. Ran setup.exe. Installed the driver. Rebooted. - Downloaded Steam. Downloaded Destiny 2. Launched. Initially ran, and then the first time I tried to change resolution in settings: black screen, total crash to shutdown. So, where along this process did I not follow the correct steps? You didnt run DDU in windows safe mode... As my steps make clear, I did boot into safe mode and ran it there. Black background, “safe mode” in the corner. Absolutely was in the correct mode. |
|
|
|
Post by zxmustang on Aug 30, 2020 2:41:09 GMT
You didnt run DDU in windows safe mode... As my steps make clear, I did boot into safe mode and ran it there. Black background, “safe mode” in the corner. Absolutely was in the correct mode. Yeah that was my bad I misread. I edited my post with that, and put some more info in to maybe help you. Look instead of a pissing contest, i'd prefer to help where I can. Im happy to. But to blanket state that the drivers are broken, this I can tell you they are not. |
|
|
|
Post by mikethebigo on Aug 30, 2020 2:47:12 GMT
As my steps make clear, I did boot into safe mode and ran it there. Black background, “safe mode” in the corner. Absolutely was in the correct mode. Yeah that was my bad I misread. I edited my post with that, and put some more info in to maybe help you. Look instead of a pissing contest, i'd prefer to help where I can. Im happy to. But to blanket state that the drivers are broken, this I can tell you they are not. Of course, and I never said you were lying. I believe they’re working fine for you. But they are not working fine for everyone. So all other things being equal, my guess is again that there is some hardware variance at play here, where some systems are tolerating the drivers better than others. It’s the only real answer. It’s just probably going to be very hard to figure out what that difference is. But this is not user error and it was wrong for you to insinuate that it had to be. As the guy above noted, a motherboard replacement actually changed how his Mac tolerated the drivers. The game crashes regardless of what resolution windows is running at. It runs in Fullcreen so it changes the resolution on launch anyway and stops rendering the Windows desktop. |
|
|
|
Post by zxmustang on Aug 30, 2020 3:00:59 GMT
Yeah that was my bad I misread. I edited my post with that, and put some more info in to maybe help you. Look instead of a pissing contest, i'd prefer to help where I can. Im happy to. But to blanket state that the drivers are broken, this I can tell you they are not. If course, and I never said you were lying. I believe they’re working fine for you. But they are not working fine for everyone. So all other things being equal, my guess is again that there is some hardware variance at play here, where some systems are tolerating the drivers better than others. It’s the only real answer. It’s just probably going to be very hard to figure out what that difference is. But this is not user error and it was wrong for you to insinuate that it had to be. As the guy above noted, a motherboard replacement actually changed how his Mac tolerated the drivers. The game crashes regardless of what resolution windows is running at. It runs in Fullcreen so it changes the resolution on launch anyway and stops rendering the Windows desktop. I dont believe it was wrong for me to insinuate that this had or could be user error. This is the internet and we are not dealing with millions of desktop support specialists here. Just read most of the reddit threads, or FB group posts or even forum threads like this. There are idiots all over the planet with these and similar issues trying to make this model macbook pro a gaming machine. There is misinformation running rampant on youtube about all these snake oil software programs and even people modifying their machines to stop issues like this. Its everywhere. There are pages and pages of morons on apple support asking the same questions and getting like 098 computer class answers, where most are incorrect. There is nodoubt that most and Im being generous here, are caused by user error plain and simple. Work a day in any level of IT support and you will see it first hand. All walks of life are buying these and trying to make this crap work. And its a big enough learning curve that just about every social media site, and hundreds of pages of forums from all over the internet are talking about how and where to find these drivers, and how to make them work. |
|
|
|
Post by zxmustang on Aug 30, 2020 3:03:12 GMT
And on that Im backing out of this. I wanted to help, but mine is working (shitily) and I dont know what to tell you guys. -out.
|
|
|
|
Post by mikethebigo on Aug 30, 2020 3:09:23 GMT
If course, and I never said you were lying. I believe they’re working fine for you. But they are not working fine for everyone. So all other things being equal, my guess is again that there is some hardware variance at play here, where some systems are tolerating the drivers better than others. It’s the only real answer. It’s just probably going to be very hard to figure out what that difference is. But this is not user error and it was wrong for you to insinuate that it had to be. As the guy above noted, a motherboard replacement actually changed how his Mac tolerated the drivers. The game crashes regardless of what resolution windows is running at. It runs in Fullcreen so it changes the resolution on launch anyway and stops rendering the Windows desktop. I dont believe it was wrong for me to insinuate that this had or could be user error. This is the internet and we are not dealing with millions of desktop support specialists here. Just read most of the reddit threads, or FB group posts or even forum threads like this. There are idiots all over the planet with these and similar issues trying to make this model macbook pro a gaming machine. There is misinformation running rampant on youtube about all these snake oil software programs and even people modifying their machines to stop issues like this. Its everywhere. There are pages and pages of morons on apple support asking the same questions and getting like 098 computer class answers, where most are incorrect. There is nodoubt that most and Im being generous here, are caused by user error plain and simple. Work a day in any level of IT support and you will see it first hand. All walks of life are buying these and trying to make this crap work. And its a big enough learning curve that just about every social media site, and hundreds of pages of forums from all over the internet are talking about how and where to find these drivers, and how to make them work. Yeah I was careful with my words, it wasn't wrong for you to think user error could be the problem, but it was wrong to assume it had to be the cause. I feel like you're harboring a lot of anger there, and I hope you're able to take a break or get some time to chill sometime soon. I would probably weep for humanity's future after 20 years of corporate IT too lol. |
|
