Forbes: 'Gears of War: Ultimate Edition' On PC Is A Disaster For AMD Radeon Gamers

[IllogicalGlory]

Nice title OP. No agenda here right?

To be fair, it's the title of the article.

 

[3DVagabond]

this is litteraly blown way out of proportion...

fact is amds drivers are good. they dont need game ready drivers. not even nvidias so called game ready drivers are ready for the games they release to...

That's right. But they say they are and that's all that matters. Like the 970's VRAM and Async compute, and Fermi DX12. They just have to claim all is ok, win the release benches and nVidia customers are content.

 

[Good_fella]

With AoS AMD created illusion that only they can have best DX12 performance. They knew if something goes wrong people will blame MS and Gameworks.

It's happening.

GoW doesn't use Gameworks but somebody desperately trying to make it prove it wrong.

I think AMD must go bankrupt so ADF could cool off. ()

Infraction issued for inflammatory language.
-- stahlhart

 

[Krteq]

With AoS AMD created illusion that only they can have best DX12 performance. They knew if something goes wrong people will blame MS and Gameworks.

It's happening.

GoW doesn't use Gameworks but somebody desperately trying to make it prove it wrong.

I think AMD must go bankrupt so ADF could cool off. ()

Nah, GoW uses HBAO+, and like I already said...

Something to think about...

We already have few DX12 titles based on UE4 (Caffeine, Descent, Fable etc.) and there are no issues with them.

Only difference in this case is a CrapWorks integration... well, this starts to be gold

 

[airfathaaaaa]

With AoS AMD created illusion that only they can have best DX12 performance. They knew if something goes wrong people will blame MS and Gameworks.

It's happening.

GoW doesn't use Gameworks but somebody desperately trying to make it prove it wrong.

I think AMD must go bankrupt so ADF could cool off. ()

you need to take a good look on this
http://forums.guru3d.com/showthread.php?t=387114

 

[casiofx]

With AoS AMD created illusion that only they can have best DX12 performance. They knew if something goes wrong people will blame MS and Gameworks.

It's happening.

GoW doesn't use Gameworks but somebody desperately trying to make it prove it wrong.

I think AMD must go bankrupt so ADF could cool off. ()

Well they brought it upon themselves, just like when there's over tessellated stuffs going on crysis 2 scandal last time

 

[Dribble]

It starting to look like the Fury/Nano's in particular have stuttering issues and need to be individually fixed by AMD for each game, unlike the 390's which tend to work fine.

This is a pretty strong reason to avoid those cards as you are so reliant on AMD fixing stuff. Sure right now they will probably fix it, but when the devs do further updates that break the fixes will AMD continue to fix it? When the next gen replacement for the fury comes out how much effort are AMD going to continue to put into all these custom fury fixes?

 

[ShintaiDK]

It starting to look like the Fury/Nano's in particular have stuttering issues and need to be individually fixed by AMD for each game, unlike the 390's which tend to work fine.

This is a pretty strong reason to avoid those cards as you are so reliant on AMD fixing stuff. Sure right now they will probably fix it, but when the devs do further updates that break the fixes will AMD continue to fix it? When the next gen replacement for the fury comes out how much effort are AMD going to continue to put into all these custom fury fixes?

The 2 engineers dedicated for the job seems to have plenty of work. But as you say, what happens when these 2 gets reallocated one way or the other. When the next gen is out, I am sure these fixes will be a thing of the past.

 

[caswow]

seems like you should avoid the 980ti since its stutters tooD:

 

[casiofx]

The 2 engineers dedicated for the job seems to have plenty of work. But as you say, what happens when these 2 gets reallocated one way or the other. When the next gen is out, I am sure these fixes will be a thing of the past.

I guess it'll be treated as 4GB card just like 290/290X?

It doesn't have the 3.5+0.5GB as 970 that really needs the optimization or it'll badly stutter if future game squeezes all the 4GB.

 

[ShintaiDK]

I guess it'll be treated as 4GB card just like 290/290X?

Yes. It will be a regular very expensive 4GB without. The 390/390X didn't get 8GB for the sake of it. And 14/16nm will bring an inflation in VRAM usage. With 4GB being low end.

 

[monstercameron]

It starting to look like the Fury/Nano's in particular have stuttering issues and need to be individually fixed by AMD for each game, unlike the 390's which tend to work fine.

This is a pretty strong reason to avoid those cards as you are so reliant on AMD fixing stuff. Sure right now they will probably fix it, but when the devs do further updates that break the fixes will AMD continue to fix it? When the next gen replacement for the fury comes out how much effort are AMD going to continue to put into all these custom fury fixes?

Not sure how you came to that conclusion. Why would amd have to "fix" memory management for this specific title?

 

[Qwertilot]

Well, there's definitely something very messed with it on the fiji stuff right now!

Surely most likely to be memory related somehow? It isn't like they changed the core architecture much from the 390 to Fiji.

 

[ShintaiDK]

Well, there's definitely something very messed with it on the fiji stuff right now!

Surely most likely to be memory related somehow? It isn't like they changed the core architecture much from the 390 to Fiji.

Tonga is the same one. Besides for the memory.

But 390 does share the same GCN as the Xbox One.

 

[littleg]

So why are the Nvidia cards having problems too?

 

[railven]

So why are the Nvidia cards having problems too?

If I had to guess, if it is DX12, might be a AS compute issue. For both sides.

I was really looking forward to this game (and a bunch of other XBone PC releases), but frankly their recently Windows 10 limitations have soured me.

Speak with your wallets. MSFT has basically ruined Games for Windows 2.0 (or is it 3.0 now?) before it even had a chance.

 

[littleg]

If I had to guess, if it is DX12, might be a AS compute issue. For both sides.

I was really looking forward to this game (and a bunch of other XBone PC releases), but frankly their recently Windows 10 limitations have soured me.

Speak with your wallets. MSFT has basically ruined Games for Windows 2.0 (or is it 3.0 now?) before it even had a chance.

Yeah, could be it. If it's an issue for both Maxwell and Fiji cards then it certainly points to something in software imo.

 

[railven]

Yeah, could be it. If it's an issue for both Maxwell and Fiji cards then it certainly points to something in software imo.

Will be real interesting to see if Quantum Break has similar issues. Could be some where along the way the "DX12 on console to PC port be so easy" meme broke.

 

[Stuka87]

Will be real interesting to see if Quantum Break has similar issues. Could be some where along the way the "DX12 on console to PC port be so easy" meme broke.

Its sure to break when nVidia convinces the developer to not just do a straight port, but cobble nVidia's proprietary code into the game, which then undoes any optimizations the game may have had.

We can just expect any gameworks game to be broken to some extent. Not a single one has been trouble free. In the case of this game, it stutters on AMD and nVidia cards. So nobody is a winner here.

 

[AtenRa]

If I had to guess, if it is DX12, might be a AS compute issue. For both sides.

Turning off Ambient Occlusion fixes some problems (not the stuttering). So I dont believe it has to do with AS and DX-12.

 

[Qwertilot]

So why are the Nvidia cards having problems too?

It seems to have issues everywhere, which is no huge surprise
(Not least with the windows store.).

Still, worth bearing in mind how 'impressive' the reported issue is - Fiji getting half the frame rate of a 290/X. That's just daft. Suppose we'll find out

I seriously hope that isn't caused by some sort of 'minor' software issue in DX12. If it is, between two such similar architectures, we're going to have a horrible time with anything using the API.

A memory bottleneck due to something or other would be much more palatable.

 

[Azix]

This is unreal engine 3 ported to dx12. Taking the ancient games there might not be working out so well. It's not representative of more modern engines being used on consoles and being ported over to PC imo. Its completely outside of this generation.

Turning off Ambient Occlusion fixes some problems (not the stuttering). So I dont believe it has to do with AS and DX-12.

ambient occlusion was supposed to be one of the things they did with async, so thought it was their async implementation that was messed up.

 

[Krteq]

ambient occlusion was supposed to be one of the things they did with async,

Yes, but not with HBAO+.

 

[Game_dev]

I am so glad I went NVIDIA this round. The Crimson driver release has been a disaster. Between damaging cards and horrible release support, this has been a nightmare for AMD users.

 

[Paul98]

I am so glad I went NVIDIA this round. The Crimson driver release has been a disaster. Between damaging cards and horrible release support, this has been a nightmare for AMD users.

Seriously this is going to be your first post? I have been having a seeing FAR more driver problems with NVidia than AMD recently. Especially since it's broken on many cards both NV and AMD.