From f88c0f53270cba5476eae001daff8005e9b9a3e8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Vladim=C3=ADr=20Vondru=C5=A1?= Date: Tue, 25 Mar 2025 22:47:27 +0100 Subject: [PATCH] GL: update workaround description with additional info. --- src/Magnum/GL/Implementation/driverSpecific.cpp | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/src/Magnum/GL/Implementation/driverSpecific.cpp b/src/Magnum/GL/Implementation/driverSpecific.cpp index bbf9542ef..3c4a3d15e 100644 --- a/src/Magnum/GL/Implementation/driverSpecific.cpp +++ b/src/Magnum/GL/Implementation/driverSpecific.cpp @@ -221,12 +221,12 @@ constexpr Containers::StringView KnownWorkarounds[]{ returns false instead of segfaulting. */ "nv-egl-crashy-query-device-attrib"_s, -/* On NV driver 572.83, DSA buffer APIs don't work. This was reported on - Windows with a NVIDIA RTX 2000 ADA generation graphics card, and downgrading - to an older driver version (September 13 2024, not sure which version) fixes - that. On Arch and 570.86 it doesn't happen. Not sure if it's really specific - to that GPU generation or it's just a regression in the platform-independent - GL frontend. +/* On NV driver 572.83 and likely 566.24 as well, DSA buffer APIs don't work. + This was reported on Windows with a NVIDIA RTX 2000 ADA generation graphics + card, and downgrading to 556.39 fixes that. On Arch, RTX 3050 and 570.86 it + doesn't happen. Not sure if it's really specific to that GPU generation or + it's just a regression in the platform-independent GL frontend that affects + only some cards somehow. The behavior is similar to the one explained below in the "intel-windows-crazy-broken-buffer-dsa" workaround (ImGui rendering