Luckily for you there is a way out of it...




































































get good.

im

MVP :o

Buy a good monitor for playing games man. Namely BenQ XL2411T.

cg_drawFPS 1
cg_lagometer 2

stable fps and clean lagometer (no blue/yellow triangles, spikes etc) are two factors.
Then there's Weird's hypothesis on low pings (long read but worth it)

Maybe you're using some strange timenudge setting or autotimenudge.

Check your refreshrate by pressing the info/menu button on your display.
Check r_displayRefresh

Last but not least, check for this cvar in your repconfig (automatically generated by QL)

cl_placebo 1/0 (can be beneficial or detrimental)

display: 1920x1080 60hz.
autotimenudge 0
timenudge 0.
com_maxfps 60
maxpackets 125

edit: when i play in window mode the game runs lil bit smoother

com_maxfps 60

why???

because my lcd cant handle more with this high resolution.

so the solution is getting a 120/144hz screen, then using 125fps

i accept plusses

1 hour later

Even tho your LCD do 60Hz you have to use com_maxFPS 125, then you use r_displayRefresh 60. You should hear us on that point man.

ill try

r_displayRefresh "60"
com_maxfps "60"
cl_maxpackets "63"


now game runs better then before, still not ok but more playable thx @all

you didn't change anything, or are trolling?

afaik you are playing with maxpackets 50 that way, everyone's advice in this thread said: play with 125fps and get 120hz screen as soon as possible.

ill play now displayrefresh 60 , maxpackets 63, maxfps 60 and its smooth.

if maxfps > 60 its not smooth anymore

wouldn't it make more sense to use maxpack 120? 2 per frame

frame starts laggin, unsmooth

strange, since it should be more in sync than with the 63 one; anyway, not really surprising

I can't tell if you're being silly or computer illiterate.

Maxfps 125 maxpackets 125.

Unless they changed it, maxfps 60 = maxpackets 60.

com_maxfps isn't only for the number of images rendered. It's used for networking and probably for input too. It's not really a good idea to set it that low unless maybe if you can't get it stable higher.

use a lower cg_playerlean maybe

On a big ffa server I can confirm your experience, feels like it's running on a playstation 1 racket.

Why are you using maxfps 60? Doesn't that limit maxpackets?

Why are you using maxfps 60?
display: 1920x1080 60hz.
Meaning: a sort of manual vsync.

Doesn't that limit maxpackets?
As far as I know the fps-rendering/netcode relation wasn't even conceived to be a part of QL since it derived from an old and silly architecture in the code that handled the way that gamestate snapshots were created and decoded. In fact, if I'm not mistaken that's some pretty old stuff from that shitty cpma mod or maybe osp... maybe I read somewhere that cpma did initially have it but not anymore?

in my case when maxfps 120 and maxpackets 120 , the green line in lagometer is unstable (lcd 60 hz). so i ve choosen maxfps 60 and maxpackets 65 (lower then 65 isnt available says console).

Well of course it's gonna look unstable, you're sending twice as much data. Also means you have twice as much data to plot what your connection's like.

125, 120 = 63.

?

there are steps for maxpackets, afaik it's 42/50/63/125, they do not correspondend 1:1 to maxfps.

isn't maxpackets 120 tops in ql (no 125 option)?

no? cg_drawfps 1; com_maxfps 125

I recall weird saying once that even though it will draw 125fps it's really 120

will have to check that

I recall someone else saying it the other way round, very recently, if you put it to 120 it's still really 125, I've got no idea personally, but id "changed the renderer" whatever that means, and it changed something with frames per second too

this?

you must have some awesome memory :D
The value shown by the (q3) command is rounded. It doesn't really say how many fps you have.

Now I don't quite remember what the equation is by heart but I thought it was:
1000 / round ( time spent to calculate this frame ).
Where the round rounds off to the closest Millisecond.
(round could actually very well be either Floor or Ceil though (as JC likes floor a lot))

(I'll assume it's round)
So if your pc takes 8.49999999 ms to calculate the next frame you'll actually have 117.smth FPS.
And if your pc takes 7.5 ms you'll actually have 133+1/3 FPS.
In both cases however the shown FPS would remain at 125.

btw... I feel like I am forgetting something minor here....
Perhaps it uses the time spent on the last 3 or 4 frames to calculate the FPS or something (I'm not completely sure on this).

lowest value possible is maxpackets is 63

ah, so they changed that in ql. then it's either 63 or 125.

since this thread is going nowhere...

you complain about a laggy game when lots of players are around and are playing with maxfps 60? the advice was to use maxfps 125 to be able to get maxpackets 125, is there any sane reason why you still aren't doing that?

see here: http://www.esreality.com/post/2391050/ffa-pin...pid2391427
and here: http://www.esreality.com/post/2391050/ffa-pin...pid2391404

stop playing dumb.

reason: framerate isnt smooth with ur suggested settings.

maxfps 60
displayrefresh 60
maxpackets 63

is my solution and works for me ok?!

On some players (lots theese days) itz hard to hit when they move - have to aim near the model to get a hit with hitscan weapons.

ah, i didn't realize you couldn't get stable 125fps. i'd suggest autotn 1, but you're already complaining about lag, so ...:d

i m not used to autotimenudge and it feels strange

Yeah can someone explain autotn to me?

Everything just looks very jittery and models keep stuttering, impossible to play like that

the theory i heard was that it uses "cl_timenudge ping/2", but i'm not sure if that is true and what happens once it exceeds -20.

so lower your resolution instead of playing 1920x1080.

why sacrifice framerate for resolution?

seems counterproductive if you ask me.

he probably uses a laptop running at native resolution, still: 640x480 is the way to go, i didn't even see that last time i checked this thread.

i'm able to get 125fps on most maps with an old netbook with r_mode 5/r_vertexlight 1/r_shadows 0/r_subdivisions 80.

What's your rate ?
cl_packetdup ? (some say it's placebo but I can feel the difference between 0 & 1)

is it on FFA only ?