aim to model!

great advice, it helped me

I would like to know that :P!

snaps is the setting that affects it, which is set to 40 as default now.

I read snaps was removed.

clientside (?)

- Changed Server Framerate - Servers now run at an increased framerate (sv_fps 40) for a smoother play experience. No adjustments need to be made by the player to take advantage of the new server framerate.


- Removed snaps cmd - As noted above, the clientside setting of a snaps cvar is no longer necessary. Clients automatically run at the appropriate rate regardless of the server's framerate settings.


from changelist

read that too but when you open up console and \snaps it still exists?! not sure why and so on :D

If you have old commands in your config they'll still appear in console

It's removed since the client receives the needed information from the server and doesn't need the settings any more.

talk to the hand, cause the server ain't listening.

Warning : I'm missing a lot of the picture here so probably only the general idea is roughly there.
Quick, someone who's been through all this, please dumb this down for us (Jalisko ? arQon?) ! ;)
Might want to read some of this - slightly outdated but most ideas still apply.

AFAIK as long as you are holding fire, your client says +attack, so you don't get to say "I shot that many rounds", only "I'm shooting/not shooting!" (same for other user commands ie +left +right +moveup). When you're done, it says -attack.

The server's the one which actually deduces and processes whatever amounts of rounds you are shooting since you started saying +attack, until you say -attack... and then there's how everyone's commands are processed vs. the actual game world rate (sv_fps!)

Now, do we only send +attack when we start shooting and -attack when done, or does it keep flooding the command upload as long as we're holding ?

I suppose depending on that and how the server treats it, if you're superhuman and can twich-click at 20hz, what you're suggesting may or may not make a slight difference. (think CPMA shaft on gtv, a new sound played for each LG cell.)

massively edited for less bullshit, still contains traces of it

I just can't imagining spamming every command in every packet, I'd bet on them being switches, on and off. There are alot of commands and sending them each 125 times per second is just crazy

then again you need to make sure such events are triggered, or what would happen if you run into packet loss?

I've ran into packetloss when releasing mouse1 and it kept shooting, so uh, it keeps shooting, obv. : o

yeah rite, packetloss in sweden ;(

polish server ; D
POLAND POLAND POLAND POLAND POLAND POLAND POLAND POLAND

+attack / -attack aren't commands, they are toggles for buttons. They map through to just a single bit in the buttons member of the usercmd_t structure. The whole usercmd_t struct is sent in each packet - see CL_WritePacket calling MSG_WriteDeltaUsercmdKey.

However the server is simply looking for the change in the "usercmd.buttons & BUTTON_ATTACK" state to decide when it should start/stop firing. So yes, hemo's description is accurate, AFAIK.

Yeah, it's like you don't say "I'm spraying cum everywhere" in every comment in a thread. You just do it once, and then everybody knows you're [constantly] spraying cum everywhere.

Test:

"I stop spraying cum everywhere."


Thanks a lot, this really helped!

i'm 12 and what is this?

That's perfectly reasonable. The +attack and -attack. However, assume that you have +attack the whole time you LG your mouse movements must be sent to the server too. And what's not more perfect than a mouse movement update precisely at the time your LG reloads and not inbetween?

Consider the situation where you send your crosshair position packets precisely inbetween two LG slugs, that's not very optimal since it means you'd be hitting something which was 25 ms behind where your target is. Meaning an added theoretical latency of 25 ms for the LG.

ask kgb, he somehow has the best lg i've ever seen.. online.