New AMD 16.1 Hotfix drivers - Include fix for Win10 and Supercruise FPS issues

Seems it was an issue on AMD's side, I wonder if any of those that raged against FDev and blamed them will apologize, guessing not but I wish people would at least accept that they were wrong in blaming FDev.
 
Hip hip 'expletive' hooray. I can finally return to elite after some 4-5 mnths. No sooner had I paid for all the expansions, I bought an R9 390X to upgrade my pc and then found I could not go anywhere due to 1fps in SC. I was forced to abandon the game as it was unplayable. I can return to my T9, Viper and 120M Cr and restart my career.

On the plus side all my forum infringements have been spent too in the meantime. Happy days all round.

This was always an AMD issue and never an FD issue. That much was always obvious to me so I do not hold any grudges against FD but AMD's rep has taken a beating as far as I am concerned. But as long as it performs then all will be forgiven as I am a forgiving type.

I cant wait to install tonight and finally play horizons. My weekend is now laid in front of me.

I'm so happy now I could squeak.
 
And unless you know what AMD and FD were collaborating on with this new update and drivers you cannot know who or what was at fault. I'm far more inclined to assume both parties had issues they need to work on.

Well, perhaps you are more willing/eager to assign any spare blame to FDEV because "broken promises".
 
Well done AMD for catching up .

News: For 'My' Asus R9 290 DCII OC 4Gb ,this fixes the supercruise FPS slowdown bug.
 
You can't. As of Crimson release your card has moved to legacy status and no further releases are planned.

:( Shouldn't have gone for AMD. It's an old card (bought it 4 years ago), but am bummed they ditched support for my card this soon. Would it be possible to hack this update in?
 
Really good news. Nvidia user myself, but I think this gives Frontier developers credit when it's confirmed like this, that the problem was in the drivers. Off topic but: next, we will see if code in the Oculus drivers are the problem for Elite not being able to support later SDK's.
 
anyone with a triple mon setup can confirm the eyefinity taskbar prob is adressed, too? taskbar on middle mon was resetting to stretched over all 3 after every reboot.

I'm going home and testing it, I hope they fixed it because it's annoying. You can have a workaround by creating a link to ccc.exe on your desktop and launching it after the pc startup, no need to change the setting again, just start ccc.
Reported the bug a few minutes ago on the amd bugtracker.
 
Great news, will download and try it later, been waiting for this such a long time, i could not join in any community events because of the lag when playing with other players in my instance in SC. And even though 14.4 driver worked ok for me, my other games (eg: Fallout 4) would not run with older drivers.
 
Well, perhaps you are more willing/eager to assign any spare blame to FDEV because "broken promises".

As opposed to defending FD in the usual Fanboi fashion despite not having anything constructive to say in a thread created to provide information only?

There as absolutely no need for you (or others) to come on this thread trolling people to say they should apologise to FD "because it was AMD's fault all along". None of us have a real clue what broke the SC FPS on AMD cards, especially considering Nvidia GPUs have hardly been trouble free. How about just leaving the thread be for people to provide constructive feedback rather than trolling.
 
Really good news. Nvidia user myself, but I think this gives Frontier developers credit when it's confirmed like this, that the problem was in the drivers. Off topic but: next, we will see if code in the Oculus drivers are the problem for Elite not being able to support later SDK's.
I'm going home and testing it, I hope they fixed it because it's annoying. You can have a workaround by creating a link to ccc.exe on your desktop and launching it after the pc startup, no need to change the setting again, just start ccc.
Reported the bug a few minutes ago on the amd bugtracker.

Tested it right now aaaaaaaaaaaaaaaaaaaaaand ... NOPE! It's not fixed 8_{
 
They did, and offered refunds. It is, by the way, a terrible excuse for what people screamed at FD during the SC AMD issue.

Thank you for your constructive feedback and valuable testing of the AMD SC fix drivers.
 
Last edited:
:( Shouldn't have gone for AMD. It's an old card (bought it 4 years ago), but am bummed they ditched support for my card this soon. Would it be possible to hack this update in?

The 5000 series cards came out in mid-end of 2009. They're old cards now so they're hardly ditching support 'soon'. As for your question, not a clue but I'd doubt it.
 
Armour, this hotfix doesn't mean it's AMD's fault

It is very unlikely not a generic freak driver bug. To be frank. ED is not important enough to fix incompetence on behalf of the developers in your driver. If it would have been FDev's fault I don't think AMD would have fixed it. ED isn't a bad seller. I think it's #15 for 2015 on Steam. But it's certainly not THE GAME that's going to give you problems. If this would be GTA then that's a different story. If that game doesn't work you will have problems and it doesn't matter if those idiots can't code. It has to work. But ED is certainly not GTA.

Chances are it had something to do with shaders. If it would have been FDev's fault AMD would have told them what they are doing wrong and FDev would have fixed it in the last update. But the last update still didn't work before the drivers update. So it clearly is an issue that could not be solved outside the driver. And that strongly suggests FDev wasn't doing something wrong. It just wasn't working as it should have.

Drivers are getting more and more complex and so are shaders. And shaders are hand crafted. So there's a good chance for bugs. Much more than using generic APIs that are well tested with little chances for freak bugs that didn't pop up before.
 
Last edited:
Back
Top Bottom