Member
111 posts
Registered:
Jul 2006
hi
im using 150 hz on monitor and 154 fps in ezquake.
any advantage / disadvantage for me if i use cl_earlypackets 1 ?
Moderator
1329 posts
Registered:
Apr 2006
Perhaps time to read the news article about it?
Member
111 posts
Registered:
Jul 2006
Perhaps time to read the news article about it?
I just love your style Renzo, your personality just SCREAMS Admin
it's like you were born to be an Admin or some sort of Boss atleast
ontopic: I read the article and I now feel like I know everything about fps-i and earlypackets
Moderator
1329 posts
Registered:
Apr 2006
I don't think so. It's just that it feels like worthless job when you see someone asking about something you have "wasted" a lot of your time trying to explain it elsewhere, like in wiki, documentation or on some news item.
Member
111 posts
Registered:
Jul 2006
I don't think so. It's just that it feels like worthless job when you see someone asking about something you have "wasted" a lot of your time trying to explain it elsewhere, like in wiki, documentation or on some news item.
hehe.
BTW I kinda meant more to ask about the part of cl_earlypackets 1 where fps and hz on monitor doesn't "need" syncing anymore for smooth play, I'm maybe babbling here but what i'm wondering more specifically is,
since I don't sync my hz (150) with fps (154) does cl_earlypackets 1 benefit me in some way?
meaning I don't have the problem with ping close to frametime (12-25 jumpy ping) but just that sync problem
Member
1435 posts
Registered:
Jan 2006
Now, this is the part where the new code, cl_earlypackets 1, kicks in. ezQuake will no longer wait for the cl_physfps frame for updating your view, instead cl_maxfps value is used
your physfps is 77, maxfps is 154