https://github.com/doitsujin/dxvk/commit/f869881f558d4abac12018fbf59c896643e21de3 related, same was happening on DX11 as well.
Game bug, it's really crazy that they ship the same broken shaders in four games in a row with literally no changes.
Guess we'll have to port the workaround from DXVK in some way.
Does this branch fix the issue? https://github.com/HansKristian-Work/vkd3d-proton/tree/f1-2020-war
Automatic builds are available there also.
Hi @Joshua-Ashton,
I can confirm that the f1-2020-war branch build provided here does indeed resolve this issue.
Thanks.
| f1-2020-war |
|---|
![]() |
Nice, made it a PR: https://github.com/HansKristian-Work/vkd3d-proton/pull/615
proton 6.3-2x1 2021-04VKD3D_SHADER_DEBUG=trace):x1 2021-04
Description:
F1® 2020 (1080110) in DirectX 12 mode exhibits the same artifacts that were originally reported with DXVK on it and various other F1 franchise titles (F1 2018, F1 2020). The issue is most notable when viewing vehicules in the "Showroom" or editing your character in the "Customisation" sections (available from the main menu).
Please let me know if any additional information is required or if additional testing is needed.
Notes
Software information
F1® 2020 (1080110)
System information
OS: Ubuntu 20.04
GPU: Nvidia GeForce GTX 1060 / AMD Radeon RX 580
Beta Drivers: 460.67 / 21.0.2~kisak1~b
Wine version: Proton 6.3-2
VKD3D-Proton version: 2.2 / Master (eca8e49)
Log files
VKD3D Log (w/ VKD3D_SHADER_DEBUG=trace): F1 2020 - VKD3D.zip
API Trace
Trace: (Title crashes on launch when attempting to trace using https://github.com/Joshua-Ashton/apitrace/releases/tag/d3d12-alpha-2)