I'm looking for high fps one. I set everything to lowest in menu and I wonder if I can get anymore by adjusting minor cvars like in quake. It's 100+ unstable now
Lowest isn't always the fastest. Ye, it's strange but, lowest in Warsow is set up for old 3dcards which don't take advantage of fragment shaders nor VBOs. If you have a modern card you'll get a faster configuration by tweaking medium profile than by using low profile or turning everything off. If you set gl_ext_GLSL to 0 you lose huge hardware speed ups.
I don't get any speedup by toggling gl_ext_GLSL. Any reference? I don't feel like testing all cvars.
I have intel GMA 4500MHD card (supports opengl 2.1 but it's very slow).
Here is mine with all the needed cvars organized in subcathegories plus my crosshair-pack.
Very stripped down and focused on visibility. Can do 300fps on my Athlon 64 X2 6400+, GeForce 9600GT and 2GB DDR2-800 RAM with 1680x1050@120Hz.
You need to change stuff like name, resolution, sensitivity and weapon-settings/binds. Also if your game doesn't want to start after you have put in my autoexec, just change s_module form 2 to 1 that should make it work again.
Warsow doesn't have a fps-cap afaik. FPS don't affect the physics in Warsow, so theoretically you can have 700 fps if your PC is good enough. But almost all players cap them at 125 or 250 fps because you don't need more.
Don't get why you are using r_drawflat and picmip at the same time but ok. If I were you I would reconcider your hud-choice a bit. The warlord hud is cool but the defaut and clownfart ones are way better for serious play.
Well I've just finished the config hence that lil mistake (corrected), and I was using a custom hud up until 1.0, (qwarsow) but it fails to display chat messages now, so fuck it.
You configure in the menu the models, skins and colors you want for team alpha and beta. If you check the box "force my team always to alpha" (somthing similar) then your oponents will be always displayed as whatever you have configured to beta.
EDIT: The map colors will also change to whatever you have configured for the team colors (in team modes like ctf, ofc, no point in bomb or ca).
fps drops from 125 to 20 when there is some action even in 1v1. Haven't seen such unstable fps in any game. fps heavily affects mouse sensitivity. Under linux I get this shit: http://www.esreality.com/post/2280030/mouse-i...der-linux/
I got few segfaults too.
Meanwhile in ql: stable 125 fps on maps like tox, playable 4v4 tdm with fps 100+ and drops don't affect sens. q3 engine looks the same on on low settings and better on high.
I still got my old config from Bobel somewhere, unfortunately it's for Warsow 0.4 so I have no idea what will happen if you try and implement it in 1.0. Just to put it in perspective it reassembles this config http://i.imgur.com/Tk2u6.jpg
do not try to use your old config from 0.4. Engine has been changed a lot from those times.
Btw, in Warsow 1.0 it is easy to make a look like in your QL screenshot:
r_drawflat "1"
r_wallcolor "100 100 100"
r_floorcolor "100 100 100"
r_lighting_greyscale "1" (makes all lights grey)
r_lighting_vertex "0" (needs for r_drawflat's working)
The lg-gfx isn't pure so ye you can make your own as you want. There is a pretty decent one from adem I think (?) that you can download somewhere in the official forums.
cg_lgbeam_old "1" turns the beam-gfx back to the old one, which is basically only a straight lane without the two small lanes like in the current one and is colored with your model/team color.
The crosshairs are plain tga-images made by me, so basically any tga-image with transparent background will work as a crosshair.
HUDs on the other hand are scripts written in a special syntax that is unique to Warsow (I've written QL huds myself and the syntax is completely different).
However you can take the images from your favourite QW-HUD (as long as they are tga-ones) and implement them into a warsow HUD without problems you just will have to make the folder structure right and write the HUD yourself (or modify an existing one).
I could if I were at home right now. But unfortunately I'm on vacation at a friends house so I can't do it from here. You could however just install Gimp and do it yourself it's really not much work.
actually, the crosshair is a tiny bit left of the center :l downloading gimp atm, gonna see if i can correct it myself. found the same thing for a few other qw crosshairs also =PP
okay, some maccgyvering and 30 min later its centered \o/
qw huds won't work
warsows hud language is different to ezQuake's hud language. ezQuake uses hud_* commands, warsow uses a scripting language for the huds.
I don't know, There used to be some, but I don't know if they are still there (and I guess they will have to get updated to 1.0 if they are). You can use the online one at the website, tho.
Edit:
I added the arrow to show me which side of the scoreboard is mine :). To remove it, go into ...\Warsow 1.0\basewsw\huds\inc\clownhud2, and overwrite the old file with this http://www.upload.ee/files/2565224/scores.hud.html
quick start: Go to <install directory>/basewsw/data0_10.pk3 and extract the huds directory from the pk3 to %APPDATA%/Warsow1.0/basewsw
So now you have all the installed huds in your home directory and can edit them. Do never edit them inside the original pk3.
Locate clownhud.hud and open it with a text editor. You'll see a list of included hud script files. Easiest way now would be to locate a different hud with the weaponlist the way you want it, and include that hud's weaponlist file in clownhud (yes, you can combine files from different huds as you please).
Or you can script the weaponlist the way you want. Here's a starting point on hud scripting (wiki is VERY slow, be patient):
I'm afraid the only explained list is in the wiki and it's very outdated.
You can get a full list by typing cvarlist in the console, but without explanations.
Also note that cg cvars won't be listed unless cgame is loaded, so you have to be in a match to get it all. Same goes to g cvars (you have to be hosting a match) but I don't think you are looking for those anyway.
try the #warsow channel too and ask around and the warsow forums. i know clownfart had a nice config and hud that was very user friendly for people, just dump your own binds in.
Question about the LG gfx. Is the thin, solid line in the middle something that is always there? http://i.imgur.com/NcaKS.jpg
I've tried a couple variations of it, but I always get that line. What I used in the pic above is this. http://i.imgur.com/ZC64K.jpg
Is there truelightning equivalent in wsw? I find it hard to aim lg without it. Also does it do fov/widescreen scaling the same as QL? Or does it do it similar to Q3 (stretch 4:3 to 16:9)
Don't confuse the graphical effect with the hit detection. In Warsow the curved laser beam hit detection matched the graphical effect, it was drawn curved and it touched people following the curve.
At Q3 with truelighting off the gfx was curved, but the hit detection was still straight. It was simply a bad representation of the beam.
With cg_predictlaserbeam 0 you disable the "always straight" drawing of the beam so it's drawn lagged just as it was at Q3, with the difference that our gfx is one line so it doesn't curve, but still points in angle to the lagged position.