An excerpt from my ongoing saga w/ NFO

[CraftyDus]

So I've been in a support ticket with the guys at NFO since last Friday, after a couple server moves and changes to the config , where the server was noticably better, I arrived at this discovery.

Monitoring your servers FPS via our FPS monitoring tool I do not see any issues there. Currently it is at 1030FPS with jumps up to the 4000 range.

I also see you are running league configs. Be careful about those as many of them were crafted by people who didn't understand the engine. Therefore incorrect rates are specified. I would encourage you to go through those and replace their rates with ours.

Please test your server for about 10 minutes and let us know. Keeping in mind if you see any high pings, FPS drops or any choke/loss in net_graph.

we had a 40 minute scrim, and noticed registration issues again, and when I check events , I see that it was moved back to chicago-dodec306-3. Our league configs are adjusting netcode in this way

sv_maxrate 25000
sv_minrate 20000
sv_minupdaterate 60
sv_maxupdaterate 101

now I see the valve recommends for client rates are this after their recent update



is tpgbasic2.cfg of

sv_maxrate 25000
sv_minrate 20000

ignoring the valve increase to 100000 for a client rate?

are you saying this one occurence of the league cfg's adjustment of the net code is causing problems with shot registration?

It very well could be, and it can open the door to choke for players. Having looked at league configs for various games for nearly a decade now, I can honestly say that leagues generally don't know how to adjust for server performance and usually get the settings wrong. I would recommend using this instead:

sv_maxrate 0
sv_minrate 100000

This will force up a players connection since some players may not have them adjusted properly. Any broadband connection can handle the rate fine, so there is no reason to lower it.

So my question for tpgadmins:

Do you mind if I change my tpgbasic2.cfg to 0-100000 from the old 20000-25000 so we can actually use the new rate 100000 in scrims/12man/matches?

[defiance]

(Make a ticket when you want official answers, as looking for official answers on 1911 will never happen because of trolls/idiots.)

Is tpgbasic2.cfg a typo? Because the config is tpgbasic.cfg and I already updated it to 100000, if you havent updated your configs since the update you are using the incorrect config.

[defiance]

Also, the guy could be referencing tpg2basic.cfg if you have that on your server still...but we don't use that for anything so it is never active. Your server is good crafty. Shots are going to miss on any server.

[Gorillabc]

Crafty, I know we got into over your server, hope you're not still pissed off about that. Like I said then, I have a NFO server at the same location. However, I don't pay for the Ultraccelerator or higher priority. Even thought I don't pay for either of those, my server still maintains 1000+ FPS even in a scrim. I don't know about now, but back when we had that argument my server was performing much better than yours as far as registration and overall feel.

All that being said, the min/max rate cvars aren't what's causing the problems on your server. I only just now updated my config when I read this thread, so back then we had the same min/max rates.

[Joshinator]

[Miller`]

(Make a ticket when you want official answers, as looking for official answers on 1911 will never happen because of trolls/idiots.)

Is tpgbasic2.cfg a typo? Because the config is tpgbasic.cfg and I already updated it to 100000, if you havent updated your configs since the update you are using the incorrect config.

May want to make a tpg news post about the config update. I was not aware of the updated config and there is not a post announcing the change.

[nunz]

(Make a ticket when you want official answers, as looking for official answers on 1911 will never happen because of trolls/idiots.)

Is tpgbasic2.cfg a typo? Because the config is tpgbasic.cfg and I already updated it to 100000, if you havent updated your configs since the update you are using the incorrect config.

May want to make a tpg news post about the config update. I was not aware of the updated config and there is not a post announcing the change.

there was before the season started i believe. a reminder may be necessary.

[CraftyDus]

Crafty, I know we got into over your server, hope you're not still pissed off about that. Like I said then, I have a NFO server at the same location. However, I don't pay for the Ultraccelerator or higher priority. Even thought I don't pay for either of those, my server still maintains 1000+ FPS even in a scrim. I don't know about now, but back when we had that argument my server was performing much better than yours as far as registration and overall feel.

All that being said, the min/max rate cvars aren't what's causing the problems on your server. I only just now updated my config when I read this thread, so back then we had the same min/max rates.

My server has been through several moves and reconfigurations just in the past week.
Let alone since when you played on it that one time in early April.
It's running the tits now. I'm quite happy with it.
My support ticket reads like the fuckin Bayeux Tapestry.
And the support guys at NFO have been good and able to long suffer my withering inarticulate parroting of player complaints, 80% of which are simply missed shots.
I'm glad to know about the sv_maxrate increase, I think a lot of server operators in our community missed that .

My complete NFO Support Ticket

[cassinoroyale]

Shots are going to miss on any server.

With the exception of Taylor "hXc" Graf or Ryan "Jules_Winnfield" Morin

[SKiNnTo]

Good thread, thanks for sharing your experience with NFO.

[Jakimo]

u too skin

[sevEN]

u too skin

whaaA?