I don't know if it's just me, but on my computer, BZflag only looks right with the brightness setting all the way to the right.
When it's in the middle (which corresponds to a normal gamma ramp), the nighttime sky looks darker, but everything looks too dark and shadowed, and its too hard to see the tanks in the distance.
What's your favorite brightness setting?
-
his blind ambition
- Private First Class
- Posts: 11
- Joined: Sat Jun 21, 2003 8:15 am
- Location: Los Angeles, CA
- Contact:
-
his blind ambition
- Private First Class
- Posts: 11
- Joined: Sat Jun 21, 2003 8:15 am
- Location: Los Angeles, CA
- Contact:
That would be very cool. I have to restart my system in order to completely correct the problem when BZFlag crashes and doesn't reset gamma. I can change my gamma level, but it gets messed again when I load a DirectX or OpenGL app.
Please do let us know!
Please do let us know!
protected object myTank(){
foreach(noob in this.game){return frag(noob);}}
foreach(noob in this.game){return frag(noob);}}
-
Spaceman Spiff
- Registered User
- Posts: 0
- Joined: Fri Oct 28, 2005 11:59 pm
missing option
How about:
"My busted client doesn't have a brightess setting, you insensitive clod!"
/learner wanders off grumbling
But on the other hand.. the brightness is perfect as it is.
"My busted client doesn't have a brightess setting, you insensitive clod!"
/learner wanders off grumbling
But on the other hand.. the brightness is perfect as it is.
Last edited by learner on Tue Jun 24, 2003 8:04 pm, edited 1 time in total.
-
Spaceman Spiff
- Registered User
- Posts: 0
- Joined: Fri Oct 28, 2005 11:59 pm
-
his blind ambition
- Private First Class
- Posts: 11
- Joined: Sat Jun 21, 2003 8:15 am
- Location: Los Angeles, CA
- Contact:
A workaround & fix
This is a cheesy fix because it doesn't actually restore your original gamma values. However, if you're like most people, you probably have a simple 1.0 gamma ramp, and this fix will make things look relatively normal.
The problem is caused by the fact that windows BZ reads the gamma ramp at the beginning (which is typically near 1.0), then sets the gamma to a really high value (cause we're all setting the slider all the way to right). Then when it exits, it sets the gamma back to the stored value.
When it crashes, it leaves the gamma at the absurdly high setting. Then, when it runs again, it reads the "good" gamma settings (which are now wrong), sets the gamma to the same high setting (the game looks fine), and then restores the "saved" gamma settings (which are still high) when exiting.
There are two ways to fix this.
1) No programming required. Run BZFlag, move the brightness slider to the middle (which corresponds to a gamma setting of 1.0) and then do something which forces bzflag to crash (I'm sure one of you enterprising punks can suggest something).
Your desktop gamma should now look okay. The next time you run bzflag, move the brightness slider back to the right.
2. Programming required. Change the line in WinWindow.cxx that says:
setGammaRamps(origGammaRamps);
to this:
setGamma(1.0);
(This is what I did).
These are both easy kludges, but not really proper fixes, because they don't restore the gamma to exactly what it was. Two things that would make more sense in the long term:
1) Save the gamma settings to a file, and delete this file when doing a proper exit. Then when you start up, if this file still exists, you know there was an improper crash, and you read the gamma settings from the file, instead of from the videocard.
This will fix the gamma problem properly when you run the app
a second time.
2) Fix the graphics so that they look really good at a gamma setting of 1.0. In other words, things should look the most normal with the slider in the middle. This will help prevent the
"my monitor is all screwed up" problem in the first place.
The problem is caused by the fact that windows BZ reads the gamma ramp at the beginning (which is typically near 1.0), then sets the gamma to a really high value (cause we're all setting the slider all the way to right). Then when it exits, it sets the gamma back to the stored value.
When it crashes, it leaves the gamma at the absurdly high setting. Then, when it runs again, it reads the "good" gamma settings (which are now wrong), sets the gamma to the same high setting (the game looks fine), and then restores the "saved" gamma settings (which are still high) when exiting.
There are two ways to fix this.
1) No programming required. Run BZFlag, move the brightness slider to the middle (which corresponds to a gamma setting of 1.0) and then do something which forces bzflag to crash (I'm sure one of you enterprising punks can suggest something).
Your desktop gamma should now look okay. The next time you run bzflag, move the brightness slider back to the right.
2. Programming required. Change the line in WinWindow.cxx that says:
setGammaRamps(origGammaRamps);
to this:
setGamma(1.0);
(This is what I did).
These are both easy kludges, but not really proper fixes, because they don't restore the gamma to exactly what it was. Two things that would make more sense in the long term:
1) Save the gamma settings to a file, and delete this file when doing a proper exit. Then when you start up, if this file still exists, you know there was an improper crash, and you read the gamma settings from the file, instead of from the videocard.
This will fix the gamma problem properly when you run the app
a second time.
2) Fix the graphics so that they look really good at a gamma setting of 1.0. In other words, things should look the most normal with the slider in the middle. This will help prevent the
"my monitor is all screwed up" problem in the first place.
-
Spaceman Spiff
- Registered User
- Posts: 0
- Joined: Fri Oct 28, 2005 11:59 pm
-
Spaceman Spiff
- Registered User
- Posts: 0
- Joined: Fri Oct 28, 2005 11:59 pm
-
megachirops
- Private First Class
- Posts: 122
- Joined: Wed Jan 15, 2003 3:32 am
- Location: El Dorado, CA.
- Contact:
Re: A workaround & fix
Does F12 still work? (I remember F12 used to crash 1.7e6)his blind ambition wrote: do something which forces bzflag to crash (I'm sure one of you enterprising punks can suggest something).
"When in doubt, quit"
-
Spaceman Spiff
- Registered User
- Posts: 0
- Joined: Fri Oct 28, 2005 11:59 pm
-
CobraA1
- Dev Monkey
- Posts: 124
- Joined: Fri Dec 06, 2002 7:19 pm
- Location: Above the Arctic Circle, below Canada: Minnesota
- Contact:
Contrast -> all the way up
Brightness -> all the way up, then turn down until black is black.
Software gamma -> leave alone
That's how I set my monitor.
Brightness -> all the way up, then turn down until black is black.
Software gamma -> leave alone
That's how I set my monitor.
-CobraA1
"If a man does not keep pace with his companions, perhaps it is because he hears a different drummer. Let him step to the music he hears, however measured or far away" --Henry David Thoreau
My avatar symbol © 2002 Jeremiah Moss. All rights reserved.
"If a man does not keep pace with his companions, perhaps it is because he hears a different drummer. Let him step to the music he hears, however measured or far away" --Henry David Thoreau
My avatar symbol © 2002 Jeremiah Moss. All rights reserved.
For ati cards just go into the display properties and click advanced and then go into the color tab. That will fix the gama after it has been messed up.DTRemenak wrote:If you're using an nVidia driver (not m$ provided) on windows, just going to display properties, clicking advanced, then on the tab that has your card's name on it (e.g. "GeForce 3 Ti 200") will restore your gamma settings to whatever you had them set to.