vibranceGUI 2.10.1
vibranceGUI v2.10.1
If you are on the x64 build of v2.9.0 or v2.10.0 with an NVIDIA card, this release is the one you want. Those two builds could not detect an NVIDIA GPU at all.
Two downloads. Take x64 unless you are on 32-bit Windows. Each zip is two files, no installer — unzip anywhere and run vibrance.GUI.exe. The title bar names the build: vibranceGUI (NVIDIA, x64, 2.10.1).
The x64 build now finds your NVIDIA card
v2.9.0 and v2.10.0 shipped an x64 build that stopped at startup with:
Failed to determine your Graphic GraphicsAdapter type (NVIDIA/AMD). Make sure you have installed a proper GPU driver.
Your driver was fine. The app asked Windows for the wrong file.
nvapi.dll is the 32-bit NVIDIA API entry point, and on 64-bit Windows it exists only in SysWOW64. The 64-bit driver installs nvapi64.dll into System32 instead. The 64-bit build was asking for nvapi.dll, which a 64-bit process cannot see, so Windows answered "the specified module could not be found" — and the app concluded you had no NVIDIA driver at all.
The x86 build was never affected, which is why running the 32-bit download on the same machine worked. That is also the workaround if you are stuck on an older build.
Why it took two releases to notice. The app checks for a machine with both vendors' drivers first, and on such a machine it identifies your GPU a different way that never touches the broken code. The development machine is one of those — an AMD chipset with an NVIDIA card. It only fails when NVIDIA is the only vendor present, which is most people, but not the machine it was tested on.
Thanks to the person who reported it with the exact error text and the detail that the x86 build worked on the same hardware. That combination made it a ten-minute diagnosis instead of a guessing game.
Everything else
No behaviour changes. v2.10.0's display-restore-after-a-crash work, the HDR level, resolution restore and colour settings are all exactly as they were — see the v2.10.0 notes, which still apply in full, including the caveats about what has and has not been watched running on real hardware.
Under the hood both driver file names are now chosen by the running process's bitness rather than hardcoded, matching what the native NVIDIA library already did, and the self-test suite gained three checks that pin the rule in both directions so the x86 build cannot be broken while fixing x64. The suite is at 735 checks across fifteen fixtures, green on both architectures.
Reporting problems
Issues are open on this fork now — they were switched off until recently, which is on me. There is a bug form that asks for the title bar string first:
https://github.com/SwatX18/vibranceGUI/issues
If you are running an official build from vibrancegui.com rather than one of mine, report to juv's tracker instead — none of this fork's changes are in that build.
This is a fork build and it is unsigned. It is not an official juv release.