Wrong,Broken,Flaw'd.......

[Mindf!3ldzX]

Call it wtf ever you will.... This post is here to outline certain never ending types of issue that should have been resolved looooong ago.


Please, if you add to this post make sure you ask yourself atleast these questions....


1]Does 'ALL or a Large Amount' Quake1 engines/clients suffer the same issues??.


1.When you adjust the Brightness/Gamma/Contrast of Quake (which is forced into using Display 1, the main desktop) then mother effing Display 2 is ALSO tweaked / and / twatted and will eventually look like shit, when compared to "How well you tweaked your settings to look good in Quake".


For the Record, I could resolve all of this shit probably with in Catalsyt Control Panel / Vision Engine Center (through excessive tweaking / retweaking / tweaking / retweaking....


All things considered, it's the small shit that I notice now days...... Like this annoying ass bug that has plagued Quake for as long as I can remember....... TOO FN LONG, at minimum IMO.

Engines that do not suffer this issue Darkplaces, that all I know of so far and thats probably where that list ends, all things considered when DirectQ/Qrack/ProQuake all exhibit that same 'WTF get the fuck off my monitor 2 CONTROLS YOU DICK' when im adjusting Quake's Brightness/Gamam/Contrast. I am owing more credit to Darkplaces now than previously allotted, due to this allbeit mega simple function, but wow it's very nice when I can tweak my display of Quake and shit outside Quake DOESNT march to the same beat, it really makes for Quake looks really nice and then whatever is on other Monitor looks JUST as sexy....
What else people???

[R00k]

It's not just Quake engines, other games suffer from this effect. I blame the blanket gamma setting over ALL monitors. Now DP might be either doing something RIGHT, or something custom to fix this.

MORE so, when I use a custom resolution on monitor 1(in-game), it pushes my windows on monitor 2 a side, this happens to me even with BattleField 3!
So ya there are some weak point when using two monitors in windows.

oh and since u are here i guess u too cant connect where everyone else is playin!!

[Spike]

regarding DP, the v_glslgamma cvar says that the gamma control is done purely by software, and will not affect any other program running on your machine.
This setting will reduce your framerate slightly, of course, which is why other engines opt to not use it.

Its a tradeoff between performance and correctness, and performance wins over preserving the user's custom gamma, I suppose.
FTE did attempt to preserve the user's gamma, but it no longer does because lots of people complained about being unable to reset gamma if it crashes. If you want the old behaviour, seta vid_preservegamma 1 before quitting/tabbing away.

tbh, I'm surprised your other monitors are even still active when a game goes 'fullscreen'.

[powerzord]

Yeah if rook would just finish the touchbuns mod we wouldn't have this issue

[MH]

That happens because the gamma setting is global; it belongs to your entire desktop, not individual windows running on it, and you just can't have different gamma for each window.

Yes, even a fullscreen game is still running in a window.

So when you change a global setting you get a global change and it affects everything.

This is nothing to do with Quake engines and everything to do with your display hardware; if your display hardware behaves in a certain way then there's nothing individual engines can do to change that. They can try to sidestep it (like the DP trick which I've recently adopted for DirectQ - it should be in that recent test build I sent you, Mindz) but they can't change it.

[Perochi]

Touch buns mod is in closed beta $9.99 for a beta key. whisper powerzord.

[Mindf!3ldzX]

That happens because the gamma setting is global; it belongs to your entire desktop, not individual windows running on it, and you just can't have different gamma for each window.

Yes, even a fullscreen game is still running in a window.

So when you change a global setting you get a global change and it affects everything.

This is nothing to do with Quake engines and everything to do with your display hardware; if your display hardware behaves in a certain way then there's nothing individual engines can do to change that. They can try to sidestep it (like the DP trick which I've recently adopted for DirectQ - it should be in that recent test build I sent you, Mindz) but they can't change it.

Welllllllllllll shit brah. On a plus note,I (through pure luck and "doing it again") created a mega generic quake folder with only two paks / added DIRECTQ / HEY I SEE BOLT.


So,
probably some cvar I've set is causing the issues. It looks like I'll be entirely having to repopulate a fresh Quake folder,and entirely skip shit like a pre existing directq.cfg and just dropping all my pak files into it. Systematically just keeo adding peices and look for the failure to replicate.


Something to do while 5-0's dont exist.

[MadGypsy]

I'm not sure I understand why it matters what happens with alternate displays while you are playing Quake. I know exactly what you are talking about, but I don't understand why it matters.

Do you honestly play Quake on one monitor while you simultaneously "do work" on the other monitor? That would be obsessive. As soon as you close the engine everything goes back to normal (well, at least in my experience).

You should put Quake on both monitors and play yourself...see if you win.

[Mindf!3ldzX]

People act as if Multitasking Human Beings is a cardinal sin

[golden_boy]

I run a Quake engine for testing things in my game while simultaneously having things like Firefox, Blender, Radiant, several terminals, Gimp and a chat client open. I also use Linux/Gnome with its standard virtual desktops between which I switch.

It does matter, and it is annoying.

While it's perhaps a reasonable assumption that most people will play their games in fullscreen and only have one monitor and do nothing else while playing, it is (like all reasonable assumptions) short-sighted. It will only work in 90% of the cases (typical users), and the other 10% (non-typical users) get fucked.

Reasonable assumptions usually have serious side effects for a minority of people.

[Syluxguy28O3]

so, can this be resolved?

[MH]

For Mindz it matters because some stuff happens on one monitor while Quake is on the other.

There are some basic things that are easy to do to make it less annoying, but you can't fix it permanently because it's not within the realms of software to fix. The only reasonable workaround is a shader-based gamma system, but otherwise basic stuff like capturing and saving the current desktop gamma when the engine starts, restoring that gamma when you Alt-Tab away, adding an exception handler that restores it if the engine crashes - that's the way to go.

[R00k]

[powerzord]

Nice buns

[Syluxguy28O3]

Nice buns

*sigh*