Quantum Break

Quantum Break

View Stats:
Szaby59 Oct 5, 2016 @ 1:37pm
[BUG?] Different graphics on AMD cards in DX11 compared to DX12
Looking at the videos I noticed something.
The starting area looks slightly different on an AMD card in DX11 than it should on DX12 (looks the same on nVidia):

RX 480 (DX11 - left | DX12 - right): https://s10.postimg.org/e10q95vt5/rx480a.png

RX 480 , GTX 970, GTX 1060: https://s10.postimg.org/wo0lw3jxl/4802.png

Looks like some effects are not rendered on AMD cards in DX11.

My R9 Fury produces the same "anomaly" in DX11 the gate looks brighter and sharper.
Last edited by Szaby59; Oct 5, 2016 @ 2:00pm
< >
Showing 1-3 of 3 comments
Necrosis1203 Oct 5, 2016 @ 5:56pm 
Its the game artifacting this is on both vendors. Shadows: Shadow quality is clearly one of the areas where sacrifices had to be made. Jumps between shadow cascades are often harsh with visible artefacts becoming obvious just a couple of metres from the player character. Even at close proximity, the shadow resolution is never particularly sharp. We also observed a number of instances where transitions between shadow maps highlighted a difference in positioning. The filtering used on shadows is excellent, though, and bokeh shapes appear to be used to create the effect of light flittering through trees, but shadows on the whole are still much too resolution for our tastes. http://www.eurogamer.net/articles/digitalfoundry-2016-quantum-break-tech-analysis
Last edited by Necrosis1203; Oct 5, 2016 @ 5:59pm
Szaby59 Oct 6, 2016 @ 12:28am 
It's not on both vendors, this bug is only on AMD cards+dx11
Last edited by Szaby59; Oct 6, 2016 @ 12:32am
Voodooman Oct 6, 2016 @ 7:39am 
This happens because ♥♥♥♥♥♥ D3D12 returned games to a state of mid 90th in terms of making non unified code, which means AMD and NVidia and other vendors and each video card should have different low level code for each, and since it different, when you backport to more unified api you can loose something in transition, which seems to happen with AMD.

Also the irony is - Xbox runs on AMD HW, so console version is better optimized for AMD and this should sustain in pc version since xbox and pc games nowadays share a lot of common x64 code, but thanks to half baked state and shortsighted coding of Win 10 and Win 12, this is not the case.

Anyway - AMD was always problematic because their driver coding division is bunch of ♥♥♥♥♥♥♥♥ monkeys who code for bananas, AMD has good software but drivers always had compatiblity and performance issues, which is why amd should be avoided on PC forever if you want less problematic and more feature-rich expirience.
< >
Showing 1-3 of 3 comments
Per page: 15 30 50

Date Posted: Oct 5, 2016 @ 1:37pm
Posts: 3