Bug 111015 - [Vampyr]Rendering issue ingame
Summary: [Vampyr]Rendering issue ingame
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/Vulkan/radeon (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: mesa-dev
QA Contact: mesa-dev
Depends on:
Reported: 2019-06-27 15:57 UTC by Maxime
Modified: 2019-06-27 19:32 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Vampyr RADV renderer (3.63 MB, image/png)
2019-06-27 15:57 UTC, Maxime
Vampyr AMDVLK renderer (3.54 MB, image/png)
2019-06-27 15:58 UTC, Maxime

Description Maxime 2019-06-27 15:57:54 UTC
Created attachment 144672 [details]
Vampyr RADV renderer


There are graphical glitches in game when i play at Vampyr with RADV+DXVK.
As you can see on the both screenshot, this issue appears only with RADV, AMDVLK is not affected.

I share you the link from my Google Drive to download the Renderdoc capture :

Thanks for your help,
Comment 1 Maxime 2019-06-27 15:58:26 UTC
Created attachment 144673 [details]
Vampyr AMDVLK renderer
Comment 2 Samuel Pitoiset 2019-06-27 16:00:42 UTC
What about RADV_DEBUG=nohiz and RADV_DEBUG=nodcc?
Comment 3 Samuel Pitoiset 2019-06-27 16:22:14 UTC
What mesa sha1? Are you able to reproduce the rendering issue with the capture?
Comment 4 Maxime 2019-06-27 16:47:43 UTC
(In reply to Samuel Pitoiset from comment #3)
> What mesa sha1? Are you able to reproduce the rendering issue with the
> capture?

1- I use Mesa-Git @ commit 62c60595844ba206dcf0f18451609e03ee65a7d3
2- With "export RADV_DEBUG=nodcc" --> Issue still exist
3- With "export RADV_DEBUG=nohiz" --> Issue still exist
4- When i launch qtrenderdoc and open the capture, the issue appears.
Comment 5 Samuel Pitoiset 2019-06-27 16:54:30 UTC
What LLVM?
Comment 6 Maxime 2019-06-27 17:34:42 UTC
Right, i used an old version of LLVM9-git. I update it to commit c71a1c39025ae135543eb6c2130e8f628b380dbe and the issue is fixed. ;-)
Comment 7 Samuel Pitoiset 2019-06-27 19:32:42 UTC
Great thanks!

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.