Skip to content

vibranceGUI 2.10.2

Choose a tag to compare

View all tags
@SwatX18 SwatX18 released this 27 Sep 13:25
· 9 commits to master since this release
v2.10.2
160aefc
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

vibranceGUI v2.10.2

Already on v2.10.1? There is no functional change here. Upgrade when convenient. If you are on v2.9.0 or v2.10.0 with an NVIDIA card, take this — those x64 builds could not detect your GPU at all, which v2.10.1 fixed.

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.2).

When something fails, the message now tells you something

The dialog that greeted anyone hitting the v2.10.0 x64 bug said their driver was not installed properly and offered to open Twitter. Their driver was fine. The app had asked Windows for the wrong file and had no way to say so, because the message was a fixed string that could not name a file name.

It now names what it looked for and which build it is:

This is the x64 build. It looked for "nvapi64.dll" (NVIDIA) and "atiadlxx.dll" (AMD)
and could load neither.
Windows reported: The specified module could not be found (error 126)

On that particular error — a file not found — it adds that this is often vibranceGUI's own fault rather than your driver's, and asks you to try the other architecture. "The x86 build works on this same machine" is the single most useful thing anyone can tell me; it separates a bug in this app from a problem with your system in one step, with no tools. It is exactly what made the last report solvable in an afternoon.

"Yes" now opens the bug report form rather than a Twitter profile.

The dialog for machines with both NVIDIA and AMD drivers installed also stopped advising people to delete nvapi.dll on 64-bit Windows — that is the 32-bit file, not the one a 64-bit application uses. It now names the right files and the folder each one lives in. Advice to delete a system file should at least name the right file.

A correction in the README

It said the x64 build had been "started on a real NVIDIA GPU, where it resolves the adapter and initialises correctly". That was written from a machine with both an AMD chipset and an NVIDIA card, which takes a different detection path and never reached the broken code. On an NVIDIA-only machine — most people — the x64 build failed every time, for two releases. The README now says what actually happened.

Everything else

Unchanged from v2.10.1 and v2.10.0, 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.

747 automated checks across fifteen fixtures, green on both architectures. They drive fakes and stubs, not a real GPU driver, display or game.

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, and none of these bugs are either.

This is a fork build and it is unsigned. It is not an official juv release.

Assets 4
Loading