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

GT5 has broken text rendering on RADV #8642

Closed
xddxd opened this issue Jul 27, 2020 · 12 comments · Fixed by #9471 or #13136
Closed

GT5 has broken text rendering on RADV #8642

xddxd opened this issue Jul 27, 2020 · 12 comments · Fixed by #9471 or #13136
Assignees
Labels
Driver: RADV (Mesa) Open-source AMD Vulkan Mesa driver OS: Linux

Comments

@xddxd
Copy link
Contributor

xddxd commented Jul 27, 2020

Gran Turismo 5 BCES00569 has broken text rendering in the menu on the RADV driver, when testing on Windows 10 with the AMD 20.7.2 driver it renders correctly.

RADV:
unknown
RPCS3.log.gz
RSX capture: https://www.dropbox.com/s/75q41jnrc6y0kq8/BCES00569_20200727125243_capture.7z?dl=0
Windows:
Screenshot_10
RPCS3.log.gz
RSX capture: https://www.dropbox.com/s/t4zuj3qaoikh9df/BCES00569_20200727130153_capture.7z?dl=0

EDIT: tested with AMDVLK too, it renders correctly.

@AniLeo
Copy link
Member

AniLeo commented Jul 29, 2020

Mesa 20.1.3

Can you try with mesa-git? Maybe it has been fixed in the meantime

If this is a driver bug, may need to be reported on Mesa directly

Can you also test with RADV_PERFTEST=aco vs RADV_PERFTEST=llvm (Note that Mesa 20.1 has LLVM as default and Mesa 20.2 has ACO as default)

@xddxd
Copy link
Contributor Author

xddxd commented Jul 29, 2020

Mesa 20.1 ACO
mesaaco
I'm still working on getting mesa-git.

@xddxd
Copy link
Contributor Author

xddxd commented Jul 29, 2020

mesa-git 20.2 ACO:
gitaco
mesa-git 20.2 LLVM:
gitllvm
the glitch is present

@AniLeo
Copy link
Member

AniLeo commented Jul 29, 2020

Tagging @kd-11 for triaging

@Megamouse Megamouse added the Driver: AMD Vulkan Proprietary or amdvlk AMD Vulkan driver label Aug 25, 2020
@pendingchaos
Copy link

RADV_PERFTEST=llvm doesn't do anything on Mesa 20.2 and newer btw. The env to disable it is RADV_DEBUG=llvm

@AniLeo
Copy link
Member

AniLeo commented Dec 18, 2020

Just to confirm, can you retest this with Strict Rendering Mode enabled and see if validation layers catch anything?

To turn on validation layers you need to enable Debug Output on Settings - Debug

And you need to have the validation layers package, vulkan-validation-layers on archlinux for example.

@AniLeo
Copy link
Member

AniLeo commented Dec 18, 2020

Ok, I've retested this

Mesa: mesa-git 21.0.0_devel.132192.04c7fce799a-1
GPU: AMD RADV SIENNA_CICHLID (LLVM 11.0.0) (RX 6800 XT)

ACO

SRM On
image

SRM Off
image

LLVM

SRM Off
image

There are a few validation errors regardless of SRM being enabled or disabled:

@kd-11
Copy link
Contributor

kd-11 commented Dec 18, 2020

This is very likely triggered by fbo loops which go away with SRM enabled. There is no actual fix other than to make SRM always enabled and eat a huge perf loss (input attachments). On PS3 this setup just works and on windows they have workarounds because a lot of software uses this technically incorrect access pattern.

@AniLeo
Copy link
Member

AniLeo commented Dec 24, 2020

Reopening and moving the unrelated spec violations to another ticket: #9495

@AniLeo AniLeo reopened this Dec 24, 2020
@AniLeo AniLeo added Driver: RADV (Mesa) Open-source AMD Vulkan Mesa driver and removed Driver: AMD Vulkan Proprietary or amdvlk AMD Vulkan driver labels Jan 20, 2022
@kd-11
Copy link
Contributor

kd-11 commented Sep 26, 2022

We finally got the framebuffer loops extension in mesa-git. This needs an update.

@xddxd
Copy link
Contributor Author

xddxd commented Sep 27, 2022

Same behavior on latest mesa-git RADV

@kd-11
Copy link
Contributor

kd-11 commented Dec 27, 2022

This is caused by a missing barrier between subsequent virtual subpasses. The game has a very weird font rendering mechanism where we basically have stencil_draw->stencil_draw...->color_draw + stencil_read->stencil_draw. All the while we have a single RP with the same RTV+DSV bound with the DSV being cyclic. No barrier is injected between the cyclic stencil draw and the color draw with stencil read which causes this data hazard.
There is an existing cyclic ref tracking system that is supposed to inject the barriers but this is not working as intended and needs an overhaul.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Driver: RADV (Mesa) Open-source AMD Vulkan Mesa driver OS: Linux
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants