So you basically commented your config from 2009 because people can't be arsed to google commands they're too stupid to understand.
Nice.

The config(s) are really well documentated, I don't think I ever have seen such extencive documentation on QL-CVARS on the internet. This makes the configs really usefull for QL-newbs.

On the other hand he did not use all the cvars that are in QL this makes the configs fail to reach their goal. Perhaps he will add the other cvars aswell when he gets time to do it.

oh yeah right sorry, it requires 2 things : having a brain and being able to use google.
I'm not bashing him, I just don't get the point, would he release an updated version of his 2009 cfg you'd have the same thing.

Your second sentence doesn't make any sense.

it not about some cvars, it's about a smart base config for competitive standard cvars...

those are commands everyone who plays on a certain level adjusts and might come in handy for those who are still a bit too afraid/overwhelmed of the whole possibilities QL offers

What T1E said is right.. It's more about the competitive cvars that people should be basing their configs around, without any personal shit in it. That's why I've written so much in them, so that people getting them can actually understand why people might want to use a certain cvar, or what it does.

If I were to just upload my cfg, it'd be filled with all my settings but it would also be stuffed full of vstrs and aliases and mouse settings and other things which are personal to me or just plain useless things for other people.

Thanks for the feedback. I'd like to know what other cvars people might want to tweak which aren't pure preference though?

One of the things with this is that I want people to be able to throw either config in their game and it won't ruin the settings they already have and are comfortable (mouse settings, etc), but will instead just give them the advantage of tweaking their config.

I'm still open to suggestions on things to include, but the essentials is meant to be basic, and the 'pro' one.. I know it's not a pro config, but it's a base.

What is your problem? He is taking away one of the obstacles new players have in the game.

gtfo tard

yay bashed by tards.

Yes. Everyone is a tard except for you. ^o)

I don't know, I understand why he does this but I'd rather either use someone's clean config as a base ( which is why I was talking about emsixteen's 09 stuff, which I used to use ) and add stuff found here and there than just exec something with a few competitive settings, writeconfig autoexec and get the worst mess possible in then end, which the audience he aims his stuff at will NEVER want to look at if they have a problem.

i could barely understand anything you said there :S

A: actually go through a list of cvars and pick what you want -> make your own clean cfg

B: exec something then writeconfig.

The number of people doing B >>>>>>>>> A. Have fun helping them debug their configs.

there's no need for autoexec
there's no need for writeconfig

yeah right and when their serverside shit decides to troll you you're fucked.

i use writeconfig for QL :P

i can solve my own problems, and a lot of people with unclean configs have also gotten help from me. though, a clean config is always easier.

all that really matters to me is what the person who's using the config wants. if they want it clean and tidy, then they can do that. if they like writeconfig'ing a lot, thats also fine. if someone needs help from me, i help.


i dont really get why you dont like emsixteen's work (or whatever you said), because this is pretty much exactly what he's doing: picking out all the cvars that most people would modify, and adding pretty thorough explanations for all of them.

shut up tinkerbell

I just skimmed through the configs and I was impressed.

Looks like a lot of work. Reminds me of my wolfcam config, but yours are more simple, with a lot more info. Mine was every cvar in the game, with about 1-2 sentences describing them.

Good work.

there's one error in the explanations. r_gamma is not linked to the post process and color correction commands.

Gamma is affected by both. Have a read of this, from the wolfcam readme:

Matching colors and lighting with quakelive:

In order to match colors and lighting post processing isn't needed, with the exception of bloom.

Quakelive's r_enablePostProcessing and r_enableColorCorrection sort of correspond to the old q3 cvar r_ignorehwgamma.

There's alot of confusion about what's involved in quakelive's post processing since there isn't much documentation about what the cvars do.

Here's my best take/quess on it:

In quake3 if you wan't to use r_gamma and r_overbrightbits you need to enable hardware gamma (r_ignorehwgamma 0). The problem is that setting gamma like that changes the color/brightness of your entire desktop not just the quake3 application. In quake3 it isn't a big problem since you usually play fullscreen and don't really care about messed up colors in the desktop underneath. Quakelive was designed to be run in a browser so they wanted to avoid changing gamma for the whole screen and wanted to restrict it to just the quakelive window. The solution was r_enablePostProcessing, which at the price of a little performance drop (an extra rendering step), enabled gamma (r_gamma + r_overbrightbits) just for the quakelive window. At that point in quakelive's history r_enablePostProcessing 1 corresponded to r_ignorehwgamma 0 in quake3 (allow the use of r_gamma and r_overbrightbits).

Bloom was later added and it created a problem since r_enablePostProcessing didn't just deal with gamma anymore (it controlled both bloom and gamma). So a later quakelive patch added r_enableColorCorrection which is basically gamma again. This allowed you to keep r_enablePostProcessing 1 if you wanted bloom and r_enableColorCorrection 0 to disable disable gamma. r_enablePostProcessing became a generic cvar enabling different types of post processing (gamma, bloom, anything else they might want to add, etc.). r_enableColorCorrection 1 became the new r_ignorehwgamma 0.

So basically quakelive and quake3 have the same colors and lighting which are controlled by the usual r_* cvars (r_mapOverBrightBits, r_intensity, etc..). The problem and confusion is that two of those: r_gamma and r_overbrightbits are special and have to be "unlocked" in order to have their settings apply.

In quake3/ioquake3/wolfcam you have to have "r_ignorehwgamma 0" in order to use r_gamma and r_overbrightbits.

In quakelive you need "r_enablePostProcessing 1 and r_enableColorCorrection 1" in order to use r_gamma and r_overbrightbits.

Oh, and to add to the confusion, quakelive still has the r_ignorehwgamma cvar :( It doesn't seem to do anything though.

well i tested changing r_gamma with postprocess and colorcorrection both in 0 and it worked

Hmm, alright, that text has led me astray then. I know that it's right for me though, if I disable either my r_gamma doesn't work (nor does bloom).

Anybody have any idea why so I can make a proper description?

PP doesnt change the behavior of r_gamma in my experience. could be hardware/drivers?

In quakelive you need "r_enablePostProcessing 1 and r_enableColorCorrection 1" in order to use r_gamma and r_overbrightbits.

Oh, and to add to the confusion, quakelive still has the r_ignorehwgamma cvar :( It doesn't seem to do anything though.

Not from my experience. I have enable PP and enable CC both off and gamma and obb function correctly. Obb 1 gives me almost as bright models as enablePP does.

For ignorehwgamma 1, it makes enemy models barely bright and you also have to vid_restart anytime you change gamma. From what I can tell, if you have it set to one and PP enabled, PP will basically disable ignorehwgamma. I don't know what hwgamma does technically, from the description it's supposed to disregard any gamma settings from the video card driver and pay attention only to game gamma. Which I would think would result in a consistent picture as far as brightness goes across different computers and it might save some hassle mucking about with settings all the time whenever playing on a different computer.

But I'm not entirely sure on that last part. People see so and so have it set to 1 (even when that person uses PP too), so they do it but you ask them what it does and never get an answer.

And I'm not 100%, but I could've sworn Sync mentioned a long time ago, that PP was created for qlive because of the differences in vertexlight (at the time) between qlive and q3. I remember back in closed beta, using vertexlight 1 resulted very dim enemy models even with keel/bright.

Alright, now I'm confused as shit.

// Post processing
// This command controls your ability to use gamma (brightness) and bloom commands.
// Turning it off is probably the single greatest way to get an FPS increase in QL,
// however I think keeping it on is worth it.
seta r_enablepostprocess "1" // 0 = Big FPS increase, but alt-tabbing ruins gamma

With older PC`s alt-tab'ing won't ruin your gamma, everything works great.

Oh right.. I'll remove the alt-tabbing comment then, heh.

I think my config is well organized. I encourage people to use it as a base when making they're own configs (as it contains almost everything configurable).

http://kyto.dez.fi/ql/config/kyto.cfg

I don't think you get the point of this. :P

I do. Just wanted to post my config so maybe you could see yours is missing thousands of cvars. :r

I'm not missing thousands of cvars though, nor many cvars which are actually of any use. The difference is I'm not shitting out every cvar in the game into this thing, the point is to have notable documentation for people.

Shrug.

maybe im a bit off topic but, really nice work on the Q4 hud. the zoom is wonderful |]

Fair enough. Maybe I didn't get the point then.

seta winkey_disable "0" // 1 = Disables Windows key

Didn't know about that, learn something new everyday haha :)

I think the first thing I've done with all the keyboards I've had since 97 or something was to pop them out with a pen.

I like my window shortcuts too much to do that :(

I still can't understand why people would need sidebuttons to browse shit on the internet tbh

I use windows key + M for desktop, L for logging off, E for explorer, etc.

bet E gets used alot... wait a minute, u use explorer?

Windows Explorer

does that come with win95?

You need SE for that.

Win+M? I prefer Win+D 'cos you can do it with one hand, and it feels like I'm playing SF.

I got used to using my pinky and thumb so it's easy for me now haha. Didn't find out about the D one until a year or so ago.

win+d is actually better because if you do it again it takes you back to where you were, win+m doesnt.

Good job, have a [+]

I would've rambled more on the comments but that might be a bad thing as I tend to get too technical.

Mouse? Dpi? Hz? EmSexteen