Created attachment 140628 [details] A screenshot of in-game menu With recent Mesa versions some parts of the game Deus Ex: Mankind Divided are rendered not the way they are supposed to. To reproduce the bug, max out all graphics settings (didn't test with other settings) and while in-game, go to "database" menu. It will show bizarre artifacts instead of readable text. The game used to work correctly with older Mesa/LLVM. Tested on: RX570 + Mesa-git cb65246ed2 + LLVM 7.0 r336061 + linux 4.17.6
Di(In reply to network723 from comment #0) > Created attachment 140628 [details] > A screenshot of in-game menu > > With recent Mesa versions some parts of the game Deus Ex: Mankind Divided > are rendered not the way they are supposed to. > To reproduce the bug, max out all graphics settings (didn't test with other > settings) and while in-game, go to "database" menu. It will show bizarre > artifacts instead of readable text. The game used to work correctly with > older Mesa/LLVM. Are you sure it used to work. I've tested all the way back to Mesa 17.0-branchpoint (d1efa09d342bff) on Intels i965 driver and I still see the issue. For now moving this to Mesa core as it seems to be a general Mesa issue (or game bug ?) rather than a radeonsi problem.
(In reply to Timothy Arceri from comment #1) > Are you sure it used to work. I've tested all the way back to Mesa > 17.0-branchpoint (d1efa09d342bff) on Intels i965 driver and I still see the > issue. > > For now moving this to Mesa core as it seems to be a general Mesa issue (or > game bug ?) rather than a radeonsi problem. I'm sure I played the game with no issues before. It was in March 2017, I think. Maybe the game was updated since then. I have no capable hardware from other vendors to test with.
I also gave the Mesa 13.0-branchpoint with ca76e6b5213c92432b applied a try and still see the issue there.
If so, I wonder if it works ok with proprietary nvidia driver, and maybe some people from Feral could comment on this.
Could you go into "~/.local/share/feral-interactive/Deus Ex Mankind Divided/preferences", find this line: <value name="NoOverwriteBOUploadStrategy" type="integer">6</value> change 6 to 1, and see if that fixes the problem?
(In reply to Alex Smith from comment #5) > Could you go into "~/.local/share/feral-interactive/Deus Ex Mankind > Divided/preferences", find this line: > > <value name="NoOverwriteBOUploadStrategy" type="integer">6</value> > > change 6 to 1, and see if that fixes the problem? That definitely makes glitches go away for me.
Thanks for confirming. It looks like we have a bug where we fail to identify Mesa properly as a result of compatibility profile support being added, which causes us to go down a path for a different driver that incorrectly adds that configuration option. That then persists even after switching back to an older Mesa version. We're looking into what we can do here, but I can confirm it is not a Mesa bug.
(In reply to Alex Smith from comment #7) > Thanks for confirming. > > It looks like we have a bug where we fail to identify Mesa properly as a > result of compatibility profile support being added, which causes us to go > down a path for a different driver that incorrectly adds that configuration > option. That then persists even after switching back to an older Mesa > version. > > We're looking into what we can do here, but I can confirm it is not a Mesa > bug. Hmm ... I'm seeing the same issue on a i965 skylake machine that should never have exposed compatibility profile support.
(In reply to Timothy Arceri from comment #8) > Hmm ... I'm seeing the same issue on a i965 skylake machine that should > never have exposed compatibility profile support. Unfortunately the bug there is that that option has always been incorrectly set on Intel (though the game does not support Intel). FWIW, the rendering issues when it is set also occur on the NVIDIA proprietary driver, so definitely not Mesa-specific.
We've just released a game data update that should fix this issue for both AMD and Intel, as well as a shader compilation failure on 18.2. It should be applied next time you launch the game (it's handled outside of Steam, will be automatically downloaded at startup).
(In reply to Alex Smith from comment #10) > We've just released a game data update that should fix this issue for both > AMD and Intel, as well as a shader compilation failure on 18.2. It should be > applied next time you launch the game (it's handled outside of Steam, will > be automatically downloaded at startup). Thanks! I can confirm all issues are gone on both AMD and Intel.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.