Yes we’ve run into this before, and came to the same conclusion that it is an NVIDIA driver issue. See this thread:
Unfortunately as a plug-in, we’re stuck with the DPI-awareness of the host process that we’re running in and can’t change it via SetProcessDpiAwarenessContext() as this would break the host’s scaling. We need to use SetThreadDpiAwarenessContext() to temporarily change the thread’s awareness and then set it back again. Since f6338c0f we’re doing this via the ScopedThreadDPIAwarenessSetter, but that thread implies that this won’t work on NVIDIA machines…