vibranceGUI 2.10.3
vibranceGUI v2.10.3
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.3).
On v2.9.0 or v2.10.0 with an NVIDIA card? Those x64 builds could not detect your GPU at all. Take this one. (Fixed in v2.10.1.)
vibranceGUI now tells you when there is a new version
That is the whole feature. On startup it asks GitHub what the newest release is, and if yours is older it shows a tray notification. Click it and your browser opens the release page.
Nothing is downloaded, installed or executed. There is no auto-installer and there will not be one while these builds are unsigned — an unsigned program that fetches and runs another unsigned program is exactly what malware looks like to an antivirus, and it would let a bad release push itself onto everyone automatically instead of only onto people who chose it. The x64 bug in v2.9.0 and v2.10.0 is the argument against that, not for it. For an app you install by unzipping it, your browser is the updater.
What it sends
A user agent string. That is all — no identifier, no hardware details, nothing about you or your machine. GitHub sees an anonymous request for a public page, the same as if you opened the releases page yourself.
It runs at most once every 12 hours, on a background thread, gives up after 8 seconds, and stays silent about its own failures — no network, a proxy or a rate limit will never produce an error box.
To turn it off: untick "Check for a new version on startup" in the settings, or set updateCheckEnabled=False in %APPDATA%\vibranceGUI\vibranceGUI.ini.
It is on by default, deliberately. The people most in need of hearing that v2.10.1 exists are the ones running a build that cannot detect their graphics card, and they had no way to find out.
The honest caveat
This release cannot reach the people it was built for. If you are on v2.9.0 or v2.10.0, that build has no update check, so nothing will ever tell you it is broken. The check only starts working from this version forward. If you know someone running an older x64 build, telling them is still the only thing that works.
Everything else
Unchanged from v2.10.2 and the releases before it, whose notes still apply in full — including the caveats about what has and has not been watched working on real hardware. The restore-after-a-crash behaviour still has not been seen working end to end by anyone, and the x64 build still has not been played with beyond starting correctly.
782 automated checks across sixteen fixtures, green on both architectures. They drive fakes and stubs, not a real GPU driver, display or game. The update check was also exercised against the live GitHub API, and against a dead host, a 404 and a black-holed address to confirm it fails silently rather than hanging your startup.
Reporting problems
https://github.com/SwatX18/vibranceGUI/issues — the form asks for the title bar string first, which names the vendor, architecture and version in one line.
If you run 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.