Commands to reduce lagg and full screen

[Wolfthorn]

Hi! Can you please write a list of commands so it doesnt lagg in game and i get full screen. TY!

[Stavros]

seta cl_maxpackets "100"
seta cl_packetdup "0"
seta snaps "40"
seta cg_predictitems "0"
seta rate "34000"
seta cl_timenudge "0"

 

seta r_fullscreen "1"

[captnconcrete]

i have a question  .. i thought 30 or 20  unless u live next door to server then 40 works .. other wise it causes a loop? am i wrong?

 

 

The snaps setting is used to calculate how many game world updates you receive from the server. Usable range is 10 to 'server sv_fps setting' and defaults to 20. Version 1.17 of Quake3 forces snaps client side to a maximum of 25 or in some cases a maximum of 30. However the network code works in such a way that snaps should always be set to match or be above the server's sv_fps or a divisor of it.

Leave snaps at your default until you encounter a server that needs a higher/lower setting

 

 

This causes the server to resend the missing packets when your snaps are set to 30 actually before the next snaps cycle begins (a maximum of 10 replacement packets "snapshots" if needed) thats why it I included the 30 snaps. 40 snaps just duplicates the 20 snaps twice over but takes longer to extrapolate the info in relevence to position / accuracy on the server (great if you live on the doorstep of the server).... Thats why you see a lot of older Q3 guys play around with it in wolf.... They know more about the wolf q3 engine /net properties than you think... !

 

so i mused be missing some thing here is there  a trick to it if u set packet dump to 0 u can use 40 an it wont loop? im just a curious beaver is all not trying to be a ass. this is what i always thought.

 

snaps should always be 20 (or maybe 10 on dialup), since the server will never send more than one snap per server frame, and varios things in ET break if sv_fps is not 20. ETpro will force your server to run at sv_fps 20. Setting snaps higher than sv_fps won't give you more snaps, but it can confuse the rate limiting code, so don't do that.

Edited April 30, 2017 by captnconcrete