Bug 110459 - Escape from Tarkov on DXVK renders wrong windows reflection unless RADV_DEBUG=nohiz is passed
Summary: Escape from Tarkov on DXVK renders wrong windows reflection unless RADV_DEBUG...
Status: RESOLVED NOTOURBUG
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Vulkan/radeon (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact: mesa-dev
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-04-17 08:32 UTC by faalagorn
Modified: 2019-05-03 21:57 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
With RADV_DEBUG=nohiz (2.46 MB, image/png)
2019-04-17 08:32 UTC, faalagorn
Details
Without RADV_DEBUG=nohiz (2.52 MB, image/png)
2019-04-17 08:33 UTC, faalagorn
Details

Description faalagorn 2019-04-17 08:32:52 UTC
Created attachment 144010 [details]
With RADV_DEBUG=nohiz

Since I didn't had that problem before, I originally hoped it was the same regression as the one affecting Lords of the Fallen, Bug 110259: originally found about it in DXVK issue here: https://github.com/doitsujin/dxvk/issues/985 but unfortunately commit 62a9d757e6074215c145c9637014d9acb16d865d did not fix it, but running with RADV_DEBUG=nohiz fixes it.

I tested it on several latest mesa and DXVK git versions now, last one was 4c3c417b00fd2594d8fa5ab86479fb7c448d1f09 for mesa, hard to tell when exactly the bug started appearing, but I may do some testing, especially if it happens with the stable one too. Fresh reinstall of the game, DXVK and even using a different Linux install did not help. My card is AMD Radeon RX 580.

Basically, it's the squares that appears on the place where windows are that are moving with my character view, in at least one map (Factory). I didn't test the game extensively without RADV_DEBUG=nohiz whether the bug happens elsewhere, but I may now for debugging, but the game runs fine otherwise on RADV with RADV_DEBUG=nohiz. I didn't test how it runs with AMDVLK either.

I'm attaching the screen how it looks like with RADV_DEBUG=nohiz and how it looks like without it.

The game is basically a Unity 5.6.6f2 online game with custom anticheat, so I normally don't want to mess too much with it, but it does have an offline mode (sadly you need to have an account to play though). If there's anything I can help with it further, let me know!
Comment 1 faalagorn 2019-04-17 08:33:47 UTC
Created attachment 144011 [details]
Without RADV_DEBUG=nohiz
Comment 2 Samuel Pitoiset 2019-04-17 09:02:32 UTC
Can you record a renderdoc capture ?
Comment 3 faalagorn 2019-04-17 09:04:13 UTC
Thanks for the reply! I will take a look later today or tomorrow hopefully; guess I should not be overly worried about it triggering some anticheat protection? The launcher needs online connection to run, but I can disconnect and play offline later :)
Comment 4 faalagorn 2019-04-19 20:22:12 UTC
I had some problems with the PC so couldn't post before. I'm no expert in Renderdoc, but it seems the game is failing to launch for me – I've been trying to run the launcher, as the game won't allow to log in otherwise. That's the result I got so far:

[faalagorn@faalagorn-desktop ~]$ renderdoccmd capture WINEPREFIX=/home/faalagorn/Games/escape-from-tarkov /home/faalagorn/.local/share/lutris/runners/wine/wine-tkg-git-escapefromtarkov/bin/wine64 /home/faalagorn/Games/escape-from-tarkov/drive_c/Battlestate Games/BsgLauncher/BsgLauncher.exe
Launching 'WINEPREFIX=/home/faalagorn/Games/escape-from-tarkov' with params: /home/faalagorn/.local/share/lutris/runners/wine/wine-tkg-git-escapefromtarkov/bin/wine64 /home/faalagorn/Games/escape-from-tarkov/drive_c/Battlestate Games/BsgLauncher/BsgLauncher.exe
exec failed
Warning - Couldn't locate renderdoc target control listening port between 38920 and 38927 in /proc/3724/net/tcp

Quick search for the error found some info about 32-bit versions not working, but both the game and launcher are 64-bit, so it may be something wrong on my side, as I never used renderdoc before. Is it possible to hook renderdoc itto a running process, or maybe there's some guides around? Anyway, I'll be on the lookout and post if I find anything more :)
Comment 5 Rhys Perry 2019-04-26 17:15:06 UTC
Try running

WINEPREFIX=/home/faalagorn/Games/escape-from-tarkov renderdoccmd capture /home/faalagorn/.local/share/lutris/runners/wine/wine-tkg-git-escapefromtarkov/bin/wine64 /home/faalagorn/Games/escape-from-tarkov/drive_c/Battlestate Games/BsgLauncher/BsgLauncher.exe

instead (environment variables should go before the "renderdoccmd", not the program you're capturing).
Comment 6 faalagorn 2019-05-03 21:57:25 UTC
Thank you! I was actually about to test it, but since I was messing with other stuff I didn't do that earlier, I only got to it today. Updating mesa didn't help, but it turned out that some DXVK update must have, so I misjudged the culprit here, and it seemed to be a DXVK bug, so I'm closing it now :). Thank you again for the help everyone!


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.