|
Post by Mat HD on Oct 27, 2018 21:48:46 GMT
Not many changes on this side of things, though the AMD installer seems to be working properly again, which is great! Means we can go back to the normal way of installing the driver again.
There's a fix to Vulcan crashing in this release which is probably the biggest reason to update over 18.10.1.
Also available for iMac Pro on the main page.
Enjoy!
Please note: The issues continue with iMac 5k with the Radeon Pro 500 series where the 5k resolution is split into two separate resolutions and not displayed correctly. Please send bug reports to AMD otherwise they won't fix this. Continue to use 18.8.2 for now. Thanks!
|
|
arjan
Newbie Boot Camper
Posts: 1
|
Post by arjan on Oct 28, 2018 11:42:49 GMT
Just tested on my iMac 5k and sorry to report the display is still split into two separate displays
|
|
ifrosty
Junior Boot Camper
Posts: 11
|
Post by ifrosty on Oct 30, 2018 0:15:55 GMT
Not many changes on this side of things, though the AMD installer seems to be working properly again, which is great! Means we can go back to the normal way of installing the driver again. There's a fix to Vulcan crashing in this release which is probably the biggest reason to update over 18.10.1. Also available for iMac Pro on the main page. Enjoy! Please note: The issues continue with iMac 5k with the Radeon Pro 500 series where the 5k resolution is split into two separate resolutions and not displayed correctly. Please send bug reports to AMD otherwise they won't fix this. Continue to use 18.8.2 for now. Thanks! Everything is working fine. Back to one click install! Thank you! Yeah. I saw that in the release notes that Mat put out with the install.
Just stick to use 18.8.2 like he said
|
|
|
Post by andymazur on Oct 31, 2018 21:15:39 GMT
Guys, I still get error 173 on MacBook PRO 15 Inch with 560
|
|
|
Post by penguin on Nov 8, 2018 7:34:42 GMT
Software and driver working well so far with iMac Pro (Radeon Pro Vega 56). Thanks again Mat!
PS if anyone knows how to obtain good and consistent FPS for 'Wolfenstein: The New Order' with the Pro Vega 56 let me know as it seems poorly optimised for AMD cards.
|
|
|
Post by mike on Nov 8, 2018 9:27:58 GMT
Software and driver working well so far with iMac Pro (Radeon Pro Vega 56). Thanks again Mat! PS if anyone knows how to obtain good and consistent FPS for 'Wolfenstein: The New Order' with the Pro Vega 56 let me know as it seems poorly optimised for AMD cards. Strange, it ran very well on my iMac Pro /Vega 64 Pro a few months ago, when I tried it. Probably it's the newer driver version. AMD sometimes drop the optimisations for games after a while, I saw the same thing with Witcher 3 (which lost some performance after 18.3.4). I also noticed lighting glitches on objects in STALKER Lost Alpha with 18.10.2, so only recommendation afaik is to simply wait for the next driver version - and see if it improves.
|
|
|
Post by penguin on Nov 8, 2018 10:37:04 GMT
Software and driver working well so far with iMac Pro (Radeon Pro Vega 56). Thanks again Mat! PS if anyone knows how to obtain good and consistent FPS for 'Wolfenstein: The New Order' with the Pro Vega 56 let me know as it seems poorly optimised for AMD cards. Strange, it ran very well on my iMac Pro /Vega 64 Pro a few months ago, when I tried it. Probably it's the newer driver version. AMD sometimes drop the optimisations for games after a while, I saw the same thing with Witcher 3 (which lost some performance after 18.3.4). I also noticed lighting glitches on objects in STALKER Lost Alpha with 18.10.2, so only recommendation afaik is to simply wait for the next driver version - and see if it improves. Thanks for your help Mike. Hopefully it improves with newer driver versions. I can rarely achieve 60fps with constant drops to 45/50 fps @1080p on the lowest graphics settings. I had the same issue with the Apple bootcamp driver. I know Apple underclocks the GPU but I don't have performance issues with other games.
|
|
|
Post by mike on Nov 9, 2018 18:30:02 GMT
That's not right at all. I ran the game in 1440p with most settings at max (except for antialiasing), and it was steady 60fps afaik. Something is really off here.
|
|