The AMD Driver Thread

[Emlyn_Dewar]

"We're sorry we got caught. Next time we'll try to be more discrete."

 

[Glanza]

 

[tamzzy]

Disagree with that take.

Here’s What this Means for You:

This is not the end of support for RDNA 1 and RDNA 2. Your Radeon RX 5000 and RX 6000 series GPUs will continue to receive:

Game support for new releases
Stability and game optimizations
Security and bug fixes
The difference is that these products now benefit from a dedicated, stable driver branch, one built on years of tuning and optimization. This approach helps deliver a smoother, more consistent experience for your games while insulating previous generation GPUs from rapid changes designed for newer architectures.

This is just another way of phrasing what has already been said.

Maintenance mode = "Stable drivers"
Game support for new releases = you won't get optimised support from day 1, but as and when "the market dictates"

 

[uscool]

Good job AMD for doing Nvidia's marketing

 

[sunn]

Kinda impressive

Creates own problem, makes it worst with vague/spun follow ups, and leaves the door fully open for more criticism when they inevitable fail to deliver.

Side note, RDNA1 could prob be sun-setted, although they should have given some notice, but when you can still buy new RDNA2 products, there's no excuse, only obv course is to overcompensate, add Vega and Polaris to the main branch.

 

[Cob]

It’s just stinks of them not wanting to enable FSR4 on RDNA2, despite the evidence that a cut down version of it works fine. They can now remove any FSR4 gubbins from the RDNA1 & 2 drivers to ensure that there’s no possibility of a workaround.

 

[stuartharrison]

Do you have a link for the IC report please?

@AMD_Vik Star Citizen 25.10.2 report threads
There are multiple report threads, here are some of them, there are more if you look - the workaround is to go back to 25.9.1 as you know;

Issue Council - Sign in

Create an account or sign in to Issue Council. Track bugs on and vote on the issues to help the development team identify what to work on next.

issue-council.robertsspaceindustries.com

Issue Council - Sign in

Create an account or sign in to Issue Council. Track bugs on and vote on the issues to help the development team identify what to work on next.

issue-council.robertsspaceindustries.com

Issue Council - Sign in

Create an account or sign in to Issue Council. Track bugs on and vote on the issues to help the development team identify what to work on next.

issue-council.robertsspaceindustries.com

Issue Council - Sign in

Create an account or sign in to Issue Council. Track bugs on and vote on the issues to help the development team identify what to work on next.

issue-council.robertsspaceindustries.com

Issue Council - Sign in

Create an account or sign in to Issue Council. Track bugs on and vote on the issues to help the development team identify what to work on next.

issue-council.robertsspaceindustries.com

 

[G J]

It’s just stinks of them not wanting to enable FSR4 on RDNA2, despite the evidence that a cut down version of it works fine. They can now remove any FSR4 gubbins from the RDNA1 & 2 drivers to ensure that there’s no possibility of a workaround.

I'm surprised that people have not kicked off more about this that RDNA 1/2/3 have been abandoned without FSR4 support for months and may not get official support from AMD.

Changing driver support and potentially dropping FSR4 support is going to look bad at the same time, maybe this is the first step.

 

[Hotwired]

Bet no one posturing over the drivers has any solid understanding how, if at all, anything has changed for the experience of owning a listed card in "maintenance mode".

They're on the back burner, but they already were on the back burner so...

 

[uscool]

Bet no one posturing over the drivers has any solid understanding how, if at all, anything has changed for the experience of owning a listed card in "maintenance mode".

They're on the back burner, but they already were on the back burner so...

Same could be said for Nvidia 20/30 series but you don't get them going saying maintenance etc and be open for criticism, AMD dug a hole

 

[humbug]

I agree with some of this, but then he goes on to suggest people shouldn't buy AMD GPU's and then promotes Nvidia..... They just can't help themselves.

@AMD_Vik Star Citizen 25.10.2 report threads
There are multiple report threads, here are some of them, there are more if you look - the workaround is to go back to 25.9.1 as you know;

Issue Council - Sign in

Create an account or sign in to Issue Council. Track bugs on and vote on the issues to help the development team identify what to work on next.

issue-council.robertsspaceindustries.com

Issue Council - Sign in

Create an account or sign in to Issue Council. Track bugs on and vote on the issues to help the development team identify what to work on next.

issue-council.robertsspaceindustries.com

Issue Council - Sign in

Create an account or sign in to Issue Council. Track bugs on and vote on the issues to help the development team identify what to work on next.

issue-council.robertsspaceindustries.com

Issue Council - Sign in

Create an account or sign in to Issue Council. Track bugs on and vote on the issues to help the development team identify what to work on next.

issue-council.robertsspaceindustries.com

Issue Council - Sign in

Create an account or sign in to Issue Council. Track bugs on and vote on the issues to help the development team identify what to work on next.

issue-council.robertsspaceindustries.com

Thanks

 

[GoogalyMoogaly]

I see AMD have announced that new drivers will continue to support Windows 10.

Well I imagine for RDNA3 and RDNA 4 cards at least

 

[humbug]

@stuartharrison

AMD GPU Error code 3221225477 work around. - Star Citizen Spectrum

If you have an AMD GPU and you're experiencing the crash on game startup with Error code 3221225477 this fix may work for you. Download and run the AMD Clean-up Utility, find it here. AMD Cleanup...

robertsspaceindustries.com

 

[stuartharrison]

@stuartharrison

AMD GPU Error code 3221225477 work around. - Star Citizen Spectrum

If you have an AMD GPU and you're experiencing the crash on game startup with Error code 3221225477 this fix may work for you. Download and run the AMD Clean-up Utility, find it here. AMD Cleanup...

robertsspaceindustries.com

Basically, what the community has already figured out.
I'm Firfely50 in SC. I've just started playing it.

 

[Grim5]

I see AMD have announced that new drivers will continue to support Windows 10.

Well I imagine for RDNA3 and RDNA 4 cards at least

Kinda pointless, W10 is now rapidly going away - steam hardware survey shows mass switching to W11 and several game developers have stated their new games will no longer support W10.
Linux marketshare is also increasing quite a bit

 

[jimhaumman]

What's the reasoning behind this decesion on AMD part? (how much money could they save? )

 

[humbug]

Basically, what the community has already figured out.
I'm Firfely50 in SC. I've just started playing it.

You're welcome to join our org.

Join the LOGI-SEC INC Discord Server!

LOGI-SEC INC is a Star Citizen organization focused on exploration, industry, and security. Join us for live leaks, patch news, and coordinated fleet operations. | 39 members

discord.gg

 

[Blackjack Davy]

I see AMD have announced that new drivers will continue to support Windows 10.

Well I imagine for RDNA3 and RDNA 4 cards at least

Well thats more than Nvidia is doing. Win 10 user? Get lost.

 

[Mercurial]

What's the reasoning behind this decesion on AMD part? (how much money could they save? )

I typed out a long response but it's basically: Buy our new stuff.

No idea on the savings but I daresay it'll be substantial over the whole platform. What they lose in goodwill and brand image is unknown though.

 

[heatonpkmassive]

What they lose in goodwill and brand image is unknown though.

Probably already lost a ton due to this and past pricing for inferior products.