win7 screen prob
someone answer this ! >:O this is pissing me off
http://forums.excessiveplus.net/viewtopic.php?t=30687
and then i do customheight/width, then fov resets to 90, i switch it to 130 and its still at 90 but says its at 130. help plz
you also did set r_mode to -1?
http://quake.freakygaming.com/pc/action/quake_3/tutorials/running_quake_3_in_widescreen.html
try to read this http://forums.excessiveplus.net/viewtopic.php?t=20619
For one thing in widescreen LCD your FOV is going to look very different from how it looked on 4:3 aspect CRT Not only is a higher FOV going to look less "stretched" in weapon view, but also in peripheral/outer edges of your visual field when looking right around the crosshairs.
I don't know if you went from a CRT to a widescreen LCD or maybe just went from a smaller LCD to a larger one, but the visual differences are partially aspect ratio-related in my opinion. Er, anyway, you said this problem is fixed but just in case it's not, that's my idea.
Now for the "5cm blank around edges" problem, check the refresh rate on your LCD and make sure to match your settings to it. If you have 19" widescreen for example I think the default setting is 60Hz, in which case you would want to set the following autoexec.cfg var
[code:1]r_displayrefresh "x"[/code:1]
and replace x with either "0" (default, locks to monitor refresh rate through Q3 engine I think?) or "60" (manual lock, goes to your graphics card to lock instead, I think). I might be wrong on how they work, I just know that "0" is default and considered standard. A "set" value to match your refresh rate is considered OPTIMAL.
Also check under advanced display settings in Windows to make sure your monitor's refresh rate is actually 60Hz before setting the r_displayrefresh var to "60". Some LCDs can go higher than this, I'm just giving the common values for a 19" LCD.
If you really want to try to address the situation, check your excessiveplus/autoexec.cfg file and check all the settings there against your hardware settings in Windows first, make sure any name files you execute afterwards don't have any "old" settings in them (just strip all but your main cfg of any settings you don't want changed whenever you /exec them), and of course don't go directly from another mod server to an E+ server.
This last has caused me some weird moments lately I went from a NoGhost instagib server to AIM+ TDM this morning and couldn't see anything r_gamma / r_mapoverbrightbits / r_overbrightbits don't work nearly as nice in most other mods, and r_contrast isn't even an option in E+, so I fux0r3d myself real good.
I hope this helps, and if it doesn't, please be patient and I'm sure we'll get you back to normal with a few more posts.
What about r_ignorehwgamma
What is its value?
If it is 1, set it to 0. If 0, set to 1. Test. Tell results.
This is what it looked on a 4:3 screen u mean.
ok so i fixed the res thing, but the fov problem is still there