wtf is bytes/sec in f6

[CLANKILLER]

what is the average sort of range for this stat? i dont remember it being 160,000 which is what i get lately at the public US server?

fucked if i know whats up...

[unrealshots]

yea pure instagib us has been extremely laggy lately i dunno what it is

[InfamousRaider]

Those numbers look normal for instagib, not a lot in info to send.

[Finalz]

my ping in general on ipug servers have been through the roof recently, considering im not the only euro pinging 180 all of a sudden is shit and wont allow us to play.
it was a pain in the ass playing in the sdom league with that ping :p

[Chadwixx]

Im up around 19000 on input, other servers (non newnet) im pulling like 3000-4000. Output is still around 3000 on both types of servers.

Thats means my hitbox = big but my shots see a small hitbox (explains why alot of shots arent counting).

[TimTim]

[Chadwixx]

Does newnet send these requests (each player) in bulk or individual?

The engine interprets 64kb as 1 fps (online), at 19000 im around 296 fps server side while my side is seeing 62.5fps (4000). The ut99 engine naturally tears at 150fps, it could be the cause of the desync.

"You're receiving more bytes per second because you're constantly receiving info about every enemy player"

It should also sending info about your teamates for collision detection and boosts. Maybe its just too much data for the engine.

[TimTim]

That isn't how it works. I'm busy at the moment so I'll have to explain it later.

I will quickly mention though that you aren't receiving much more data per player, but you are receiving data for every player on the map rather than just those within your vicinity. I did this to fix a couple of issues, and the benefits of it greatly outweigh the drawbacks of requiring more bandwidth.

[CLANKILLER]

thx for replying guys, in the screenshot it shows 15534* but the * was a number most of time i was watching it. so 155340 bytes which is a shit ton..

at the UK server is plays much smoother for me and i hit alot more, on US server i swear shots dont register or the person i shot dies about 3 paces later on my screen.

heres a screenshot of UK server and its totally different and steady at around 7000 up and down

[SJA94]

Doesn't the bytes/sec drop down at the end of games?

[RickJames]

Isn't the us IG server usually full of players though? Can't remember what the player limit is, but I think it's like 12 or 14 or 16. If the uk IG server was way less populated, that would explain the difference.

I felt like newnet felt different on us ig than on the pug servers (felt like hitting was a little different). I've never had an issue with nn in a pug. I get like 5000-6000 bytes in, with one guy in warmup with me, to #ipug servs.

[TimTim]

Ya, RJ gets it.

The number of inbound bytes per second is proportional to how many players are in the server with you at the time, which can get to be over 18000 with a full server. And if you have a shoddy connection (like say, from certain parts of the UK to the US) it will jump up quite a bit if you're getting packet loss or if your connection drops for a split second, because the server needs to make up for data that you never received.

[Chadwixx]

Both pubs are 12 man max and usually filled up. It both servers use newnet and one is going much higher than the other, then it has to be something with the set up.

Anyone know the tickrate on the uk vs the us? It could be multiplying if those cheap euros still refuse to spend and extra $2 and get a tickrate higher than 30

[SJA94]

I think they are both 100tr.

[CLANKILLER]

i just think that server plays like fat ass with newnet on it. not saying its newnet at fault but ever since it changed over it is terrble for me anyways.. was the last place i enjoyed playing, how i can double my ping and go to the UK server to get decent play is beyond me..

CK..

[RickJames]

Hey Clankiller I just noticed that you're using 14000 netspeed on the US IG server and 20000 on the uk one in those screenshots. Try using 20000 on both- I think 20000 is best for newnet/100 tickrate play.

[Chadwixx]

Not seeing any advantage with newnet in ig. I can see its advantages in weps with the hit detection but what does it actually bring to gib?

[HuMPtY]

[Chadwixx]

Did it fix the double shot (reg shot + zp shot macro) for ppl who ping 30?

I feel the little 64bit ut engine is being overworked with the current settings. We set the servers to 100 tickrates to compensate for the flaws in zp. With the newnet adjustments there is no need to keep tickrates that high. Drop them down to 60 or 45 (hayday setting) and see what happens, its currently using too much bandwidth.

Ace also needs to lower the min value. 10000 min is like tearing mode based on how the engine interprets the 64k packet. Thats why we cap fps with netspeed not ini setting. 64k = 1 fps, at 150 the ut engine starts tearing because it cant keep up, thats a 9600 netspeed setting, something you cant obtain with the current min req.

Cant seem to snap on the us server, not much fun to shoot walls when your mouse is on the target.. Will check again later and hope its more playable, currently its kind of annoying to turtle the xhair in order to make shots.

[RickJames]

chadwixx, your posts show that you really don't know much about newnet. The first thing I'd suggest is using 20000 netspeed on any newnet server, as newnet is designed for 100 tick and 20000 netspeed is best for this. It would probably feel a lot better for you if you used 20000.

Also, you said that you cap fps with "netspeed and not ini setting", which is a really outdated way of doing it. Cap fps in the opengl/d3d settings in your ini.

[Chadwixx]

Im currently using 20000 netspeed. I just think capping it at engine is better than capping it after the engine. The engine is from 1999 and made for 56k, of coarse its an outdated way to do it.

Either way im done, this game is way to inconsistent and has no cheat protection, its just not worth the headache anymore.

Thanks for the help

[Meth]

I honestly feel that 100 tickrate is too much for a 20000 netspeed capped NN server. It's 100% fine if only 9 people were playing in a match, but with 10+ that my bytes/second goes past 20000 and my frames drop/game gets choppy/hitscan bugs are abound. I remember when the tickrate was 60 on US/UK IG w/ NN and there was 0 issues with 12 people (pugs were also incredibly smooth before the positional updates were added to NN). It became completely unplayable on US/UK for me now that it was set to 100.

Is there really -no- way to increase the netspeed cap past 20000, or lower tickrate to say 90/95? I can't even bother to pug anymore with how annoying it is.

[TimTim]

I play with 25000 netspeed. And since ACE's highperftoggle decouples framerate from netspeed, there are 0 issues there (as Chad seems to have assumed). You could increase your netspeed to 10000000 and it wouldn't matter. All that number means now is the cap on the bytes per second; and unless you're still on dialup, your connection should be able to handle it no problem whatsoever.

[Meth]

[TimTim]