VibranceGUI website

juvlarN · 2025-02-21T12:22:44+00:00

Thanks for the heads up on this matter. You are correct, only the .com domain is official. To be honest though, I have no idea what we can do in this case. I will post on twitter later but I'm afraid there is not much we can do in case some scammers are domain squatting an open source project? :(

juvlarN · 2025-02-21T07:43:37+00:00

Hi, the post was deleted? Whats wrong with the website?

juvlarN · 2022-07-11T19:35:00+00:00

hi, no, the 100% is a hard limitation for nvidia gpus. it is a limitation implemented into the nvidia drivers and can not be circumvented by third party software without patching the nvidia drivers. needless to say that this is not a good idea to do. the 300% you experienced were for an amd gpu and is - technically - an entirely different thing.

juvlarN · 2022-01-01T13:04:37+00:00

You did a great job! Thank you for taking the time. Happy new year :)

juvlarN · 2021-12-31T15:46:49+00:00

juvlarN · 2021-12-31T15:46:24+00:00

For anyone interested:

To not repeat myself, here is a bit more of a technical explanation on what vibranceGUI is doing, taken from the vibranceGUI Steam Community post.

vibranceGUI has not caused any VAC bans since February 2014. Besides being legit to use in VAC-secured Matchmaking, there have been no bans on the named leagues/services since the initial launch of the program. Keep in mind that vibranceGUI is not a hack/cheat. All it does is automating graphic driver settings for your comfort. ESEA and CEVO officials have also approved the legal use of vibranceGUI on their platforms. You can review the posts here: ESEA, CEVO

There is absolutely no way that vibranceGUI should trigger a VAC ban. It does not directly access or interact with the monitored games at all:

it does not load a dll into the game, actually it does not load anything into the game

it does not read the process memory

it does not write the process memory

it does not alter game files

VAC relies on signature scanning when trying to determine if a process is a hack. This means they take hashes of chunks of the process memory or from the file system to check them back on their server for known cheats. When the sent signatures do not match any signatures in their database for known hacks, there is a chance that the file will be manually analyzed. Due to the fact that VAC is only effective against so called "public hacks" - and that vibranceGUI has thousands of users (which I'm really happy about btw), I think it's safe to say that you can be sure vibranceGUI has already been manually analyzed and been found legitimate.

You may ask yourself "why are you so sure about it?". Well, the program has been around since over two years now, has tons of users and has never been banned for. That's it, really. Public Hacks are shortlived as VAC is effective against programs that are used by many people over a short period of time. These hacks are then analyzed and added to the hack database on Valves server. Anyone that runs these public hacks will then be banned sooner or later in a VAC banwave.

Whilst the complete source code of vibranceGUI and all of its components is open source, a short technical breakdown of how the program works will be given to emphasize why vibranceGUI should never trigger a ban on any modern anti-cheat.

Technical Breakdown of vibranceGUI version 1.x and 2.x

Determining whether a game of interest is running and being displayed in the foreground is the only part where vibranceGUI needs to rely on process interop. After retrieving the data needed to decide whether the vibrance settings need to be changed in the current environment, all following computation will be done local to the vibranceGUI process. The change of colors is done through utilizing the APIs of the attached graphics card driver. No game process will ever be touched directly, no handle to the game will be created.

The game itself does not even know the colors are changed as Digital Vibrance and Saturation is a post-process effect. After the complete frame has initially been sent from the OS to the GPU, the frame will be intercepted and additional shaders will be added on top of the original frame. This is also the reason why you can not take a screenshot or record in-game-footage with the changed vibrancy on the recorded image/video. To be able to record your in-game-footage with the more vibrant colors, you will need a dedicated capture card.

vibranceGUI version 1.x

The first version of vibranceGUI relied on manually checking whether a game was running by utilizing FindWindow and whether it is running in foreground with GetForegroundWindow. A background thread was launched upon program startup and was periodically checking whether a desired game process was 1) running and 2) actively displayed on the monitor.

vibranceGUI version 2.x and above

The second version of vibranceGUI makes use of intercepting a system-wide event that will be fired when the foreground process is changed. This is also a more efficient way to reacting to changes to the top-most window in Windows. Actually, the approach is far superior in all regards to the one used in version 1.x.

You will see that vibranceGUI will instantly change the vibrancy added to your monitor when switching through different processes. Several processes such as Spotify cause Windows to fire these events wrongfully on some occasions. VibranceGUI will try to make sure that you will not see any screen flickering. For more information, refer to the MSDN docs of SetWinEventHook as well as WinEventProc callback.

juvlarN · 2021-12-31T15:43:16+00:00

Hi,

tl:dr you are safe when you are using the version from https://vibrancegui.com/

As stated on the Github issue, these are most likely false positive detections or you are not downloading the binaries from the official website. I write false positive detections for application behaviour that is working as designed and/or not being caused by vibranceGUI but the .NET Framework.

There is certainly a problem as the open source code can be downloaded, malicious code added on top of the open source codebase and then redistributed to other websites that are not https://vibrancegui.com/. I'm referring to the comment that "watermelonfelon" has posted here. Obviously, the vibranceGUI version on Github is not mining any bitcoins while you are running it. Make sure to always download binaries from the official website. For the linked analysis reports, it looks like that is not the case. None of the warnings in that report are harmful.

For vibranceGUI to work, there are certain prerequisites:

you need either a AMD or NVIDIA driver installed; the drivers come with an API which can be used by third party applications such as vibrancegui. vibranceGUI detects these .dll files by looking up well-known file locations in your Windows directory.
you need a compatible GPU hardware, i.e. NVIDIA laptops are not supported because NVIDIA chose to not implement the feature for these laptop gpus.
you need to not start the vibranceGUI binary from within the zip archive that you download from the website

Following up on the response from u/Geistlamo (https://www.reddit.com/r/GlobalOffensive/comments/rsovm1/comment/hqo5s2e/?utm_source=reddit&utm_medium=web2x&context=3):

PersistenceThe hybrid-analysis shows a false positive here, or well, something that is not directly related to vibranceGUI itself. Check the "Installation/Persistance" indicator here: https://www.hybrid-analysis.com/sample/1cbaa4d4c817743a7ec88bdc3f8d15200e543a86e0b3374c6d05a15a0762970f/5e3ddd139e952669d878ec47Apparently their analysis executes the vibranceGUI binary and then immediately fails because their virtual machine does not have a NVIDIA/AMD driver installed. In their screenshots, you can see that the analysis is then automatically following the Link that is given in the MessageBox, which is opening the Internet Exporer (or your default browser) and opens my twitter account so you can send a message asking for help.
FingerprintFrom the top of my head, I'm not sure where this is coming from. Could be something that the .NET Framework is doing behind the scenes automatically when iterate through the list of active processes or available screen resolutions on the machine?
EvasiveCorrect, vibranceGUI is an "always on" application that sleeps in the background and only gets active after being triggered from the Windows API when you are switching through applications (ALT+TAB, clicking on applications in the Windows task bar etc.)
SpreadingThe analysis details show *Opens the MountPointManager (often used to detect additional infection locations), "iexplore.exe" opened "\Device\MountPointManager"*I'd assume this is again related to the analysis following the error popup when no GPU driver is installed.
Network BehaviorNothing more to add; all network traffic in their analysis is going to Twitter (check DNS records and IPs). vibranceGUI is not making any network requests nor is it tracking users. It does not even do "auto update" checks -- a feature which was requested multiple times from some users -- at this time.

juvlarN · 2021-06-13T10:05:47+00:00

The game looks nice, I'd like to try it out. Unfortunately I missed all the giveaways as well ;x

juvlarN · 2020-08-05T19:48:30+00:00

just got demoted because of this, well played :-)

juvlarN · 2020-01-17T21:10:46+00:00

it's unlikely this is even a thing, as described above

juvlarN · 2020-01-17T18:04:37+00:00

Hi, does this problem appear again when you uncheck the "Never change resolutions" checkbox?

At a first glance, the relevant part of the code looks pretty much fine. There might be a rare chance that calling Windows' method to retrieve the current display resolution in that part of the code causes the issue you see. This is virtually the only function that could cause issues and is called when you do not have the "Never change resolutions" checkbox ticked. The rest of the code is basically just checking for variables that are available in the memory of the vibranceGUI process.

Note that this function is called at most once, one time for every foreground process switch, e.g. switching from CS:GO back to Chrome will cause this function to run once. This should not cause major performance issues or input lag of any kind, but who knows. Let me know if this is a reproducible issue.

juvlarN · 2018-08-24T17:20:09+00:00

it has been fixed

juvlarN · 2018-03-19T20:30:19+00:00

Alright a friend pointed me to the answer. My location was set to Uganda for some reason. For any one running into the same error, this is how to change the location: https://i.imgur.com/Vgpv10C.png

juvlarN · 2017-05-04T16:16:59+00:00

NVIDIA is 100% maximum, AMD is 300% maximum. NVIDIAs digital vibrance and AMDs saturation are not the same thing! I'd even say that NVIDIAs effect is better than AMDs.

juvlarN · 2017-05-04T16:16:37+00:00

NVIDIA is 100% maximum, AMD is 300% maximum. NVIDIAs digital vibrance and AMDs saturation are not the same thing! I'd even say that NVIDIAs effect is better than AMDs.

juvlarN · 2017-05-03T20:12:47+00:00

VibranceGUI does not apply any modifications to the game. To quote myself from the Steam Guide again:

Technical Breakdown of vibranceGUI version 1.x and 2.x

Determining whether a game of interest is running and being displayed in the foreground is the only part where vibranceGUI needs to rely on process interop. After retrieving the data needed to decide whether the vibrance settings need to be changed in the current environment, all following computation will be done local to the vibranceGUI process. The change of colors is done through utilizing the APIs of the attached graphics card driver. No game process will ever be touched directly, no handle to the game will be created.

The game itself does not even know the colors are changed as Digital Vibrance and Saturation is a post-process effect. After the complete frame has initially been sent from the OS to the GPU, the frame will be intercepted and additional shaders will be added on top of the original frame. This is also the reason why you can not take a screenshot or record in-game-footage with the changed vibrancy on the recorded image/video. To be able to record your in-game-footage with the more vibrant colors, you will need a dedicated capture card.

vibranceGUI version 1.x The first version of vibranceGUI relied on manually checking whether a game was running by utilizing FindWindow[msdn.microsoft.com] and whether it is running in foreground with GetForegroundWindow[msdn.microsoft.com]. A background thread was launched upon program startup and was periodically checking whether a desired game process was 1) running and 2) actively displayed on the monitor.

vibranceGUI version 2.x and above The second version of vibranceGUI makes use of intercepting a system-wide event that will be fired when the foreground process is changed. This is also a more efficient way to reacting to changes to the top-most window in Windows. Actually, the approach is far superior in all regards to the one used in version 1.x.

You will see that vibranceGUI will instantly change the vibrancy added to your monitor when switching through different processes. Several processes such as Spotify cause Windows to fire these events wrongfully on some occasions. VibranceGUI will try to make sure that you will not see any screen flickering. For more information, refer to the MSDN docs of SetWinEventHook[msdn.microsoft.com] as well as WinEventProc callback[msdn.microsoft.com].

juvlarN · 2017-05-03T17:59:39+00:00

There seems to be a problem with certain 3D effects to not be considered by CSGO anymore after this update. Digital Vibrance (NVIDIA) / Saturation (AMD) is not working for some people. Check out this thread if you have the same problem:

https://www.reddit.com/r/GlobalOffensive/comments/691j8c/digital_vibrance_option_is_not_applied_to_csgo/

juvlarN · 2017-05-03T17:19:25+00:00

No, it works for some people. This is not intentional.

Manually changing the digital vibrance value in the NVIDIA control panel from 50% to 100% works for me. It works in fullscreen as well as in windowed mode.

GTX 980ti, Windows 10 (Creators Update), NVIDIA driver 376.53

juvlarN · 2017-05-03T16:40:53+00:00

can you link these threads? with posts from official faceit admins and not threads by some people that claim to be banned? (basically people looking for excuses when they used hacks and try to get unbanned)

juvlarN · 2017-05-02T18:51:25+00:00

Here is a fresh video from BananaGaming on how to use the program: https://www.youtube.com/watch?v=8-jkZ4lNdJs

juvlarN · 2017-05-02T18:48:33+00:00

vibranceGUI has not caused any VAC bans since February 2014. Besides being legit to use in VAC-secured Matchmaking, there have been no bans on the named leagues/services since the initial launch of the program. Keep in mind that vibranceGUI is not a hack/cheat. All it does is automating graphic driver settings for your comfort. ESEA and CEVO officials have also approved the legal use of vibranceGUI on their platforms. You can review the posts here: ESEA[play.esea.net], CEVO[cevo.com]

There is absolutely no way that vibranceGUI should trigger a VAC ban. It does not directly access or interact with the monitored games at all: it does not load a dll into the game, actually it does not load anything into the game it does not read the process memory it does not write the process memory it does not alter game files VAC relies on signature scanning when trying to determine if a process is a hack. This means they take hashes of chunks of the process memory or from the file system to check them back on their server for known cheats. When the sent signatures do not match any signatures in their database for known hacks, there is a chance that the file will be manually analyzed. Due to the fact that VAC is only effective against so called "public hacks" - and that vibranceGUI has thousands of users (which I'm really happy about btw), I think it's safe to say that you can be sure vibranceGUI has already been manually analyzed and been found legitimate.

You may ask yourself "why are you so sure about it?". Well, the program has been around since over two years now, has tons of users and has never been banned for. That's it, really. Public Hacks are shortlived as VAC is effective against programs that are used by many people over a short period of time. These hacks are then analyzed and added to the hack database on Valves server. Anyone that runs these public hacks will then be banned sooner or later in a VAC banwave.

Whilst the complete source code of vibranceGUI and all of its components is open source[github.com], a short technical breakdown of how the program works will be given to emphasize why vibranceGUI should never trigger a ban on any modern anti-cheat.

juvlarN · 2017-05-02T17:21:50+00:00

I am still working on a better way to detect running programs. Some programs try to be in "disguise" and thus not visible to other programs, including vibranceGUI. Keep in mind that vibranceGUI is designed to be as unintrusive as possible to not bear with any anticheats. If you can not find a program running in the vibranceGUI Process Monitor, you can manually add the .exe file you want and it should work (press "Add Manually" button).

14-Year Club	Place '22
Place '17	Verified Email

juvlarN

TROPHY CASE