banimod / etpro / ettv forums

Thanks for the replies guys I appreciate it. I need to read like a primer on this stuff. Its interesting to me. But I dont have a great sense of it yet.

doesnt matter what timestamp your client commands have, if your opponent's command gets to the server first. and network jitter will have the greatest effect on that, far more than any mouse tuning you could do. he could pull the trigger much later than you, but thanks to random network jitter (and...

network jitter from client to server, and server to client. clock slip between server and client. server cpu and network load timer resolution on win32. engine withholding snaps from client so interpolation works. builtin command delay by client. variable delay from client snap and other cgame proce...

Bani, I think you and I are on different pages here, you know much more than I do about it of course, so perhaps we are on the same page and I dont know it. Hmmm. Ok ignoring mouserate for a second, and stipulating perhaps wrongly, that server works in 50ms gameworld increments/timestamps. All those...

I can understand there are multiple lags/noise. [BTW I would LOVE a post on a what actually happens when a player sees an enemy for first time and shoots. Say from start time on image appearing on players screen, to player seeing it/acting on it, to the mouse button being pressed, reported to the cl...

PW post: In Reply To #20 board guest 1964993 wrote: "125mhz is already beyond anyones reflexes, you'll notice no difference putting it higher" My reply: You raise an interesting point about reflexes. The patch basically takes the mouse response from 8ms to 2ms sampling. As I understand it,...

All the stats programs spit out gib numbers, but as far as I can tell, there isnt any gib info in the etconsole log, and thats the only thing they look at. Where is this info coming from? I assume this is from the server log, not the client console. Yeah, sorry, CLIENT log, etconsole.log I havent l...

Ahhhh,

Had to read it a couple time, but I understand now. Everything is the same with the first shot, but its just the same as is if ones mouse delays the first fire button signal for 100ms, everything else is calculated as usual by the actual game/computer etc.

thanks reyalp

I was wondering the following: With antilag, I no longer try to lead people at all, I just shoot at where I think the head hitbox is. 1)Does antilag take into account the 1/10 of a second fire delay of the initial shot? 2)Is the 1/10 of a delay significant, ie how far does the players hitbox move in...

All the stats programs spit out gib numbers, but as far as I can tell, there isnt any gib info in the etconsole log, and thats the only thing they look at.

Where is this info coming from?

maybe the nummer is the cleint id then Yeah, I thought of that, but the first error message seems to equal the players that are availbale on the invite list to pick, then it switches to the other error message, at least the two times I tried it with: bind x "fireteam create; vote no; fireteam ...

Sauron|EFG wrote:Wouldn't it be enough (or even better) to just add it to the end of round stats (cg_autoaction) if all you want is the number of revives by each players?

Well, I am lazy and it would be cool to have it in the regular stat programs, but yeah, how would I get it the the cg_autoaction thingy?

"fireteam invite 1" (using 1 as an example) has always worked for me. I have no idea why it doesn't work for you... When i do his script it says invalid client selected fireteam invite 1 invalid client selected fireteam invite 2 " (repeated=number of people on the fireteam invite lis...

bind x "fireteam create; fireteam invite 1; fireteam invite 2; fireteam invite 3; fireteam invite 4; fireteam invite 5; fireteam invite 6" might work The "fireteam create" worked, the fireteam invite 1 etc failed. Fireteam create brought up the f1 f2 vote thing first, so I guess...

Gotenks,

I like your signature a lot : )