|
|
Post by mike on Sept 3, 2018 10:25:13 GMT
Hi again, Mat
The GPU core doesn't go higher than 1310mhz in modern dx11 games, while previously it ran at 1350mhz. Playing Crysis 1 the GPU max out at about 1210mhz. Are you still using proper Vega drivers for your Bootcamp drivers?
Don't know how much those 40mhz adds performance-wise. Witcher 3 took a 10-15% performance loss compared to 17.12 (most noticeable in rural areas/forests). However, AMD is less good at keeping older optimisations than Nvidia (also poorer Witcher 3 performance in 18.3.4 vs.17.12). The lower clock speed could be part of the issue....
Is this something you could look into, Mat?
Otherwise, 18.8.2 produce considerably less heat and fan noise...
|
|
|
|
Post by Mat HD on Sept 3, 2018 10:41:38 GMT
Hi again, Mat The GPU core doesn't go higher than 1300mhz in modern dx11 games, while previously it ran at 1350mhz. Playing Crysis 1 the GPU max out at about 1210mhz. Are you still using proper Vega drivers for your Bootcamp drivers? Don't know how much those 50mhz adds performance-wise, but it's not ideal. Probably explains some of the temperature loss. Witcher 3 took a 10-15% performance loss compared to 17.12 (most noticeable in rural areas/forests). AMD is less good at keeping older optimisations than Nvidia, but the lower clock speed could be part of the issue. Is this something you could look into, Mat? Too bad, because 18.8.2 otherwise produce considerably less fan noise... These are based on AMD's PC release yes so I'd have thought that the GPU would always go to it's maximum core speed based on its specifications. The 50 MHZ difference in clock speed COULD account for the 5 FPS loss in Witcher 3. Crysis 1 is less demanding than modern games so perhaps the driver chooses to not fully utilise the maximum clock speed, especially if you have an FPS limiter. Unfortunately I am unable to do anything about this as I am not an engineer. Sounds like it could possibly be a bug though - probably worth reporting it to AMD. |
|
|
|
Post by mike on Sept 3, 2018 11:01:55 GMT
Yes, probably some kind of bug. I sent a report to AMD. (I tested Crysis 1 in areas where the framerate dipped below the fps limiter.) It's crazy how much lower temperature 18.8.2 has compared to 17.12, "almost" makes it worthwhile. Witcher 3 now runs cooler with fans @1900rmp, than before @2500rpm. I guess it was too good to be true...  |
|
|
|
Post by Mat HD on Sept 3, 2018 11:14:58 GMT
Yes, probably some kind of bug. I sent a report to AMD. (I tested Crysis 1 in areas where the framerate dipped below the fps limiter.) It's crazy how much lower temperature 18.8.2 has compared to 17.12, "almost" makes it worthwhile. Witcher 3 now runs cooler with fans @1900rmp, than before @2500rpm. I guess it was too good to be true... I guess it depends on what you want. Quieter running Mac with near-equal performance or louder, hotter running iMac with maximum performance. |
|
|
|
Post by FlyingAdmiral2187 on Sept 4, 2018 7:20:25 GMT
So... after a few tryouts with two different iMac Pro’s with the Vega 56 I can say with 100% certainty that this driver is not working with the Vega 56 GPU. I tried on both machines different installation methods, also with different Windows 10 x64 Versions and I get Code 43.
For every try I made a clean OS install with legit and non-modified Windows isos.
So here’s what I tried.
Driver related I tried the installation method in the ReadMe and the old one, also with the official 18.8.2 driver and choosing Radeon Pro 580 and with this specific iMac Pro one.
All times I used the DDU correctly and made sure the Apple drivers were uninstalled completely.
I tried installing only the driver with settings and the other time I let everything checked.
After that I deleted the AMD folder in the Bootcamp folder so that when making a clean install of the OS the Bootcamp installer couldn’t install nothing from the Apple AMD drivers.
I used following Windows 10 x64 versions and deleted the partition completely before reinstalling:
Windows 10 RS1
Windows 10 RS4 Build 1803
Windows 10 RS5 Insider Build 1807
Non of the above mentioned methods worked. Every time I tried installing the driver I got the Code 43 error. I spent more than 20 hours trying!
So my question for Mat:
Do you think you can fix this or are we going to wait for a new driver version to get the Vega 56 to work?
|
|
|
|
Post by mike on Sept 4, 2018 18:54:39 GMT
FlyingAdmiral, you could use 18.3.4, or Apple's own driver (17.12) for now. They still work just fine... I have some interesting numbers here though. Here are 3DMark Timespy scores for Apple's own 17.12 driver, and Mat's 18.3.4 and 18.8.2: 17.12: 6536 18.3.4: 6628 18.8.2: 6575 It could be that the real performance of 18.8.2 isn't that much lower than previous drivers, as I noticed poorer Witcher 3 performance already in 18.3.4. To find out more, I would have to reinstall older drivers and do more comparative benchmarks. Don't really have any interest for that. Anyways, the decrease in heat is a huge benefit. I hope AMD will continue with this trend, as I actually prefer this trade-off. We'll see...  |
|
|
|
Post by Mat HD on Sept 4, 2018 19:12:29 GMT
So... after a few tryouts with two different iMac Pro’s with the Vega 56 I can say with 100% certainty that this driver is not working with the Vega 56 GPU. I tried on both machines different installation methods, also with different Windows 10 x64 Versions and I get Code 43. For every try I made a clean OS install with legit and non-modified Windows isos. So here’s what I tried. Driver related I tried the installation method in the ReadMe and the old one, also with the official 18.8.2 driver and choosing Radeon Pro 580 and with this specific iMac Pro one. All times I used the DDU correctly and made sure the Apple drivers were uninstalled completely. I tried installing only the driver with settings and the other time I let everything checked. After that I deleted the AMD folder in the Bootcamp folder so that when making a clean install of the OS the Bootcamp installer couldn’t install nothing from the Apple AMD drivers. I used following Windows 10 x64 versions and deleted the partition completely before reinstalling: Windows 10 RS1 Windows 10 RS4 Build 1803 Windows 10 RS5 Insider Build 1807 Non of the above mentioned methods worked. Every time I tried installing the driver I got the Code 43 error. I spent more than 20 hours trying! So my question for Mat: Do you think you can fix this or are we going to wait for a new driver version to get the Vega 56 to work? Was it 18.8.1 that worked ok on Vega 56? I can't remember now but if so that's your best bet for now. |
|
|
|
Post by FlyingAdmiral2187 on Sept 5, 2018 7:21:20 GMT
The only driver that’s working is the 18.3.4.
As I only use Windows for gaming some games do not work at all! For example Monster Hunter World.
With the 18.5.2 everything worked fine, but Microsoft fucked it up and it gives me BSOD.
For now I will stay with MacOS. I will give it a shot on the next drivers that’ll appear.
The funny thing is that on Parallels everything works just fine with the official AMD driver and with the drivers from Mat.
Also the internal speakers and camera work which did not work under Bootcamp.
But Parallels is not meant for gaming and the performance is worse than poor!
|
|
|
|
Post by henni on Sept 5, 2018 9:49:09 GMT
FYI: Monster Hunter World runs perfectly with the latest Official Windows Bootcamp Drivers on my iMac Pro with Vega 56 (as do most of the other games on my machine).
|
|
|
|
Post by bsauvage on Sept 13, 2018 7:15:07 GMT
Installed today on Vega64 and working great as reported by others (less noise/heat even than previous Apple official drivers which is what I was on until now).
However hit a glitch during install: when setup was running, just after the AMD window says driver has been installed (so, before it gives the option to install Relive), some sort of screen corruption appeared (horizontal coloured lines within a part of the screen) then screen went black and unresponsive. I then rebooted and it was fine, with driver having installed properly (confirmed as I'm now playing Shadow of Tomb Raider which didn't work on apple stock drivers). No big deal as it works as intented, but reporting for completeness.
Thank you so much Matt for the awesome work. I don't dare to imagine how long we would have had to wait to play this otherwise!
|
|
