Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

F1® 2020 (1080110) - Artifacts on various assets (Cars & Character) #611

Closed
ZereoX opened this issue Apr 9, 2021 · 5 comments
Closed
Assignees

Comments

@ZereoX
Copy link

ZereoX commented Apr 9, 2021

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).

VKD3D-Proton Windows
F1 2020 - DirectX 12 - Proton 6 3-2 F1 2020 - DirectX 12 - Windows

Please let me know if any additional information is required or if additional testing is needed.

Notes

  • On Windows, the title crashes at launch or remains stuck on a black screen with VKD3D-Proton.

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)

@knikkinen
Copy link

doitsujin/dxvk@f869881 related, same was happening on DX11 as well.

@doitsujin
Copy link
Collaborator

doitsujin commented Apr 11, 2021

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.

misyltoad added a commit that referenced this issue Apr 12, 2021
Signed-off-by: Joshua Ashton <joshua@froggi.es>

Closes: #611
misyltoad added a commit that referenced this issue Apr 12, 2021
Signed-off-by: Joshua Ashton <joshua@froggi.es>

Closes: #611
@misyltoad
Copy link
Collaborator

Does this branch fix the issue? https://github.com/HansKristian-Work/vkd3d-proton/tree/f1-2020-war

Automatic builds are available there also.

@misyltoad misyltoad self-assigned this Apr 12, 2021
@ZereoX
Copy link
Author

ZereoX commented Apr 12, 2021

Hi @Joshua-Ashton,

I can confirm that the f1-2020-war branch build provided here does indeed resolve this issue.

Thanks.

f1-2020-war
image

@misyltoad
Copy link
Collaborator

Nice, made it a PR: #615

misyltoad added a commit that referenced this issue Apr 12, 2021
Signed-off-by: Joshua Ashton <joshua@froggi.es>

Closes: #611
adamdmoss pushed a commit to adamnv/vkd3d-proton that referenced this issue Apr 27, 2023
Signed-off-by: Joshua Ashton <joshua@froggi.es>

Closes: HansKristian-Work#611
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants