16.4.1

Radeon Software Crimson Edition 16.4.1 Highlights
Support for:
    • Quantum Break™
      • Upto 35% faster performance using Quantum Break™ on Radeon™ R9 Fury X than with Radeon™ Software Crimson Edition 16.3.2(1).
    • Oculus Rift™
    • HTC Vive™
Resolved Issues
    • Frame rate capping issues experienced in some DirectX®12 applications is resolved.
    • Hitman™ may experience flickering when played in DirectX® 11 mode using high game shadow settings.
Known Issues
    • A few game titles may fail to launch or crash if the AMD Gaming Evolved overlay is enabled. A temporary workaround is to disable the AMD Gaming Evolved "In Game Overlay"
    • Need For Speed™ may experience poor scaling or flickering in AMD Crossfire™ mode. As a work around users can disable the profile through the Radeon™ Settings game manager.
    • The Division™ may experience flickering in AMD Crossfire™ mode.
    • Power efficiency toggle in Radeon™ Settings is showing up for some unsupported products.
    • XCOM2™ users may experience an application crash when using AMD Crossfire™ mode. As a work around please disable AMD Crossfire™ for the games profile in the Radeon™ Settings Gaming tab.
    • Some DX9 applications cannot disable AMD Crossfire™ mode through Radeon™ Settings.
    • A small subset of AMD Radeon™ R9 380 users may be experiencing slower than expected fan speeds. A work around is to raise your fan speeds through AMD Overdrive in Radeon™ Settings manually to a desired amount.
    • HDMI Scaling options may not be available in Radeon™ Settings on some system configurations.


:hmm:
 
I feel really sorry for people that still use Crossfire. It's become a joke, only that it's not funny anymore.
 
Hmm...they didn't even mention something else that they fixed in the change log. I'll update 16.3.2 to 16.4.1 anyway.
 
I feel really sorry for people that still use Crossfire. It's become a joke, only that it's not funny anymore.

Triple Crossfire works fine here under Windows 7. The thing is that Windows 10 is terrible for gaming. Also I do not buy any game which is crappy coded, unless they fix it.
 
Last edited:
I feel really sorry for people that still use Crossfire. It's become a joke, only that it's not funny anymore.
it's not a big deal The Division looks about the same as Dying Light did when new and it took them about 4 to 5 months to fix Dying Light and get cfx balanced but is great at 4k with cfx now
The Division will work in time with sli/cfx

FO4 works fine in cfx and is still crap with sli, it is the main reason I run both sli anf cfx for 4k


.......

just wish they would stop putting all my desktop icons to the left side of the screen, I have to rearrange all my icons with every new driver :(
 
Last edited:
does it scale well at all times tho bill? Gamebryo based titles for me usually have toilet seat style scaling depending on what part of the game your at lol.
 
Thanks for the heads up. :up:
Nice driver so far with FAH. TPF is within 2 seconds of the 16.3 driver with the power efficiency of the 16.3.2.

Just have to do a bit of gaming now.
 
it's not a big deal The Division looks about the same as Dying Light did when new and it took them about 4 to 5 months to fix Dying Light and get cfx balanced but is great at 4k with cfx now
The Division will work in time with sli/cfx

FO4 works fine in cfx and is still crap with sli, it is the main reason I run both sli anf cfx for 4k


.......

just wish they would stop putting all my desktop icons to the left side of the screen, I have to rearrange all my icons with every new driver :(

Dying light would be perfect if it wasnt for the insane flicker when your covered in blood. With the difficulty of the new expansion, covering yourself in blood is pretty essential too. My only issue with it.
 
Dying light would be perfect if it wasnt for the insane flicker when your covered in blood. With the difficulty of the new expansion, covering yourself in blood is pretty essential too. My only issue with it.
not played in a while is the flicker part of being covered in blood or cfx ?
 
I found a bug in this driver release. On my Kaveri A10-7400p laptop, the frame rate limit feature no longer works. I rolled back to 16.3.2 and it works okay again. I hope this is fixed in the next driver release.

I have not tested any other system config, has anyone else seen this issue?
 
Back
Top