New Restrictions for Clan{KEA} Servers

[DeathInc KEA]

Due to the use of an advanced q2admin that has been implimented on all of the Clan{KEA} Quake2 servers...you will now need to either use the basic q2 client or the r1q2 client. All nocheat clients will not be able to connect.
I highly recommed droping the nocheat client for the r1q2 client since it is 10 times smoother than nocheat...has a built in XP mouse fix....and can handle all pac files for graphics.
Here is a link:

r1q2 - r1gx client/server

I highly recommed that you try this q2 client out. I've been using it for the last 8 months and I'll swear by it.

[daelmun]

http://www.kontula.net/comments.php?id=145

^nice easy to understand instruction on how to disable the weird physics in r1q2 to make the client feel like reg quake2.exe.

set vid_ref r1gl
set cl_async 0
set cl_smoothsteps 2
set cl_protocol 34 <- in order to make demos recorded with the client usable with other clients and also keygrip2, usefull if you collect frags for a movie or something else.

Read the guide, it's worth a look.

Note that locs are placed in the quake2/baseq2/locs folder and NOT the quake2/locs folder, a lot of people haven't realized this

[DeathInc KEA]

set cl_protocol 34

Just a note, that by using that command it will disable all the network fixes for r1q2 thus rendering it to run not nearly as smooth as it is meant to.

[naymlis]

set cl_protocol 34

Just a note, that by using that command it will disable all the network fixes for r1q2 thus rendering it to run not nearly as smooth as it is meant to.

damnit! i can't decide whether to use it now or not.. but i haven't noticed any major differences between the two since i started using 34 a few days ago, so i'll probably just stick with it.

[daelmun]

Yeah, been using protocol 34 for a couple weeks now and nothing really different, so I'll stick with it. Think if people in 100 years find a quake2 demo but can't watch it cause they don't have r1q2 Would be sad, wouldn't it?

Yeah, didn't notice that smoothsteps was set to 2 there, it used to be 0. I guess I should read my own posts and learn something myself, I'll try smoothsteps 2 untill I see if it's a good or bad thing

From the r1q2 readme:

cl_smoothsteps [0/1/2/3]
Smooth movement up steps/stairs. The prediction that smooths this doesn't work so well at low cl_maxfps values so you can turn it off. 0 = off, 1 = original Q2 style step smoothing, 2 = more aggressive step smoothing, 3 = try to detect 'steps' and only smooth them. If cl_async is set to 0, this cvar is ignored and the original Q2 style smoothing is used. Default 3.

cl_protocol [0,34,35]
Protocol version to report. Defaults to 0 (autodetect) and will attempt protocol 35 followed by 34. Sometimes though you may have to set cl_protocol 34 to connect to some weird servers or if a server is running an old version of R1Q2. You should normally not need to touch this.

[X'tyfe]

set cl_async 0 why? this is a good thing
it decouples r_maxfps from cl_maxfps

if you want your fps seperate from your cl_maxfps, do this

set cl_async 1
set cl_maxfps 30 (no more or less then this)
set r_maxfps 100 (anything you want)

[Slikkster]

I tried the r1q2 client without R'ing TFM (doh), so I stopped using it.

[10zx]

r1q2 crashes on me from time to time..

[naymlis]

r1q2 never crashed on me on my pc, but since i started using it on this one it usually always crashes when i alt+tab it, but never has for any other reason.. and i think i read that if you use cl_async 0 it automatically sets smoothsteps to 0.. couldve read it wrong tho

[Yuna]

Quake 2 crashes on me sometimes but only since I've had WinXP. It crashes sometimes if I use original Quake 2 or r1q2, neither of them crash more or less than the other. I've never been able to alt-tab. I have to put it into windowed mode, bring down the console and then I can move the mouse into other windows. Putting the console up means the mouse always moves back to the middle of the Q2 window, so you can aim.