|
|
|
Member 226 posts
Registered: Jun 2006
I just ordered a 120hz 22" monitor and I already have a 60hz 22" but I'm trying to get a config ready for the new monitor. The new monitor should be here by Feb 23. I'm curious to see what everyone's quake looks and feels like at this aspect ratio.
Here's mine at 1680x1050 (16:10): http://www.prodigysc.com/ezquake005.png
And the config: http://www.prodigysc.com/config.cfg
I'll post my textures folder (without credits :S) if that's okay: http://www.prodigysc.com/foogssetup.zip
Most of the graphics you can get off of gfx.quakeworld.nu (Except for the HUD numbers I made those myself) and I just modified the shaft / cell packs color to pink so I wouldn't get it confused with my white enemy skin.
Please let me know what you think of my config and if I have something wrong e.g. geometry messed up or small tweaks I should make.
Include what aspect ratio and resolution the config is for. Post up your widescreen configs!
Edit to my config: I had an issue with movement with that config. Sorry to anyone that already downloaded it and used it. I fixed it though now. So try downloading it again and im sure you'll love the movement.
Member 113 posts
Registered: Mar 2006
I don't found next commands in your config: vid_wideaspect 1 cl_maxfps x/120 (i use 960) cl_physfps 77 and vid_displayfrequency "75" ? lol? make it 120 my settings: 1680x1050 (viewsonic 2268) screenshotconfigmost settings from Def's Quakeworld Setup
Member 1435 posts
Registered: Jan 2006
vid_widescreen 1 is only good when you are about to switch from CRT (4:3) to TFT (16:10) and don't want to change all the stuff manually. Also it's good when you need to toggle between the two displays often. It does the recalculations for you.
If you already have everything set for TFT (and fenris has, vid_mode 13 is 16:10, also his vid_conwidth/vid_conheight is 16:10), he does not need vid_widescreen 1. Actually he should not use it as it would apply 4:3->16:10 transformation to something that already is 16:10, so it would result in some weird proportions.
Member 113 posts
Registered: Mar 2006
hehe, i used both vid_mode 13/-conwidth 768 -conheight 480 and vid_wideaspect 1 and feeled a bit weird, thx for mention it
Member 226 posts
Registered: Jun 2006
I don't found next commands in your config: vid_wideaspect 1 cl_maxfps x/120 (i use 960) cl_physfps 77 and vid_displayfrequency "75" ? lol? make it 120 my settings: 1680x1050 (viewsonic 2268) screenshotconfigmost settings from Def's Quakeworld SetupYour config says you use this as your resolution in game: vid_customheight "1024" vid_customwidth "1600" Yeah once I get the 120hz LCD I'll make my vid_displayfrequency 120, but for now on this LG monitor it maxes at 60hz even though the config says 75. :S How come you don't use your monitors native resolution? Is there any reason to cap your cl_maxfps to 960 anymore when using independent physics? Your config is pretty baller though.
Member 462 posts
Registered: Jan 2006
Here is mine: http://www.cs.tut.fi/~blaze/config.cfg
Member 113 posts
Registered: Mar 2006
I don't found next commands in your config: vid_wideaspect 1 cl_maxfps x/120 (i use 960) cl_physfps 77 and vid_displayfrequency "75" ? lol? make it 120 my settings: 1680x1050 (viewsonic 2268) screenshotconfigmost settings from Def's Quakeworld SetupYour config says you use this as your resolution in game: vid_customheight "1024" vid_customwidth "1600" Yeah once I get the 120hz LCD I'll make my vid_displayfrequency 120, but for now on this LG monitor it maxes at 60hz even though the config says 75. :S How come you don't use your monitors native resolution? No, i using 1680x1050 in reality, native resolution rocks in games I set it via command line: ezquake-gl.exe -width 1680 -height 1050 -conwidth 768 -conheight 480 -bpp 32 -mem 64 -noforcemaccel -noforcemparms +set vid_displayfrequency 120 +set s_khz 44 -ruleset smackdown -norjscripts -noscripts -particles 4096 +set cl_independentPhysics 1 +cfg_load spblan2 Is there any reason to cap your cl_maxfps to 960 anymore when using independent physics? Your config is pretty baller though. I prefer stable fps count. From The Theory of Smooth QW : /cl_maxfps 0 isn't generally a good idea since the framerate will vary a lot depending on the situation, making updates really irregular. This, of course, has no real impact on anything as long as your fps range is 1000-3000fps, but if it goes from 120 to 400 then it matters a lot. Although i have 1300-2000 fps, i still feel better with stable count.
Member 226 posts
Registered: Jun 2006
I prefer stable fps count. From The Theory of Smooth QW : /cl_maxfps 0 isn't generally a good idea since the framerate will vary a lot depending on the situation, making updates really irregular. This, of course, has no real impact on anything as long as your fps range is 1000-3000fps, but if it goes from 120 to 400 then it matters a lot. Although i have 1300-2000 fps, i still feel better with stable count. Ahh I see. I'm also using cl_earlypackets 1. Also From The Theory of Smooth QWThe cl_earlypackets feature obsoletes parts of this guide, so in case you are using the cl_earlypackets you should set cl_physfps 77 and cl_maxfps to whatever value is good for you, preferrably being at least your monitor refreshrate or more. There are no multiplication rules of any kind anymore (neither cl_physfps nor monitor refreshrate matters) so you are free to use 200fps, 300fps, 400fps or whatever if you wish. I'm gonna change my cl_physfps to 77 now. I suppose I'm gonna cap my fps to something stable too. Thanks! Here is mine: http://www.cs.tut.fi/~blaze/config.cfg I'm thinking now I should also up my fov. 133 feels sharper dunno if i'll go that high but i'll definitely go over 120 for sure. Gonna test it out. Thanks for everyone posting their configs so far it's helped a lot. Keep going!
Member 462 posts
Registered: Jan 2006
133 equals 125 on 4:3. It is quite big, but offers good visibility to sides, so you don't miss items or opponents that easily.
Member 226 posts
Registered: Jun 2006
Got the 120hz monitor today and it is dope! I updated my config and it works perfectly on that monitor. Really Really Really Really Really Really Really Really Smooth. Butter Bacon Slick Buns. I did have some troubles getting it to go into 120hz on linux. I spent 3 hours playing with it in 60hz and thought it was a load of shit and thought that i got ripped off. Just added one line to my xorg.conf and it worked in 120hz and it was amazing. Here's what I added in case someone out there is ripping their hair out trying to get this to work. Under the Device section for that monitor. (I'm running both my old monitor and the new one [both lcd one at 60hz and the other at 120hz]) Option "ModeValidation" "AllowNon60HzDFPModes" eg: Section "Device" # 60hz monitor Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce GTX 275" BusID "PCI:1:0:0" Screen 0 EndSection
Section "Device" # 120hz monitor Identifier "Device1" Driver "nvidia" VendorName "NVIDIA Corporation" BoardName "GeForce GTX 275" Option "ModeValidation" "AllowNon60HzDFPModes" BusID "PCI:1:0:0" Screen 1 EndSection
|
|
|
|