The more recent viewers for Linux appear to be giving me some partial UI corruption, mostly anything related to font rendering, on Kubuntu 26.04. It does not happen on Alchemy 7.1.9.2516. I only switched to Linux a couple of weeks back after Windows Update ruined my Windows 11 install - this problem does not appear on Windows.

There is no easy reproducible pattern, it can take 15 to 30 minutes before the corruption starts, however it is directly related to the debug settings CollectFontVertexBuffers and CollectUIImageVertexBuffers. Switching the first from true to false causes the corruption to change immediately, while switching the latter to false dramatically reduces the corruption - there's still some very minor corruption happening, but causing the window to completely re-draw like a size change removes it, so the viewer is fine to use. Setting RenderVBOEnable also reduces the corruption even if the former two are still enabled (I assume that's a global vertex buffer setting).

Screenshots shows the worst of it when both settings are left on after 30 minutes and the UI is generally "used". Using the UI causes the corruption to appear faster. Some other UI elements start showing incorrect triangle colours, this is how I knew it was vertex buffer related. Inworld 3D rendering is unaffected, only things related to the UI.

Have tried updating the NVIDIA driver to 615.71.09, but problem still persists.

UPDATE 12/11/2026 - It turns out SOME meshes inworld are also exploding into vertices as well, like some of the older vertex buffer bugs that the viewer used to have with AMD cards. Flicking object LOD to lowest then back to highest temporarily fixes it. Again, this does not happen with Alchemy, and it also does not happen in The Elder Scrolls Online, Guild Wars 2 or Palworld, which run perfectly fine under Proton-GE.

UPDATE 13/11/2026 - Running the Windows viewer under Proton-GE does not cause this problem. I believe Proton is translating OpenGL to Vulkan in this case, especially with the insanely high performance I've never seen from SL before. This would most likely mean an OpenGL bug with the NVIDIA driver?