But only once. The rest of the time it probably just, as DonFck says, sends the ID.Vilham wrote:
Im studying this at the moment in SCI for my degree. He tells the truth, all though DonFck may be right that it assigns an Id, however when a player joins the server his name still needs to be transfered to every other player.
Last edited by Scorpion0x17 (2006-11-04 17:35:23)
No, it won't even do that - comparing the time it takes to render even ridiculously long names to the time it takes to render the whole of everything else going on, not to mention the time the code spend doing a whole heap of other stuff is like comparing the human lifespan to the lifespan of the universe. (well, ok, that's a slight over-exageration, but the point is, make your name as long as you want, it makes so close to zero difference that it may as well be zero difference).slicknic wrote:
more likely just causes Your computer to lag.
Last edited by GotMex? (2006-11-04 17:48:46)
No, it's not like that what-so-ever in any way, shape or form. ANY PC that is capable of running BF2 isn't going to even bat a single eyelash over the player names even if they were all sent in their entirety, which they almost certainly are not. This theory is just wrong. Plain wrong. Vanilla wrong.Soldier-Of-Wasteland wrote:
It's just like a web page with 100 pictures at 10k each, and a similar page that has the pictures at 500k.... which one is gonna take longer to load ?
well in cs u can see bandwidth... if i remember it was /netgraph 3 or sometin like that? anyway i remember numbers less than 5 kbps... been a loong time since ive looked thoMarinejuana wrote:
If your name with tag has too many characters, the end of it will appear cut-off in game. So pretty much all of your in-game examples aren't even possible.
I highly doubt that the name is actually transmitted each time somebody does something. Its more likely the user Id # or something even simpler that the server assigns to each person as they enter the server is sent between computers. That would be as redundant as having the sound files constantly sent between computers rather than simply referenced within each individual PC.
Does anybody know a page that talks about how much actually has to be transmitted from a PC as a person is playing FPS? With relateively few separate states like jump, prone, shooting, drawn item, etc, and then 3 axis for positioning in the map, it seems like probably only 15-30 or so different pieces of info would even need to be sent (many of which are mutually exclusive limiting the total amount of info possibly sent). They probably have to be refreshed at least 20 times per second though. And one's computer has to keep up with the possibly 63 sets of this information in order for the game to happen in sync. I'm just curious what the kbps output of a computer playing FPS is to others on a server. That would pretty much resolve this. bet it is a surprsingly small amount of data, but the length of the name is probably still pretty insignificant since it isn't logically necessary to send it more than once per connection.
you laid out 3 posts in a row (#27, #28, #29). try "Edit" on for size and spare bf2s the bandwith of hammering 2 additional posts in a row. you appear to have some sort of obsessive disorder. worst of all, your post which i quoted appears as you need to visit the restroom to go pee.Scorpion0x17 wrote:
Somebody please close this thread now.
actually, if you just spam your gun by holding down MOUSE0, you will cause lag. i laff at the guys with cheap pc's and their MOUSE0 gets stuck.GotMex? wrote:
I suggest we should also limit our shooting, sending radio commands, and talking over VoIP since they will all use up bandwidth. Only shoot when you are 100% you are going to get that kill.
I don't think anyone will notice 4 microseconds of lag.Riddick51PB wrote:
you laid out 3 posts in a row (#27, #28, #29). try "Edit" on for size and spare bf2s the bandwith of hammering 2 additional posts in a row. you appear to have some sort of obsessive disorder. worst of all, your post which i quoted appears as you need to visit the restroom to go pee.Scorpion0x17 wrote:
Somebody please close this thread now.actually, if you just spam your gun by holding down MOUSE0, you will cause lag. i laff at the guys with cheap pc's and their MOUSE0 gets stuck.GotMex? wrote:
I suggest we should also limit our shooting, sending radio commands, and talking over VoIP since they will all use up bandwidth. Only shoot when you are 100% you are going to get that kill.
i noticed bf2 limits you to 22 positions, compared to about 32 position in cs. so it's not such a big deal, but every little bit counts.
the point is not that there is a lot of lag, but any amount of lag is not a good thing. no matter how small that bit of lag may be.
Can you explain how to change it? It's good advice if I can use it..Riddick51PB wrote:
hey ya'll, just a friendly reminder that a long player name causes lag for everyone.
so, a player name like: THE_ULTIMATE_ANGEL_OF_DEATH_PWND
causes the game to have to transmit that across from the server to all 64 players on the server which results in lag.
example:
THE_ULTIMATE_ANGEL_OF_DEATH_PWND [Teamkills] Mr.Joshua
THE_ULTIMATE_ANGEL_OF_DEATH_PWND [Teamkills] Riddick51PB
THE_ULTIMATE_ANGEL_OF_DEATH_PWND [Teamkills] -=Volx=-Ace
THE_ULTIMATE_ANGEL_OF_DEATH_PWND [Teamkills] [B1]Rambo
translation: that requires sending and receiving lots of characters due to a long name.
it can get worse:
THE_ULTIMATE_ANGEL_OF_DEATH_PWND [Teamkills] THE_PLAYER_WITH_A_VERY_LONG_NAME
anyway, use a short name to reduce lag. my suggestion: 18 positions or fewer.
thank you for your support.
That 4ms-8ms causes more stutter then lag per say and it's annoying.Spark wrote:
I don't think anyone will notice 4 microseconds of lag.Riddick51PB wrote:
you laid out 3 posts in a row (#27, #28, #29). try "Edit" on for size and spare bf2s the bandwith of hammering 2 additional posts in a row. you appear to have some sort of obsessive disorder. worst of all, your post which i quoted appears as you need to visit the restroom to go pee.Scorpion0x17 wrote:
Somebody please close this thread now.actually, if you just spam your gun by holding down MOUSE0, you will cause lag. i laff at the guys with cheap pc's and their MOUSE0 gets stuck.GotMex? wrote:
I suggest we should also limit our shooting, sending radio commands, and talking over VoIP since they will all use up bandwidth. Only shoot when you are 100% you are going to get that kill.
i noticed bf2 limits you to 22 positions, compared to about 32 position in cs. so it's not such a big deal, but every little bit counts.
the point is not that there is a lot of lag, but any amount of lag is not a good thing. no matter how small that bit of lag may be.
2 errors in your thinkingRiddick51PB wrote:
if all 64 players do that, then it is 640 bytes, or almost 1 kilobyte of data for each kill. that's a lot of data.VicktorVauhn wrote:
With all the lines of code nessisary to keep up with the positions of moving players, shots fired, and where they hit is an extra 10 charicters really gonna take that long to proccess?
Last edited by Mad Ad (2006-11-05 00:44:53)
SCI is Skills for Communicating Information one module of my degree.Scorpion0x17 wrote:
But only once. The rest of the time it probably just, as DonFck says, sends the ID.Vilham wrote:
Im studying this at the moment in SCI for my degree. He tells the truth, all though DonFck may be right that it assigns an Id, however when a player joins the server his name still needs to be transfered to every other player.
What's SCI? Is it anything like Software Engineering (which is the degree I completed over 10years ago).
If it is and you still think that Riddick is correct, then you seriously need to do some more studying.