[quote]I'm for it - problem is, when 90% of gamers use 6-bit Twisted Nematic panels (which give poor colours to begin with) and don't even realise the problem as long as the game "works"... I worry that you're fighting a losing battle.
90%? You're being humble. I'd bet that its 90% on here alone. 95%+ in the real world. :?
Well perhaps, but there are plenty people with hardware calibrators out there.
Let's see, custom colours are mostly used by people who own a hardware calibrator, right?
People who most likely use hardware calibrators:
Photographers
Photoshoppers
Web designers
Video developers
etc...
And at least SOME of them must be PC gamers of some sort, I'm not sure how to approximate how many of these professions requiring a hardware calibrator are gamers, but it's probably safe to say at least half of them (?).
Anyway, it is really quite annoying not being able to retain calibrated colours in fullscreen games.
And I know that the majority won't care (I recently asked in a forum of a game that's being currently developed to add this support, but a developer replied back saying "what?".... :doh :doh ) but I don't think it's a big nor difficult change for developers to start using this, OR at least give the games "borderless window" options, as a viable workaround.
After some time searching, I found Ian, author of
ColorClutch. Basically, he's one of the few people who got sick of fullscreen games losing colour profiles and decided to do something about it. His program works for many games, but it doesn't in many other games. Not to mention the process is somewhat intrusive, it works by injecting a dll into the running process. I sent him an email regarding the situation, and here's the reply I got back:
Hey,
Ah, it's good to hear someone is making good use of Color Clutch (at least in offline games). It's unfortunate that nVidia restricts you in such a manner on their newer cards. The Powerstrip developer is surely more knowledgeable than I am in this area, and if he says it's very unlikely there will be any change from nVidia, he's probably right, unfortunately. That said, the GTX 480 is still a very new card, so only time will tell. It sounds like nVidia isn't interested in allowing this sort of hack, and even if they wanted to, they have quite a handful of more important issues to deal with now--low yields on the GTX 4xx cards, and the overheating issues in their laptop graphics cards finally coming to light (thanks to Starcraft 2).
As for being flagged, VAC banned, or anything else in multiplayer, I make no promises, but a place to start would be on the forums--well, for steam anyway. I'm also not sure if there's even a way to get it to inject into a steam game, as I need to start the process from the injector currently, and I believe with any software from steam, you have to let steam start the game. In the future I will hopefully get around to adding chain loading capability, which should let you use it even with other launchers. For the mean time, I've asked on the steam forums about the possibility of VAC bans related to CC.
As for an updated version of CC that's less invasive, it's unlikely, for a couple reasons. First off, I want to stay in user space. Kernel space would allow for additional methods, but it's arguably more invasive, and can lead to system instability if I'm not perfect--and as careful as I am, bugs are unavoidable. The saving grace is your system doesn't BSoD if you mess something up in user land, so CC will stay there. That being, there's really only one other method I can think of off the top of my head that would work, and that is a Direct3D wrapper. I want to avoid this for several reasons, but primarily the versioning issues with wrappers--when the D3D DLL is updated, usually the wrapper has to be as well, and this can cause all sorts of headaches for the end user.
As far as "deleting" the default sRGB profile, that isn't possible, AFAIK. The way profiles appear to work in Windows is by giving a response curve *relative* to the standard sRGB curves--thus, if you were to remove the original sRGB curve, your profile would also be rendered useless. This may be incorrect, but even so, I don't think there's any way to safely prevent the built in default at whatever level they're implemented (software or hardware). The main reason developers in general don't care about calibration is that so few users bother to calibrate their monitors, and even if they did, it's unlikely they'd notice much difference when the color reverts, as monitors typically have fairly close color rendition. I was fortunate enough to get a very bad one (or maybe all the monitors of this model are bad?), and it's very obvious when the color is off, especially on midtones and highlights. Maybe the calibration tool provided with Windows 7 will help, but I doubt most will bother with it.
Thanks for the feedback.
I also emailed Ian a copy of this thread. Maybe he'll sign up here or something.
CALIBRATED COLOURS OF THE WORLD, UNITE!