Starting KZ but need to configurate Display, FPS and graphic card!

Originally posted by Hardbitter

Just -freq 100 works fine for me.

Ye sorry I was mistaken, your fps_max value must be 99.5 and fps_override 1 to make it work if I'm not mistaken.

It is absolutely acceptable if your desktop and in-game resolutions differ.

I'm pretty sure that fps_max is the only setting that should differ from standard cfg for legal kz gaming, so just download standard config.cfg and change settings we talked about above or use it to see if you use legal values.

I don't know how things are done in radeon graphic cards or if anything at all has to be made there, I think nothing. I didn't make anything. Just choose 100 hz in you monitor configuration and use the freq option in your launch options that's all.

Alright mate. Thanks a lot. fps_override 1 perhaps isn't allowed? where did you get a copy of default.cfg?

[blockquote]
Demo rules
General rules

Demo must be complete. Which means you have to start the demo before pressing the startbutton and end the demo after you have pressed the stopbutton.
Knife & USP are the only weapons allowed.
Demo must be compressed with WinRAR and named like "mapname_author_decimal.time.rar", for example "kz_man_bighardclimb_Ad9r_1337.76.rar"
The name of the demo file (inside the rar file) has to be like this: "mapname_author_time.dem", for example "kz_man_bighardclimb_Ad9r_1337.76.dem"
Submit the demo through our Demo Uploader or to an admin via IRC in case you have problems with the Demo Uploader. Our channel is #Xtreme-Jumps and is located at Quakenet.
Average fps must be at least 85 fps.
The nickname you are using to upload your demo should be the same as your Xtreme-Jumps.eu account to avoid multiaccount.
The demo must be recorded in-eye.
NON-Steam rules

NON-Steam demos are not allowed.
-> Get a legal copy of Counter-Strike if you want to submit record demos on this site.
You are not allowed to use one of the old protocols (eg. protocol 47).
-> Changes in the protocol might affect the game's physics which could cause slight advantages or disadvantages compared to the latest version.
Settings

Demos must be done with these settings:

Server settings:
edgefriction "2"
sv_gravity "800"
sv_stopspeed "75"
sv_maxspeed "320"
sv_accelerate "5"
sv_airaccelerate "10"
sv_wateraccelerate "10"
sv_friction "4"
sv_waterfriction "1"
sv_stepsize "18"
sv_maxvelocity "2000"
sv_cheats "0"
mp_footsteps "1"
Client settings:
cl_lw "1"
cl_sidespeed "400"
cl_backspeed "400"
cl_forwardspeed "400"
cl_movespeedkey "0.52"
fps_max "99.5"
fps_override "0"
gl_vsync "0"
You are not allowed to use any cvar or setting that might give you an unfair advantage compared to the default counter-strike settings (just as cl_sidespeed and so on), even if it's not stated in the list above. Keep your config default!
Gamespecific rules

The demo must be recorded at your own LAN server (aka listen server aka not dedicated). Demos which are recorded at dedicated servers will NOT be accepted.
You may not destroy breakable objects (like bridges for example) or push buttons (with an exception for HP boosters), or push movable objects, before you have pushed the start button.
You are not allowed to use any script or metamod or amxx plugins that give you an advantage to other jumpers.
IMPORTANT: You are not allowed to use methods which show your velocity during a run, this includes:

/speed,
/showpre,
/ducks,
/multibhop,
/duckspre,
/ljpre

...and similar AMXX commands.

In order to disable this on your server, follow next instructions:

For kz_ljs_xm.amxx: remove letter 'c' from kz_ljs_connectenabler cvar in addons\amxmodx\configs\amxx.cfg or if such line doesn't exist add kz_ljs_connectenabler "ab" to the end of file.

For uq_jumpstats.amxx: remove letters 'c', 'd', 'g', 'i', 'j' and 'k' from kz_uq_connect cvar in addons\amxmodx\configs\amxx.cfg or if such line doesn't exist add kz_uq_connect "abehlmn" to the end of file.
You may not use any other timer than the original one.
Using Godmode isn't allowed - use the health button!
Hook/teleporters: You are allowed to use AMX features like teleporters or hook to get up to places you could climb up as well, means you are allowed to use them as a 'support tool' to save "senseless" climbing time before you start the actual run (because theoretically the same record would be possible without teleport/hook - it would only take much more time to get up there every time before you start a run).
BUT: It's not allowed to use teleporters or hook to get an unfair advantage, means gaining more speed or reaching an unreachable spot (to start the run from).
-> Setting a teleporter or hooking to a precise location and taking your speed and direction with you into that teleporter can be an unfair advantage, because this might give you an additional speedboost (and therefore more speed than you could gain without these AMX features).
Demos that require any sprites, models, sounds or gfx not coming with the downloadable .rar/.zip file in the download section are not allowed. Those custom files often come from using inofficial AMXX plugins. If you want to avoid this, you should record your demo at a clean server with the Official XJ AMXX pack v2.1 or no plugin at all.
If you want to use HLTV models, use the non-bugged XJ HLTV models. You can get them in the download section.
-> Other HLTV models are not allowed.
adjust_crosshair scripts (changing the color of the crosshair) are not allowed.
Fakedemos are strictly forbidden. Nobody is allowed to record any demos (for the record or the LJ record section) with a friends nickname or another username. In case of any abuse both involved player will get a 6 month ban from the whole XJ community (Website, IRC, Servers).
It is strictly forbidden to change your keys/binds/aliases during a run, they must be set before you start the timer.
It is strictly forbidden to take any kind of advantage from another player present on your server.
As soon as you started the timer, you have to be the only one "alive".
If the admin thinks that the demo is breaking against any rules, he can choose to not put it on the demo-page. If you do not agree with the admin, you can, of course, tell him what you think about it. But in a polite way.
Timer rules

Ever since it was discovered that the Kreedz-Timer was inaccurate and that timerbugs can occur (FAQ: What is a timerbug?) it caused quiet a few problems and a lot of different rules had to be introduced. To solve this problem a final set of rules was established:
-> The XJ record system is using a real time time-measurment system allowing millisecond times up to 2 decimals!
It's not possible to beat demos with faster times in the third decimal place (.00x), if there are two demos with the same times in the first two decimal places the first submitted demo will be accepted (first come first serve). -> This is based on the fact that the demand interval of the hl engine is not capable of giving solid and valid times beyond the second decimal place 100% of the time (then again timeshifts would be happening in some cases, which would be way harder to determine than the old timerbugs, since they are happening in the decimal areas): Because of the quantization of time measurement in the hl engine in 0.01s intervals the mean error of one time measurement is 0.005s. So the statistical variance for the measured record time is Sqrt[2*0.005^2] = 0.0071. Every time difference smaller than the statistical variance is not significant and only based on statistical effects so it is likely to have occurred only by chance.
To check the real times performed in your demos either use the Official XJ AMXX pack v2.1 in your run, or use the DemoChecker after the demo was recorded (or both, if you want to be sure). -> If different times are shown (caused by massive ingame lags, for example) the DemoChecker time will always be more accurate and therefore overrule the plugin time.
Rules about cheating

Any kinds of jumpscripts (bhopscript, doubleduckscript, duckscripts etc) are strictly forbidden! The only command that your jump or duck key is allowed to be bound to is "+jump" or "+duck".
You are not allowed to install and use plugins or tools that effects the jump or duck command in any way!
You are not allowed to use tools or other stuff that might affect your game in any way, especially not tools to slow down the ingame speed ('slowmo').
[/blockquote]

Originally posted by Hardbitter

Try using net_graph instead of cl_showfps, it should differ there hopefully. You don't have to run it in launch options, just enable it with console command.

Screen tearing is a normal thing for 100hz setting, I got used to it really quick, I don't even notice it now. Unless you have some heavy tearing? For me it's slightly visible noise appearing from time to time in the middle of my screen.

CS video options
http://imgur.com/a/KEXyi

Now my settings are:
[blockquote]
cl_showfps 1
net_graph 3

fps_max 99.5

Windows Display setting: 100 hz
Video Card Panel: 99.9304 hz (ATI Radeon panel)

-freq 100
-refresh 100

Resolution: 1024x768
Display Mode: Normal (4:3)

Run in a Window: NO/YES
[/blockquote]

with that, i'm getting screen tearing in the middle of the screen , and if I use RunInAWindow: YES then I get also lag like if a heavy program is also executing and lags your game. Than can be other thing.

I tested some Display Modes of Normal Screen and WideScreen, I think 640x480, 800x600 and 1024x768 are what work best for me in 4:3.
I tested RunInAWindow and is good with 1024x768.

What I tested also is that if I change Windows Display Setting to 120 hz or 144 hz then the screen tearing disappears. But I don't know if this is good that the monitor hz's are greater than the game FPS's.

I wish I have nvida again with that great settings panel where you can set "leave control to application",
my ATI Radeon panel is not as easy.