<b><span style="text-decoration:underline;">Edit: September 22nd 2013: Added in more workarounds sections: Windowed Borderless Gaming & CPKeeper (Color Profile Keeper).</span></b><br><br><br>

Edit: May 1st 2012: Had some success with this new borderless window tool <a href="http://forums.steampowered.com/forums/showthread.php?t=2675769" target="_blank">http://forums.steampowered.com/forums/showthread.php?t=2675769</a><br><br><br><br><br>

Original post:<br>

This is an on-going issue, <i>many</i> people have this problem, yet, literally for <b>years,</b> Nvidia has not done anything to remedy the situation...<br><br>

As many of you probably know, getting a game to keep your calibrated colours in fullscreen can be a chore if the game/video driver does not implement it properly. Many high budget (and low) are increasingly giving widescreen/monitor support, but the notion of colour profiles has yet to be popularized. Simply put, the developers do not see it as a big concern. But I am betting that many gamers with calibrated colours cannot stand their full screen games being reset to default colours like I do! Many triple-A titles like Dawn of War 2, ArmA, Dragon Age, etc currently do NOT support preserving colour profiles.<br><br>

This problem can be universally fixed for all software if the problem was addressed on the driver/video level. Unfortunately, Nvidia has been shrugging the problem off as if it is not a big deal:

<div class="quote-container"><span>Quote:</span>

<div class="quote-block">Originally Posted by <strong>Nvidia</strong> <br>

Thank you for the update and I apologize for the confusion.<br><br>

After the doing further research, I found that NVIDIA does not control or have any function to control the color settings while playing games in full screen mode. Since, these features are application specific it is controlled via the applications. Therefore, please use the games setup if applicable.</div>

</div>

<br>

Basically, whoever has custom calibrated colors for their monitors, lose the colors when a fullscreen game is launched; colors are reverted back to their default mode, making the game look rather disgusting. In the past, this was also a problem under desktop, but that has been fixed.<br><br>

Custom calibrated color profiles are made with hardware devices such as color calibrators, giving the monitor accurate color. Then, this profile is loaded under the OS. But games launched in fullscreen <i>overrides</i> the profile.<br><br>

Nvidia has been ignoring/sidelining this problem for far too long. Many of us use custom colors, and to not support custom colors in fullscreen games is ridiculous! Below, I will be posting a few workarounds for this big problem.<br><br><span style="text-decoration:underline;"><b>1) Direct Hardware-level force (ATI ONLY)</b></span> If you are an ATI user, there is a very easy fix for this. Use PowerStrip, load up the color profile, and enable the setting "Write directly to palette DAC". This setting under PowerStrip allows it to bypass the driver/OS altogether and write directly to the hardware. An effective method to force calibrated colors in fullscreen games. <b>However, Nvidia has locked out this ability</b>. EnTech, the developer behind PowerStrip explains:

<div class="quote-container"><span>Quote:</span>

<div class="quote-block">Write directly to palette DAC" is an EnTech expression that predates NVidia, and essentially refers to going around the OS and the display driver, and writing directly to the hardware. <b>NVidia does not approve of this method, and starting with the Geforce8 no longer shares hardware register data with EnTech.</b></div>

</div>

<br><span style="text-decoration:underline;"><b>2) Borderless windowed mode.</b></span> This mode has a few names; "borderless windowed mode," "frameless windowed mode" or "fullscreen windowed mode". It runs the game in fullscreen native resolution mode, without the OS borders, giving the game a "full screen" look. And since the game is running windowed, the color profiles are kept. There are two ways to do this, one is to enable it in games that natively support it. The problem with this is that an extremely few number of games support this feature. Second, with third party applications such as <a class="bbcode_url" href="http://grismar.net/shiftwindow/" target="_blank">Shiftwindow</a> and <a class="bbcode_url" href="http://gwr.orekaria.com/" target="_blank">Gamers Window Relocator</a>. It works well, however, not all games support windowed mode, it is laborious, must be manually set for each game, and just flat out does not work (even when its working). For example, the game will be removed of its borders, but the taskbar will remain on top of the game.<br><br><b><span style="text-decoration:underline;">3) <a class="bbcode_url" href="http://colorclutch.sourceforge.net/" target="_blank">Color Clutch</a></span></b> (the author of this tool on this forum somewhere)<br>

CC is a tool to force calibrated colours in DX games through dll injections. This works for MOST games. However, this is a rather intrusive way, injecting dlls may get you kicked/banned from Steam, etc (no word if this affects VAC). It is also a bit laborious, each game needs to be set up manually, and you must launch the game through a *.bat file. This can cause problems with content-distrubtion services like Steam, where you have to launch the game through the Steam application.<br><br>

the author describes the problem in an email <a class="bbcode_url" href="http://widescreengamingforum.com/node/14191#comment-221733" target="_blank">HERE</a> and <a class="bbcode_url" href="http://widescreengamingforum.com/node/14191?page=2#comment-221748" target="_blank">HERE</a>

<div class="quote-container"><span>Quote:</span>

<div class="quote-block">Anyway, the problem is, at least on the DirectX front, not a problem of what a game doesn't do, but rather a problem of what a game does do. Full-screen Direct3D applications do not inherently screw up color calibration. The problem occurs when a specific function is called--in Direct3D9 and earlier, this is SetGammeRamp(), and in later versions it was moved to the DXGI and renamed SetGammaControl() (simply referred to as SGR()/SGC() from here on). These are the functions that cause loss of color calibration. While I can't say with 100% accuracy whether the problem itself lies in Microsoft's design of the API or the implementation by the various graphics card vendors (nVIDIA/ATi/Intel), with the problem occurring on several vendors cards I would assume it is behaving exactly how Microsoft designed it.<br><br>

It's even more ambiguous when you look at the documentation. There is actually a flag that can be passed to the function, D3DSGR_CALIBRATE, which "If a gamma calibrator is installed, the ramp will be modified before being sent to the device to account for the system and monitor response curves." However, upon testing, I found that this either doesn't work as expected (at least on my 5850), or works exactly as expected but the "gamma calibrator" doesn't include installed monitor profiles and therefore is seemingly useless anyway. If it doesn't include the "curves" of monitor profiles, what does it refer to then?<br><br>

The reasons for even calling such a function to begin with are dubious. Originally, it seems this was used by developers to "fade out" or "fade in" a scene, or provide some basic color filtering, which was not very easy to do efficiently back in the day. This doesn't seem to be in practice in any game made in the last ~5 years that I've played, judging from my experience playing them both with and without Color Clutch in use (explained later).<br><br>

More recently, games seem to use it in a different fashion--to provide users who have no such monitor calibration some in-game adjustment. Ultimately, developers want the game to look the same way to the end user that it looked to them, and setting gamma ramps is a quick, though incomplete and incorrect fix for this. A better way would allow users to set brightness, contrast, and gamma using a shader, which is what I believe some of the newer games are doing. For instance, I recently purchased BF:BC2, and it has brightness and contrast (no gamma) adjustments which thankfully never call SGC().<br><br>

The easy fix for those who want full screen gaming while holding on to their monitor calibration is to simply not call the function. Unfortunately, most games call SGR()/SGC() no matter what, even if there have been no adjustments to the gamma in the settings. That was why I wrote Color Clutch. The theory behind it is simple--prevent the games from calling these functions, and your color calibration will survive. There aren't a whole lot of good ways to do this, so I took what I thought was the best way; injecting a DLL into the process, and then, whenever it tries to call SGR()/SGC(), instead it calls my "bogus" function with the same parameters. The only difference between the real function and mine is that my function doesn't actually do anything.<br><br>

As for current plans regarding Color Clutch, I'm working on support for some older versions of DirextX (specifically 6, which I think is the first version to include a SGR() function, and 7). This is made difficult by the complete lack of documentation pertaining to these old APIs, but I should eventually be able to get something out that works. OpenGL, though, has no apparent analog to SGR()/SGC(), so I don't believe I can do anything there, and I'm not entirely sure how, why, or even if some users are losing calibration on OGL games.<br><br>

Sorry about the long post, but I thought it was better to be thorough than lacking.</div>

</div>

<br><br><span style="text-decoration:underline;"><b>4) <a class="bbcode_url" href="http://www.softpedia.com/get/Tweak/Video-Tweak/Monitor-Calibration-Wizard.shtml" target="_blank">Monitor Calibration Wizard</a></b></span><br>

This tool works by constantly checking and reverting back the profile if it reverts back to one other then the assigned profile. The biggest problem is that this is a "soft" solution, and games/drivers that are set to override the color profile <i>will</i> override then. Therefore, MCW works for a very small amount of games.<br><br>

I found the author describing the problem in an <a class="bbcode_url" href="http://widescreengamingforum.com/node/14191?page=3#comment-221756" target="_blank">email</a>:

<div class="quote-container"><span>Quote:</span>

<div class="quote-block">MCW uses some Windows API (application programming interface) to adjust the colors, basically a couple functions to set the gamma ramp lookup table. It works well within Windows, and a number of games (specifically OpenGL based games). However, support within Direct3D games become dependent on the video drivers to "care" about this lookup table and to carry the settings over into what is rendered through Direct3D. Support in that regard has typically been kept, but it does get broken from time to time by the video card driver developers.<br><br>

The other issue is that the video card drivers themselves have their own color correction support built in, and often that correction takes precedence over the Windows gamma ramp tables. I have an option in MCW to "apply fix to override driver level color correction", which attempts to workaround some video card driver implementations. It does this by setting the gamma ramp table twice, with two different profiles. Oddly, that has worked decent as a workaround for the video card driver implementations, but may do nothing to help in your case.<br><br>

In the long run, new methods other than the gamma ramp table may be needed to be used to support games. I haven't dug into it too much, but it may be possible to modify the Direct3D drawing surface being used by a game (unless Windows security prevents it). Otherwise, I would be looking at utilizing the APIs available in each video card driver. I know ATI does a good job of providing a programming interface to their drivers, so I wouldn't expect it to be difficult to get things working well on an ATI based video card. I haven't looked at nVidia yet, but I would imagine they have something similar available. Of course, going that route also means you have to build against a number of video card manufactures' programming interfaces (APIs), and support multiple versions and changes to those APIs, which gets to be a pain. This is why I think it might be better to bring pressure on the video card developers to keep proper support for the Windows gamma ramp API, so existing software doesn't break.<br><br>

Back when Vista came out, Microsoft broke support for the gamma ramp API, requiring application to ask for permission before it could be used. This basically broken all the calibration software out there that wasn't written for Vista, and virtually all the OpenGL based games (as far as color correction built into the games). Later, Microsoft backed down on the security so everything worked as it did before. Some of the video card manufactures also built in workarounds into the video card drivers because of how slow Microsoft was in dealing with it.<br><br>

There's no universal fix, but there are generally workarounds. I am a gamer myself, so I would certainly attempt to get things working within games if I can.</div>

</div>

<br><br><br><br><span style="text-decoration:underline;"><b>5) <a class="bbcode_url" href="http://goebish.free.fr/cpk/" target="_blank">CPKeeper (Color Profile Keeper)</a></b></span><br><br>

This tool allows to apply and lock ICC profile files to keep monitors calibration even while running or quitting 3D fullscreen applications such as video games.<br><br>

Personally, I had limited success with this program. However...<br><br><br><span style="text-decoration:underline;"><b>6) <a class="bbcode_url" href="http://forums.steampowered.com/forums/showthread.php?t=2675769" target="_blank">Windowed Borderless Gaming</a></b></span><br><br>

This is my current go-to app. I use this in addition to MCW. Basically, you need to run your games in windowed mode, hit F3, and the game gets rid of borders. A really nice thing about this particular app is that you can manually tweak the window location (x and y), so you can adjust to fit your screen 100%. However, it's not compatible with ALL the games I've tried, sometimes the Windows bar would not go away. Success rate is about 99% for me. I recommend using this.<br><br><br>

As you can see, all of these workarounds are not perfect. The only absolutely "perfect" solution only exists on ATI cards, where users can directly access the hardware to force color profiles. This is not possible on Nvidia. <span style="font-size:16px;"><b>Please feel free to add on your own workaround/solutions!</b></span> I will update the original post.<br><br>

I do not see why Nvidia is not fixing this properly. When and how can we get Nvidia to properly implement fullscreen custom color support? <i>Please?</i>