It seems to render correctly here, so it might be a driver issue, can you try RADV_DEBUG=nohiz,nodcc or using amdvlk?
RADV_DEBUG=nohiz,nodcc fixed it for me, thanks!
@CarnageDevs please open a bug report about that here then: https://gitlab.freedesktop.org/mesa/mesa/-/issues
Ideally also try with only nohiz or only nodcc to narrow down which of them fixes it and mention that and that the issue seems to be exclusive to RDNA3 in the Mesa bug report.
Opened a bug report: https://gitlab.freedesktop.org/mesa/mesa/-/issues/8127
Seems like only nodcc is necessary to get the textures rendering correctly
proton experimentalx1 2023-01RADV_DEBUG=nohiz,nodccx2 2023-01DXVK_FRAME_RATE=60x1 2023-01PROTON_USE_WINED3D=1x1 2023-01PROTON_USE_WINED3D=1 %command%x1 2023-01
Upon starting a new game in Prototype 2, all the textures are seemingly rendered black:
Software information
Prototype 2 (Steam)
In-game graphics settings:
Resolution: 1920x1080
Anti-Alias Level: High
VSync Enabled: On
Shadow Detail: High
Ambient Occlusion: On
Motion Blur: On
Effects Quality: High
Prop Draw Distance: High
Steam launch options:
DXVK_FRAME_RATE=60 taskset -c 0-7 %command%System information
Apitrace file(s)
Trace was made under Linux, I included both a trace done with
PROTON_USE_WINED3D=1 %command%as well as one without (using DXVK). The WineD3D trace crashed after the first loading screen upon starting a new game, as soon as the first cutscene showed. DXVK trace was able to get past those cutscenes to the start of the game where the rendering issues are present.Log files