Closed danmons closed 1 year ago
You should report that to the driver people, I doubt there is an actual vkQuake issue. I couldn't test it anyway.
One thing to try would be r_indirect 0
and r_gpulightmapupdate 0
OK thanks, I'll report it to the Mesa developers.
Following through on your suggestions:
r_indirect 0
: this solved certain textures from vanishing.
r_gpulightmapupdate 0
: this solved the psychedelic wall textures.
I'll create an issue in mesa gitlab's instance with this information.
On a Raspberry Pi 4B running X11 and GCC12, I've tested the following combinations:
And compiling vkQuake directly from git (I've been pulling and re-testing both vkQuake and Mesa for about a month now).
The various text overlays, weapon models, and character models all look fine.
Walls, columns, floors etc all have texture rendering errors, as captured in the attached screenshots. Changing different lighting, rendering and texture options in
vkQuake.cfg
makes no different to the outcome that I can find. Likewise, no difference if fullscreen, borderless fullscreen or windowed.Unsure if it's a Mesa problem or a vkQuake problem, however other Vulkan demos (Sascha Willems demos, vkcube, vkmark2, etc) all render as expected.
[edit] If I follow the exact same build process on my Ryzen laptop with Radeon 5600 video card running Arch Linux and Mesa, no problems. Renders as expected.