Re: [hlds_linux] TF2 Config Help?
hehehe, anyone have some basic kernel config suggestions? On Wed, May 13, 2009 at 7:00 PM, Richard Eid wrote: > Huh? Safe from what? 67 produces the same results as 66, so there's no > reason to use it. If people complain about you using 66 instead of 67, > rest > easy knowing that they don't have a clue. > >-Richard Eid > > > On Wed, May 13, 2009 at 8:45 PM, Cc2iscooL wrote: > > > Better safe than sorry, I guess! (One less thing for srs bzns players to > > whine about.) > > > > On Wed, May 13, 2009 at 6:45 PM, Richard Eid > > wrote: > > > > > Yeah, 67 is the new 101. Pretty much pointless, though arguments could > > be > > > made against that if you watch net_graph. But even at 66, you'll see > > 66.x > > > coming through at times. > > > > > >-Richard Eid > > > > > > > > > On Wed, May 13, 2009 at 7:33 PM, Cc2iscooL > wrote: > > > > > > > That's about what I have mine set to. I always set to 67 for maximums > > > just > > > > to get that possible "extra" though. Might as well be over than > under. > > > > > > > > I'd recommend rate 15000 for a 32 slot though, at least. > > > > > > > > On Wed, May 13, 2009 at 6:01 PM, Richard Eid > > > > wrote: > > > > > > > > > The problem, though, is that 100 doesn't exist in Source 2007 for > > > > > cl_cmdrate > > > > > and cl_updaterate, so those 100 settings are meaningless. And a > > > minrate > > > > of > > > > > 10 is a little rough. Unless everyone connecting to your > server > > > has > > > > at > > > > > least an 800Kbps or greater download speed from their ISP, they'll > > have > > > > > some > > > > > major problems playing on your server. > > > > > > > > > > You're right, though. The important settings in your config are > the > > > > > minimums. They are far too high for a lot of people and the 66 > > cmdrate > > > > and > > > > > updaterate minimums that it is defaulting to are also a problem. > > > Unless > > > > > people can hold 66fps on their client, they may begin to see some > > > timeout > > > > > issues. I'd leave the min values for everything at the defaults. > So > > > my > > > > > config for you would look like: > > > > > > > > > > sv_minrate 1 > > > > > sv_maxrate 0 > > > > > sv_maxupdaterate 66 > > > > > sv_mincmdrate 30 > > > > > sv_minupdaterate 20 > > > > > sv_maxcmdrate 66 > > > > > > > > > > Those settings are a lot more fair to the clients that will be > > > connecting > > > > > to > > > > > your server(s) and will generally provide for a better overall > > > > experience. > > > > > I'm actually surprised you're not seeing a lot of timeout issues > and > > > > other > > > > > connection related errors. > > > > > > > > > >-Richard Eid > > > > > > > > > > > > > > > On Wed, May 13, 2009 at 6:06 PM, Danny Heinrichs > > > > > wrote: > > > > > > > > > > > Just wanted to chime in with my settings. Most admins don't like > to > > > > give > > > > > > theirs out because it takes a lot of research (at least for me) > to > > > > figure > > > > > > out how to achieve no choke and no loss with srcds TF2. > > > > > > > > > > > > As long as your box can handle the extra bandwidth (I know you > said > > > you > > > > > > have > > > > > > 100mbps, but there's always other issues such as packet loss), > > these > > > > work > > > > > > well for me: > > > > > > > > > > > > sv_minrate 10 > > > > > > sv_maxrate 0 > > > > > > sv_maxupdaterate 100 > > > > > > sv_mincmdrate 100 > > > > > > sv_minupdaterate 100 > > > > > > sv_maxcmdrate 100 > > > > > > net_splitrate 300 > > > > > > net_splitpacket_maxrate 6 > > > > > > > > > > > > The important settings here are no the max's, but the min's, and > > most > > > > > > importantly the minrate boost. The reason I have min rates that > > high > > > is > > > > > > because some clients we're having lots of issues with everyone > > being > > > > > jumpy > > > > > > because the client cmd/update rates are 20/30 by default. Far too > > low > > > > for > > > > > > our 32 slot server. The split packet stuff doesn't have an > effect > > on > > > > on > > > > > > the > > > > > > choke/loss that I have witnessed, but it is how we've been > running > > so > > > > > just > > > > > > wanted to include it for the sake of completeness. > > > > > > > > > > > > Good luck with your server! > > > > > > > > > > > > Danny > > > > > > > > > > > > On Wed, May 13, 2009 at 12:10 PM, FPSB | Goerge > > > > > > wrote: > > > > > > > > > > > > > alright, thanks for that! > > > > > > > > > > > > > > Still looking for kernel suggestions :) > > > > > > > > > > > > > > On Wed, May 13, 2009 at 2:21 AM, Cc2iscooL < > cc2isc...@gmail.com> > > > > > wrote: > > > > > > > > > > > > > > > Change maxrate to > > > > > > > > > > > > > > > > sv_maxrate 0 > > > > > > > > > > > > > > > > Make sure on your client you have... > > > > > > > > > > > > > > > > rate 5 (this wi
Re: [hlds_linux] TF2 Config Help?
A minrate of 100,000 doesn't necessarily mean all clients will be using 100KBps the whole time. It'll just force everyone to have rate set to at least 10. Rate 10 means send no more than 100KBps. So if there is ever a time where your server needs to send 100KBps to a client and that client has a slow DSL connection (say 512kbps or something), then yes, there will be loss. I would think that in most cases the 512kbps player with a rate of 10 will be fine. Still, I wouldn't recommend a minrate of 10. -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of Richard Eid Sent: Wednesday, May 13, 2009 4:01 PM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] TF2 Config Help? The problem, though, is that 100 doesn't exist in Source 2007 for cl_cmdrate and cl_updaterate, so those 100 settings are meaningless. And a minrate of 10 is a little rough. Unless everyone connecting to your server has at least an 800Kbps or greater download speed from their ISP, they'll have some major problems playing on your server. You're right, though. The important settings in your config are the minimums. They are far too high for a lot of people and the 66 cmdrate and updaterate minimums that it is defaulting to are also a problem. Unless people can hold 66fps on their client, they may begin to see some timeout issues. I'd leave the min values for everything at the defaults. So my config for you would look like: sv_minrate 1 sv_maxrate 0 sv_maxupdaterate 66 sv_mincmdrate 30 sv_minupdaterate 20 sv_maxcmdrate 66 Those settings are a lot more fair to the clients that will be connecting to your server(s) and will generally provide for a better overall experience. I'm actually surprised you're not seeing a lot of timeout issues and other connection related errors. -Richard Eid On Wed, May 13, 2009 at 6:06 PM, Danny Heinrichs wrote: > Just wanted to chime in with my settings. Most admins don't like to give > theirs out because it takes a lot of research (at least for me) to figure > out how to achieve no choke and no loss with srcds TF2. > > As long as your box can handle the extra bandwidth (I know you said you > have > 100mbps, but there's always other issues such as packet loss), these work > well for me: > > sv_minrate 10 > sv_maxrate 0 > sv_maxupdaterate 100 > sv_mincmdrate 100 > sv_minupdaterate 100 > sv_maxcmdrate 100 > net_splitrate 300 > net_splitpacket_maxrate 6 > > The important settings here are no the max's, but the min's, and most > importantly the minrate boost. The reason I have min rates that high is > because some clients we're having lots of issues with everyone being jumpy > because the client cmd/update rates are 20/30 by default. Far too low for > our 32 slot server. The split packet stuff doesn't have an effect on on > the > choke/loss that I have witnessed, but it is how we've been running so just > wanted to include it for the sake of completeness. > > Good luck with your server! > > Danny > > On Wed, May 13, 2009 at 12:10 PM, FPSB | Goerge > wrote: > > > alright, thanks for that! > > > > Still looking for kernel suggestions :) > > > > On Wed, May 13, 2009 at 2:21 AM, Cc2iscooL wrote: > > > > > Change maxrate to > > > > > > sv_maxrate 0 > > > > > > Make sure on your client you have... > > > > > > rate 5 (this will probably reset every time you restart the game) > > > cl_cmdrate 67 > > > cl_updaterate 67 > > > > > > Your rate is probably dropping down to your server's minimum, which is > > > 9000. > > > I don't know what kind of slots you have, but if you have a 32 slotter > > 9000 > > > is nowhere near enough bandwidth @ 45-67 update rate. > > > > > > Try a sv_minrate of 15000-2 for best effect on the server side. > > You're > > > limiting clients to a high update rate, limit them to a high rate as > well > > > to > > > improve overall satisfaction! > > > > > > On Wed, May 13, 2009 at 2:51 AM, FPSB | Goerge < > > brutalgoerge...@gmail.com > > > >wrote: > > > > > > > My server always feels a little off when I run the default kernel. > So > > I > > > > find some guides to compile it, but they all seemed geared to making > > > srcds > > > > get thousands of FPS. When I run them, it does seem smoother for the > > > most > > > > part, but it starts to hiccup. Sometimes it doesn't happen very > often, > > > > sometimes it happens so often, it's hard to play, and I rather use > the > > > > default kernel again. > > > > > > > > I've set the sv_",,.rate" cvars to all the settings i could find, > like > > i > > > > think i use currently, but they never seem to change anything. > > > > sv_maxrate 35000 > > > > sv_mincmdrate 45 > > > > sv_minupdaterate 45 > > > > sv_minrate 9000 > > > > sv_maxcmdrate 67 > > > > sv_maxupdaterate 67 > > > > > > > > I'm on centos 5.2 64 bit 2.6.18-128.1.6.el5 (default) > > > >
[hlds_linux] Killing Floor Win32 Dedicated Server files available
The Win32 version of the Killing Floor dedicated server is now available. To download the files, run hldsupdatetool, using the game name "killingfloor". A Linux version is planned for the Killing Floor dedicated server, but is not ready yet. Jason ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] TF2 Config Help?
Huh? Safe from what? 67 produces the same results as 66, so there's no reason to use it. If people complain about you using 66 instead of 67, rest easy knowing that they don't have a clue. -Richard Eid On Wed, May 13, 2009 at 8:45 PM, Cc2iscooL wrote: > Better safe than sorry, I guess! (One less thing for srs bzns players to > whine about.) > > On Wed, May 13, 2009 at 6:45 PM, Richard Eid > wrote: > > > Yeah, 67 is the new 101. Pretty much pointless, though arguments could > be > > made against that if you watch net_graph. But even at 66, you'll see > 66.x > > coming through at times. > > > >-Richard Eid > > > > > > On Wed, May 13, 2009 at 7:33 PM, Cc2iscooL wrote: > > > > > That's about what I have mine set to. I always set to 67 for maximums > > just > > > to get that possible "extra" though. Might as well be over than under. > > > > > > I'd recommend rate 15000 for a 32 slot though, at least. > > > > > > On Wed, May 13, 2009 at 6:01 PM, Richard Eid > > > wrote: > > > > > > > The problem, though, is that 100 doesn't exist in Source 2007 for > > > > cl_cmdrate > > > > and cl_updaterate, so those 100 settings are meaningless. And a > > minrate > > > of > > > > 10 is a little rough. Unless everyone connecting to your server > > has > > > at > > > > least an 800Kbps or greater download speed from their ISP, they'll > have > > > > some > > > > major problems playing on your server. > > > > > > > > You're right, though. The important settings in your config are the > > > > minimums. They are far too high for a lot of people and the 66 > cmdrate > > > and > > > > updaterate minimums that it is defaulting to are also a problem. > > Unless > > > > people can hold 66fps on their client, they may begin to see some > > timeout > > > > issues. I'd leave the min values for everything at the defaults. So > > my > > > > config for you would look like: > > > > > > > > sv_minrate 1 > > > > sv_maxrate 0 > > > > sv_maxupdaterate 66 > > > > sv_mincmdrate 30 > > > > sv_minupdaterate 20 > > > > sv_maxcmdrate 66 > > > > > > > > Those settings are a lot more fair to the clients that will be > > connecting > > > > to > > > > your server(s) and will generally provide for a better overall > > > experience. > > > > I'm actually surprised you're not seeing a lot of timeout issues and > > > other > > > > connection related errors. > > > > > > > >-Richard Eid > > > > > > > > > > > > On Wed, May 13, 2009 at 6:06 PM, Danny Heinrichs > > > wrote: > > > > > > > > > Just wanted to chime in with my settings. Most admins don't like to > > > give > > > > > theirs out because it takes a lot of research (at least for me) to > > > figure > > > > > out how to achieve no choke and no loss with srcds TF2. > > > > > > > > > > As long as your box can handle the extra bandwidth (I know you said > > you > > > > > have > > > > > 100mbps, but there's always other issues such as packet loss), > these > > > work > > > > > well for me: > > > > > > > > > > sv_minrate 10 > > > > > sv_maxrate 0 > > > > > sv_maxupdaterate 100 > > > > > sv_mincmdrate 100 > > > > > sv_minupdaterate 100 > > > > > sv_maxcmdrate 100 > > > > > net_splitrate 300 > > > > > net_splitpacket_maxrate 6 > > > > > > > > > > The important settings here are no the max's, but the min's, and > most > > > > > importantly the minrate boost. The reason I have min rates that > high > > is > > > > > because some clients we're having lots of issues with everyone > being > > > > jumpy > > > > > because the client cmd/update rates are 20/30 by default. Far too > low > > > for > > > > > our 32 slot server. The split packet stuff doesn't have an effect > on > > > on > > > > > the > > > > > choke/loss that I have witnessed, but it is how we've been running > so > > > > just > > > > > wanted to include it for the sake of completeness. > > > > > > > > > > Good luck with your server! > > > > > > > > > > Danny > > > > > > > > > > On Wed, May 13, 2009 at 12:10 PM, FPSB | Goerge > > > > > wrote: > > > > > > > > > > > alright, thanks for that! > > > > > > > > > > > > Still looking for kernel suggestions :) > > > > > > > > > > > > On Wed, May 13, 2009 at 2:21 AM, Cc2iscooL > > > > wrote: > > > > > > > > > > > > > Change maxrate to > > > > > > > > > > > > > > sv_maxrate 0 > > > > > > > > > > > > > > Make sure on your client you have... > > > > > > > > > > > > > > rate 5 (this will probably reset every time you restart the > > > game) > > > > > > > cl_cmdrate 67 > > > > > > > cl_updaterate 67 > > > > > > > > > > > > > > Your rate is probably dropping down to your server's minimum, > > which > > > > is > > > > > > > 9000. > > > > > > > I don't know what kind of slots you have, but if you have a 32 > > > > slotter > > > > > > 9000 > > > > > > > is nowhere near enough bandwidth @ 45-67 update rate. > > > > > > > > > > > > >
Re: [hlds_linux] TF2 Config Help?
Better safe than sorry, I guess! (One less thing for srs bzns players to whine about.) On Wed, May 13, 2009 at 6:45 PM, Richard Eid wrote: > Yeah, 67 is the new 101. Pretty much pointless, though arguments could be > made against that if you watch net_graph. But even at 66, you'll see 66.x > coming through at times. > >-Richard Eid > > > On Wed, May 13, 2009 at 7:33 PM, Cc2iscooL wrote: > > > That's about what I have mine set to. I always set to 67 for maximums > just > > to get that possible "extra" though. Might as well be over than under. > > > > I'd recommend rate 15000 for a 32 slot though, at least. > > > > On Wed, May 13, 2009 at 6:01 PM, Richard Eid > > wrote: > > > > > The problem, though, is that 100 doesn't exist in Source 2007 for > > > cl_cmdrate > > > and cl_updaterate, so those 100 settings are meaningless. And a > minrate > > of > > > 10 is a little rough. Unless everyone connecting to your server > has > > at > > > least an 800Kbps or greater download speed from their ISP, they'll have > > > some > > > major problems playing on your server. > > > > > > You're right, though. The important settings in your config are the > > > minimums. They are far too high for a lot of people and the 66 cmdrate > > and > > > updaterate minimums that it is defaulting to are also a problem. > Unless > > > people can hold 66fps on their client, they may begin to see some > timeout > > > issues. I'd leave the min values for everything at the defaults. So > my > > > config for you would look like: > > > > > > sv_minrate 1 > > > sv_maxrate 0 > > > sv_maxupdaterate 66 > > > sv_mincmdrate 30 > > > sv_minupdaterate 20 > > > sv_maxcmdrate 66 > > > > > > Those settings are a lot more fair to the clients that will be > connecting > > > to > > > your server(s) and will generally provide for a better overall > > experience. > > > I'm actually surprised you're not seeing a lot of timeout issues and > > other > > > connection related errors. > > > > > >-Richard Eid > > > > > > > > > On Wed, May 13, 2009 at 6:06 PM, Danny Heinrichs > > wrote: > > > > > > > Just wanted to chime in with my settings. Most admins don't like to > > give > > > > theirs out because it takes a lot of research (at least for me) to > > figure > > > > out how to achieve no choke and no loss with srcds TF2. > > > > > > > > As long as your box can handle the extra bandwidth (I know you said > you > > > > have > > > > 100mbps, but there's always other issues such as packet loss), these > > work > > > > well for me: > > > > > > > > sv_minrate 10 > > > > sv_maxrate 0 > > > > sv_maxupdaterate 100 > > > > sv_mincmdrate 100 > > > > sv_minupdaterate 100 > > > > sv_maxcmdrate 100 > > > > net_splitrate 300 > > > > net_splitpacket_maxrate 6 > > > > > > > > The important settings here are no the max's, but the min's, and most > > > > importantly the minrate boost. The reason I have min rates that high > is > > > > because some clients we're having lots of issues with everyone being > > > jumpy > > > > because the client cmd/update rates are 20/30 by default. Far too low > > for > > > > our 32 slot server. The split packet stuff doesn't have an effect on > > on > > > > the > > > > choke/loss that I have witnessed, but it is how we've been running so > > > just > > > > wanted to include it for the sake of completeness. > > > > > > > > Good luck with your server! > > > > > > > > Danny > > > > > > > > On Wed, May 13, 2009 at 12:10 PM, FPSB | Goerge > > > > wrote: > > > > > > > > > alright, thanks for that! > > > > > > > > > > Still looking for kernel suggestions :) > > > > > > > > > > On Wed, May 13, 2009 at 2:21 AM, Cc2iscooL > > > wrote: > > > > > > > > > > > Change maxrate to > > > > > > > > > > > > sv_maxrate 0 > > > > > > > > > > > > Make sure on your client you have... > > > > > > > > > > > > rate 5 (this will probably reset every time you restart the > > game) > > > > > > cl_cmdrate 67 > > > > > > cl_updaterate 67 > > > > > > > > > > > > Your rate is probably dropping down to your server's minimum, > which > > > is > > > > > > 9000. > > > > > > I don't know what kind of slots you have, but if you have a 32 > > > slotter > > > > > 9000 > > > > > > is nowhere near enough bandwidth @ 45-67 update rate. > > > > > > > > > > > > Try a sv_minrate of 15000-2 for best effect on the server > side. > > > > > You're > > > > > > limiting clients to a high update rate, limit them to a high rate > > as > > > > well > > > > > > to > > > > > > improve overall satisfaction! > > > > > > > > > > > > On Wed, May 13, 2009 at 2:51 AM, FPSB | Goerge < > > > > > brutalgoerge...@gmail.com > > > > > > >wrote: > > > > > > > > > > > > > My server always feels a little off when I run the default > > kernel. > > > > So > > > > > I > > > > > > > find some guides to compile it, but they all seemed geared to > > > making > > > > > > srcds > > > > > >
Re: [hlds_linux] TF2 Config Help?
Yeah, 67 is the new 101. Pretty much pointless, though arguments could be made against that if you watch net_graph. But even at 66, you'll see 66.x coming through at times. -Richard Eid On Wed, May 13, 2009 at 7:33 PM, Cc2iscooL wrote: > That's about what I have mine set to. I always set to 67 for maximums just > to get that possible "extra" though. Might as well be over than under. > > I'd recommend rate 15000 for a 32 slot though, at least. > > On Wed, May 13, 2009 at 6:01 PM, Richard Eid > wrote: > > > The problem, though, is that 100 doesn't exist in Source 2007 for > > cl_cmdrate > > and cl_updaterate, so those 100 settings are meaningless. And a minrate > of > > 10 is a little rough. Unless everyone connecting to your server has > at > > least an 800Kbps or greater download speed from their ISP, they'll have > > some > > major problems playing on your server. > > > > You're right, though. The important settings in your config are the > > minimums. They are far too high for a lot of people and the 66 cmdrate > and > > updaterate minimums that it is defaulting to are also a problem. Unless > > people can hold 66fps on their client, they may begin to see some timeout > > issues. I'd leave the min values for everything at the defaults. So my > > config for you would look like: > > > > sv_minrate 1 > > sv_maxrate 0 > > sv_maxupdaterate 66 > > sv_mincmdrate 30 > > sv_minupdaterate 20 > > sv_maxcmdrate 66 > > > > Those settings are a lot more fair to the clients that will be connecting > > to > > your server(s) and will generally provide for a better overall > experience. > > I'm actually surprised you're not seeing a lot of timeout issues and > other > > connection related errors. > > > >-Richard Eid > > > > > > On Wed, May 13, 2009 at 6:06 PM, Danny Heinrichs > wrote: > > > > > Just wanted to chime in with my settings. Most admins don't like to > give > > > theirs out because it takes a lot of research (at least for me) to > figure > > > out how to achieve no choke and no loss with srcds TF2. > > > > > > As long as your box can handle the extra bandwidth (I know you said you > > > have > > > 100mbps, but there's always other issues such as packet loss), these > work > > > well for me: > > > > > > sv_minrate 10 > > > sv_maxrate 0 > > > sv_maxupdaterate 100 > > > sv_mincmdrate 100 > > > sv_minupdaterate 100 > > > sv_maxcmdrate 100 > > > net_splitrate 300 > > > net_splitpacket_maxrate 6 > > > > > > The important settings here are no the max's, but the min's, and most > > > importantly the minrate boost. The reason I have min rates that high is > > > because some clients we're having lots of issues with everyone being > > jumpy > > > because the client cmd/update rates are 20/30 by default. Far too low > for > > > our 32 slot server. The split packet stuff doesn't have an effect on > on > > > the > > > choke/loss that I have witnessed, but it is how we've been running so > > just > > > wanted to include it for the sake of completeness. > > > > > > Good luck with your server! > > > > > > Danny > > > > > > On Wed, May 13, 2009 at 12:10 PM, FPSB | Goerge > > > wrote: > > > > > > > alright, thanks for that! > > > > > > > > Still looking for kernel suggestions :) > > > > > > > > On Wed, May 13, 2009 at 2:21 AM, Cc2iscooL > > wrote: > > > > > > > > > Change maxrate to > > > > > > > > > > sv_maxrate 0 > > > > > > > > > > Make sure on your client you have... > > > > > > > > > > rate 5 (this will probably reset every time you restart the > game) > > > > > cl_cmdrate 67 > > > > > cl_updaterate 67 > > > > > > > > > > Your rate is probably dropping down to your server's minimum, which > > is > > > > > 9000. > > > > > I don't know what kind of slots you have, but if you have a 32 > > slotter > > > > 9000 > > > > > is nowhere near enough bandwidth @ 45-67 update rate. > > > > > > > > > > Try a sv_minrate of 15000-2 for best effect on the server side. > > > > You're > > > > > limiting clients to a high update rate, limit them to a high rate > as > > > well > > > > > to > > > > > improve overall satisfaction! > > > > > > > > > > On Wed, May 13, 2009 at 2:51 AM, FPSB | Goerge < > > > > brutalgoerge...@gmail.com > > > > > >wrote: > > > > > > > > > > > My server always feels a little off when I run the default > kernel. > > > So > > > > I > > > > > > find some guides to compile it, but they all seemed geared to > > making > > > > > srcds > > > > > > get thousands of FPS. When I run them, it does seem smoother for > > the > > > > > most > > > > > > part, but it starts to hiccup. Sometimes it doesn't happen very > > > often, > > > > > > sometimes it happens so often, it's hard to play, and I rather > use > > > the > > > > > > default kernel again. > > > > > > > > > > > > I've set the sv_",,.rate" cvars to all the settings i could find, > > > like > > > > i > > > > > > think i use cur
Re: [hlds_linux] TF2 Config Help?
That's about what I have mine set to. I always set to 67 for maximums just to get that possible "extra" though. Might as well be over than under. I'd recommend rate 15000 for a 32 slot though, at least. On Wed, May 13, 2009 at 6:01 PM, Richard Eid wrote: > The problem, though, is that 100 doesn't exist in Source 2007 for > cl_cmdrate > and cl_updaterate, so those 100 settings are meaningless. And a minrate of > 10 is a little rough. Unless everyone connecting to your server has at > least an 800Kbps or greater download speed from their ISP, they'll have > some > major problems playing on your server. > > You're right, though. The important settings in your config are the > minimums. They are far too high for a lot of people and the 66 cmdrate and > updaterate minimums that it is defaulting to are also a problem. Unless > people can hold 66fps on their client, they may begin to see some timeout > issues. I'd leave the min values for everything at the defaults. So my > config for you would look like: > > sv_minrate 1 > sv_maxrate 0 > sv_maxupdaterate 66 > sv_mincmdrate 30 > sv_minupdaterate 20 > sv_maxcmdrate 66 > > Those settings are a lot more fair to the clients that will be connecting > to > your server(s) and will generally provide for a better overall experience. > I'm actually surprised you're not seeing a lot of timeout issues and other > connection related errors. > >-Richard Eid > > > On Wed, May 13, 2009 at 6:06 PM, Danny Heinrichs wrote: > > > Just wanted to chime in with my settings. Most admins don't like to give > > theirs out because it takes a lot of research (at least for me) to figure > > out how to achieve no choke and no loss with srcds TF2. > > > > As long as your box can handle the extra bandwidth (I know you said you > > have > > 100mbps, but there's always other issues such as packet loss), these work > > well for me: > > > > sv_minrate 10 > > sv_maxrate 0 > > sv_maxupdaterate 100 > > sv_mincmdrate 100 > > sv_minupdaterate 100 > > sv_maxcmdrate 100 > > net_splitrate 300 > > net_splitpacket_maxrate 6 > > > > The important settings here are no the max's, but the min's, and most > > importantly the minrate boost. The reason I have min rates that high is > > because some clients we're having lots of issues with everyone being > jumpy > > because the client cmd/update rates are 20/30 by default. Far too low for > > our 32 slot server. The split packet stuff doesn't have an effect on on > > the > > choke/loss that I have witnessed, but it is how we've been running so > just > > wanted to include it for the sake of completeness. > > > > Good luck with your server! > > > > Danny > > > > On Wed, May 13, 2009 at 12:10 PM, FPSB | Goerge > > wrote: > > > > > alright, thanks for that! > > > > > > Still looking for kernel suggestions :) > > > > > > On Wed, May 13, 2009 at 2:21 AM, Cc2iscooL > wrote: > > > > > > > Change maxrate to > > > > > > > > sv_maxrate 0 > > > > > > > > Make sure on your client you have... > > > > > > > > rate 5 (this will probably reset every time you restart the game) > > > > cl_cmdrate 67 > > > > cl_updaterate 67 > > > > > > > > Your rate is probably dropping down to your server's minimum, which > is > > > > 9000. > > > > I don't know what kind of slots you have, but if you have a 32 > slotter > > > 9000 > > > > is nowhere near enough bandwidth @ 45-67 update rate. > > > > > > > > Try a sv_minrate of 15000-2 for best effect on the server side. > > > You're > > > > limiting clients to a high update rate, limit them to a high rate as > > well > > > > to > > > > improve overall satisfaction! > > > > > > > > On Wed, May 13, 2009 at 2:51 AM, FPSB | Goerge < > > > brutalgoerge...@gmail.com > > > > >wrote: > > > > > > > > > My server always feels a little off when I run the default kernel. > > So > > > I > > > > > find some guides to compile it, but they all seemed geared to > making > > > > srcds > > > > > get thousands of FPS. When I run them, it does seem smoother for > the > > > > most > > > > > part, but it starts to hiccup. Sometimes it doesn't happen very > > often, > > > > > sometimes it happens so often, it's hard to play, and I rather use > > the > > > > > default kernel again. > > > > > > > > > > I've set the sv_",,.rate" cvars to all the settings i could find, > > like > > > i > > > > > think i use currently, but they never seem to change anything. > > > > > sv_maxrate 35000 > > > > > sv_mincmdrate 45 > > > > > sv_minupdaterate 45 > > > > > sv_minrate 9000 > > > > > sv_maxcmdrate 67 > > > > > sv_maxupdaterate 67 > > > > > > > > > > I'm on centos 5.2 64 bit 2.6.18-128.1.6.el5 (default) > > > > > > > > > > I've tried 2.6.28 with RT patch/ no RT patch > > > > > max preempt > > > > > everything between 100 and 1000Hz > > > > > tickless enabled and disabled > > > > > > > > > > chrt on the srcds process > > > > > > > > > > I really don't care what the server FPS is, as long as it's
Re: [hlds_linux] TF2 Config Help?
The problem, though, is that 100 doesn't exist in Source 2007 for cl_cmdrate and cl_updaterate, so those 100 settings are meaningless. And a minrate of 10 is a little rough. Unless everyone connecting to your server has at least an 800Kbps or greater download speed from their ISP, they'll have some major problems playing on your server. You're right, though. The important settings in your config are the minimums. They are far too high for a lot of people and the 66 cmdrate and updaterate minimums that it is defaulting to are also a problem. Unless people can hold 66fps on their client, they may begin to see some timeout issues. I'd leave the min values for everything at the defaults. So my config for you would look like: sv_minrate 1 sv_maxrate 0 sv_maxupdaterate 66 sv_mincmdrate 30 sv_minupdaterate 20 sv_maxcmdrate 66 Those settings are a lot more fair to the clients that will be connecting to your server(s) and will generally provide for a better overall experience. I'm actually surprised you're not seeing a lot of timeout issues and other connection related errors. -Richard Eid On Wed, May 13, 2009 at 6:06 PM, Danny Heinrichs wrote: > Just wanted to chime in with my settings. Most admins don't like to give > theirs out because it takes a lot of research (at least for me) to figure > out how to achieve no choke and no loss with srcds TF2. > > As long as your box can handle the extra bandwidth (I know you said you > have > 100mbps, but there's always other issues such as packet loss), these work > well for me: > > sv_minrate 10 > sv_maxrate 0 > sv_maxupdaterate 100 > sv_mincmdrate 100 > sv_minupdaterate 100 > sv_maxcmdrate 100 > net_splitrate 300 > net_splitpacket_maxrate 6 > > The important settings here are no the max's, but the min's, and most > importantly the minrate boost. The reason I have min rates that high is > because some clients we're having lots of issues with everyone being jumpy > because the client cmd/update rates are 20/30 by default. Far too low for > our 32 slot server. The split packet stuff doesn't have an effect on on > the > choke/loss that I have witnessed, but it is how we've been running so just > wanted to include it for the sake of completeness. > > Good luck with your server! > > Danny > > On Wed, May 13, 2009 at 12:10 PM, FPSB | Goerge > wrote: > > > alright, thanks for that! > > > > Still looking for kernel suggestions :) > > > > On Wed, May 13, 2009 at 2:21 AM, Cc2iscooL wrote: > > > > > Change maxrate to > > > > > > sv_maxrate 0 > > > > > > Make sure on your client you have... > > > > > > rate 5 (this will probably reset every time you restart the game) > > > cl_cmdrate 67 > > > cl_updaterate 67 > > > > > > Your rate is probably dropping down to your server's minimum, which is > > > 9000. > > > I don't know what kind of slots you have, but if you have a 32 slotter > > 9000 > > > is nowhere near enough bandwidth @ 45-67 update rate. > > > > > > Try a sv_minrate of 15000-2 for best effect on the server side. > > You're > > > limiting clients to a high update rate, limit them to a high rate as > well > > > to > > > improve overall satisfaction! > > > > > > On Wed, May 13, 2009 at 2:51 AM, FPSB | Goerge < > > brutalgoerge...@gmail.com > > > >wrote: > > > > > > > My server always feels a little off when I run the default kernel. > So > > I > > > > find some guides to compile it, but they all seemed geared to making > > > srcds > > > > get thousands of FPS. When I run them, it does seem smoother for the > > > most > > > > part, but it starts to hiccup. Sometimes it doesn't happen very > often, > > > > sometimes it happens so often, it's hard to play, and I rather use > the > > > > default kernel again. > > > > > > > > I've set the sv_",,.rate" cvars to all the settings i could find, > like > > i > > > > think i use currently, but they never seem to change anything. > > > > sv_maxrate 35000 > > > > sv_mincmdrate 45 > > > > sv_minupdaterate 45 > > > > sv_minrate 9000 > > > > sv_maxcmdrate 67 > > > > sv_maxupdaterate 67 > > > > > > > > I'm on centos 5.2 64 bit 2.6.18-128.1.6.el5 (default) > > > > > > > > I've tried 2.6.28 with RT patch/ no RT patch > > > > max preempt > > > > everything between 100 and 1000Hz > > > > tickless enabled and disabled > > > > > > > > chrt on the srcds process > > > > > > > > I really don't care what the server FPS is, as long as it's smooth in > > > game. > > > > Like I said, these 'high fps' kernel settings kinda help, but they > have > > > bad > > > > stuttering. > > > > > > > > Basic Server specs = > > > > Intel Q9440 > > > > 4g ram > > > > Linux Centos 5.2 > > > > 100 mb/s transer rate > > > > Max Load EVER 50% > > > > > > > > I am wondering if there are any suggestions to smooth out gameplay? > I > > go > > > > to > > > > other linux servers, and they use slightly weaker processors, like > > q6600, > > > > and it feels much a ton smoother than mine. >
Re: [hlds_linux] TF2 Config Help?
ummm anyone with DSL play on your servers? On Wed, May 13, 2009 at 3:06 PM, Danny Heinrichs wrote: > Just wanted to chime in with my settings. Most admins don't like to give > theirs out because it takes a lot of research (at least for me) to figure > out how to achieve no choke and no loss with srcds TF2. > > As long as your box can handle the extra bandwidth (I know you said you > have > 100mbps, but there's always other issues such as packet loss), these work > well for me: > > sv_minrate 10 > sv_maxrate 0 > sv_maxupdaterate 100 > sv_mincmdrate 100 > sv_minupdaterate 100 > sv_maxcmdrate 100 > net_splitrate 300 > net_splitpacket_maxrate 6 > > The important settings here are no the max's, but the min's, and most > importantly the minrate boost. The reason I have min rates that high is > because some clients we're having lots of issues with everyone being jumpy > because the client cmd/update rates are 20/30 by default. Far too low for > our 32 slot server. The split packet stuff doesn't have an effect on on > the > choke/loss that I have witnessed, but it is how we've been running so just > wanted to include it for the sake of completeness. > > Good luck with your server! > > Danny > > On Wed, May 13, 2009 at 12:10 PM, FPSB | Goerge > wrote: > > > alright, thanks for that! > > > > Still looking for kernel suggestions :) > > > > On Wed, May 13, 2009 at 2:21 AM, Cc2iscooL wrote: > > > > > Change maxrate to > > > > > > sv_maxrate 0 > > > > > > Make sure on your client you have... > > > > > > rate 5 (this will probably reset every time you restart the game) > > > cl_cmdrate 67 > > > cl_updaterate 67 > > > > > > Your rate is probably dropping down to your server's minimum, which is > > > 9000. > > > I don't know what kind of slots you have, but if you have a 32 slotter > > 9000 > > > is nowhere near enough bandwidth @ 45-67 update rate. > > > > > > Try a sv_minrate of 15000-2 for best effect on the server side. > > You're > > > limiting clients to a high update rate, limit them to a high rate as > well > > > to > > > improve overall satisfaction! > > > > > > On Wed, May 13, 2009 at 2:51 AM, FPSB | Goerge < > > brutalgoerge...@gmail.com > > > >wrote: > > > > > > > My server always feels a little off when I run the default kernel. > So > > I > > > > find some guides to compile it, but they all seemed geared to making > > > srcds > > > > get thousands of FPS. When I run them, it does seem smoother for the > > > most > > > > part, but it starts to hiccup. Sometimes it doesn't happen very > often, > > > > sometimes it happens so often, it's hard to play, and I rather use > the > > > > default kernel again. > > > > > > > > I've set the sv_",,.rate" cvars to all the settings i could find, > like > > i > > > > think i use currently, but they never seem to change anything. > > > > sv_maxrate 35000 > > > > sv_mincmdrate 45 > > > > sv_minupdaterate 45 > > > > sv_minrate 9000 > > > > sv_maxcmdrate 67 > > > > sv_maxupdaterate 67 > > > > > > > > I'm on centos 5.2 64 bit 2.6.18-128.1.6.el5 (default) > > > > > > > > I've tried 2.6.28 with RT patch/ no RT patch > > > > max preempt > > > > everything between 100 and 1000Hz > > > > tickless enabled and disabled > > > > > > > > chrt on the srcds process > > > > > > > > I really don't care what the server FPS is, as long as it's smooth in > > > game. > > > > Like I said, these 'high fps' kernel settings kinda help, but they > have > > > bad > > > > stuttering. > > > > > > > > Basic Server specs = > > > > Intel Q9440 > > > > 4g ram > > > > Linux Centos 5.2 > > > > 100 mb/s transer rate > > > > Max Load EVER 50% > > > > > > > > I am wondering if there are any suggestions to smooth out gameplay? > I > > go > > > > to > > > > other linux servers, and they use slightly weaker processors, like > > q6600, > > > > and it feels much a ton smoother than mine. > > > > > > > > Both linux kernel settings, and source engine settings (rates and > junk) > > > > > > > > I'm tired of guessing with these kernel settings, takes too long to > > > change > > > > setting, compile, reboot, test. :) > > > > ___ > > > > To unsubscribe, edit your list preferences, or view the list > archives, > > > > please visit: > > > > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > > > > > > > > > > > > > > > -- > > > Cc2iscooL > > > Head Admin/Owner > > > http://www.cc2iscool.com > > > ___ > > > To unsubscribe, edit your list preferences, or view the list archives, > > > please visit: > > > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > > > > ___ > > To unsubscribe, edit your list preferences, or view the list archives, > > please visit: > > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visi
Re: [hlds_linux] TF2 Config Help?
Just wanted to chime in with my settings. Most admins don't like to give theirs out because it takes a lot of research (at least for me) to figure out how to achieve no choke and no loss with srcds TF2. As long as your box can handle the extra bandwidth (I know you said you have 100mbps, but there's always other issues such as packet loss), these work well for me: sv_minrate 10 sv_maxrate 0 sv_maxupdaterate 100 sv_mincmdrate 100 sv_minupdaterate 100 sv_maxcmdrate 100 net_splitrate 300 net_splitpacket_maxrate 6 The important settings here are no the max's, but the min's, and most importantly the minrate boost. The reason I have min rates that high is because some clients we're having lots of issues with everyone being jumpy because the client cmd/update rates are 20/30 by default. Far too low for our 32 slot server. The split packet stuff doesn't have an effect on on the choke/loss that I have witnessed, but it is how we've been running so just wanted to include it for the sake of completeness. Good luck with your server! Danny On Wed, May 13, 2009 at 12:10 PM, FPSB | Goerge wrote: > alright, thanks for that! > > Still looking for kernel suggestions :) > > On Wed, May 13, 2009 at 2:21 AM, Cc2iscooL wrote: > > > Change maxrate to > > > > sv_maxrate 0 > > > > Make sure on your client you have... > > > > rate 5 (this will probably reset every time you restart the game) > > cl_cmdrate 67 > > cl_updaterate 67 > > > > Your rate is probably dropping down to your server's minimum, which is > > 9000. > > I don't know what kind of slots you have, but if you have a 32 slotter > 9000 > > is nowhere near enough bandwidth @ 45-67 update rate. > > > > Try a sv_minrate of 15000-2 for best effect on the server side. > You're > > limiting clients to a high update rate, limit them to a high rate as well > > to > > improve overall satisfaction! > > > > On Wed, May 13, 2009 at 2:51 AM, FPSB | Goerge < > brutalgoerge...@gmail.com > > >wrote: > > > > > My server always feels a little off when I run the default kernel. So > I > > > find some guides to compile it, but they all seemed geared to making > > srcds > > > get thousands of FPS. When I run them, it does seem smoother for the > > most > > > part, but it starts to hiccup. Sometimes it doesn't happen very often, > > > sometimes it happens so often, it's hard to play, and I rather use the > > > default kernel again. > > > > > > I've set the sv_",,.rate" cvars to all the settings i could find, like > i > > > think i use currently, but they never seem to change anything. > > > sv_maxrate 35000 > > > sv_mincmdrate 45 > > > sv_minupdaterate 45 > > > sv_minrate 9000 > > > sv_maxcmdrate 67 > > > sv_maxupdaterate 67 > > > > > > I'm on centos 5.2 64 bit 2.6.18-128.1.6.el5 (default) > > > > > > I've tried 2.6.28 with RT patch/ no RT patch > > > max preempt > > > everything between 100 and 1000Hz > > > tickless enabled and disabled > > > > > > chrt on the srcds process > > > > > > I really don't care what the server FPS is, as long as it's smooth in > > game. > > > Like I said, these 'high fps' kernel settings kinda help, but they have > > bad > > > stuttering. > > > > > > Basic Server specs = > > > Intel Q9440 > > > 4g ram > > > Linux Centos 5.2 > > > 100 mb/s transer rate > > > Max Load EVER 50% > > > > > > I am wondering if there are any suggestions to smooth out gameplay? I > go > > > to > > > other linux servers, and they use slightly weaker processors, like > q6600, > > > and it feels much a ton smoother than mine. > > > > > > Both linux kernel settings, and source engine settings (rates and junk) > > > > > > I'm tired of guessing with these kernel settings, takes too long to > > change > > > setting, compile, reboot, test. :) > > > ___ > > > To unsubscribe, edit your list preferences, or view the list archives, > > > please visit: > > > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > > > > > > > > > > -- > > Cc2iscooL > > Head Admin/Owner > > http://www.cc2iscool.com > > ___ > > To unsubscribe, edit your list preferences, or view the list archives, > > please visit: > > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Killing Floor Dedicated Server
Actually Well yeah, but Steam is going to be selling it, which may have prompted the OP's thinking it would get support from this list. Even though it won't obviously. -mauirixxx -Original Message- From: hlds_linux-boun...@list.valvesoftware.com [mailto:hlds_linux-boun...@list.valvesoftware.com] On Behalf Of ash-...@quickfox.org Sent: Wednesday, May 13, 2009 10:03 AM To: Half-Life dedicated Linux server mailing list Subject: Re: [hlds_linux] Killing Floor Dedicated Server Andrey Egorov wrote: > Killing Floor will relase tomorrow. I think, it good idea will relase > Killing Floor dedicated server earlier. Hey, Tripware, you plan will > relase dedicated server? I'm pretty sure that Killing Floor is based on Unreal technology, not Source. Wrong mailing list. ~Ash-Fox ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Killing Floor Dedicated Server
isn't killing floor based on unreal engine? Andrey Egorov escribió: > Hi, > > Killing Floor will relase tomorrow. I think, it good idea will relase > Killing Floor dedicated server earlier. Hey, Tripware, you plan will > relase dedicated server? > > Andrey. > > > ___ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] Killing Floor Dedicated Server
Andrey Egorov wrote: > Killing Floor will relase tomorrow. I think, it good idea will relase > Killing Floor dedicated server earlier. Hey, Tripware, you plan will > relase dedicated server? I'm pretty sure that Killing Floor is based on Unreal technology, not Source. Wrong mailing list. ~Ash-Fox ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
[hlds_linux] Killing Floor Dedicated Server
Hi, Killing Floor will relase tomorrow. I think, it good idea will relase Killing Floor dedicated server earlier. Hey, Tripware, you plan will relase dedicated server? Andrey. ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] TF2 Config Help?
alright, thanks for that! Still looking for kernel suggestions :) On Wed, May 13, 2009 at 2:21 AM, Cc2iscooL wrote: > Change maxrate to > > sv_maxrate 0 > > Make sure on your client you have... > > rate 5 (this will probably reset every time you restart the game) > cl_cmdrate 67 > cl_updaterate 67 > > Your rate is probably dropping down to your server's minimum, which is > 9000. > I don't know what kind of slots you have, but if you have a 32 slotter 9000 > is nowhere near enough bandwidth @ 45-67 update rate. > > Try a sv_minrate of 15000-2 for best effect on the server side. You're > limiting clients to a high update rate, limit them to a high rate as well > to > improve overall satisfaction! > > On Wed, May 13, 2009 at 2:51 AM, FPSB | Goerge >wrote: > > > My server always feels a little off when I run the default kernel. So I > > find some guides to compile it, but they all seemed geared to making > srcds > > get thousands of FPS. When I run them, it does seem smoother for the > most > > part, but it starts to hiccup. Sometimes it doesn't happen very often, > > sometimes it happens so often, it's hard to play, and I rather use the > > default kernel again. > > > > I've set the sv_",,.rate" cvars to all the settings i could find, like i > > think i use currently, but they never seem to change anything. > > sv_maxrate 35000 > > sv_mincmdrate 45 > > sv_minupdaterate 45 > > sv_minrate 9000 > > sv_maxcmdrate 67 > > sv_maxupdaterate 67 > > > > I'm on centos 5.2 64 bit 2.6.18-128.1.6.el5 (default) > > > > I've tried 2.6.28 with RT patch/ no RT patch > > max preempt > > everything between 100 and 1000Hz > > tickless enabled and disabled > > > > chrt on the srcds process > > > > I really don't care what the server FPS is, as long as it's smooth in > game. > > Like I said, these 'high fps' kernel settings kinda help, but they have > bad > > stuttering. > > > > Basic Server specs = > > Intel Q9440 > > 4g ram > > Linux Centos 5.2 > > 100 mb/s transer rate > > Max Load EVER 50% > > > > I am wondering if there are any suggestions to smooth out gameplay? I go > > to > > other linux servers, and they use slightly weaker processors, like q6600, > > and it feels much a ton smoother than mine. > > > > Both linux kernel settings, and source engine settings (rates and junk) > > > > I'm tired of guessing with these kernel settings, takes too long to > change > > setting, compile, reboot, test. :) > > ___ > > To unsubscribe, edit your list preferences, or view the list archives, > > please visit: > > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > > > > > > -- > Cc2iscooL > Head Admin/Owner > http://www.cc2iscool.com > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
Re: [hlds_linux] TF2 Config Help?
Change maxrate to sv_maxrate 0 Make sure on your client you have... rate 5 (this will probably reset every time you restart the game) cl_cmdrate 67 cl_updaterate 67 Your rate is probably dropping down to your server's minimum, which is 9000. I don't know what kind of slots you have, but if you have a 32 slotter 9000 is nowhere near enough bandwidth @ 45-67 update rate. Try a sv_minrate of 15000-2 for best effect on the server side. You're limiting clients to a high update rate, limit them to a high rate as well to improve overall satisfaction! On Wed, May 13, 2009 at 2:51 AM, FPSB | Goerge wrote: > My server always feels a little off when I run the default kernel. So I > find some guides to compile it, but they all seemed geared to making srcds > get thousands of FPS. When I run them, it does seem smoother for the most > part, but it starts to hiccup. Sometimes it doesn't happen very often, > sometimes it happens so often, it's hard to play, and I rather use the > default kernel again. > > I've set the sv_",,.rate" cvars to all the settings i could find, like i > think i use currently, but they never seem to change anything. > sv_maxrate 35000 > sv_mincmdrate 45 > sv_minupdaterate 45 > sv_minrate 9000 > sv_maxcmdrate 67 > sv_maxupdaterate 67 > > I'm on centos 5.2 64 bit 2.6.18-128.1.6.el5 (default) > > I've tried 2.6.28 with RT patch/ no RT patch > max preempt > everything between 100 and 1000Hz > tickless enabled and disabled > > chrt on the srcds process > > I really don't care what the server FPS is, as long as it's smooth in game. > Like I said, these 'high fps' kernel settings kinda help, but they have bad > stuttering. > > Basic Server specs = > Intel Q9440 > 4g ram > Linux Centos 5.2 > 100 mb/s transer rate > Max Load EVER 50% > > I am wondering if there are any suggestions to smooth out gameplay? I go > to > other linux servers, and they use slightly weaker processors, like q6600, > and it feels much a ton smoother than mine. > > Both linux kernel settings, and source engine settings (rates and junk) > > I'm tired of guessing with these kernel settings, takes too long to change > setting, compile, reboot, test. :) > ___ > To unsubscribe, edit your list preferences, or view the list archives, > please visit: > http://list.valvesoftware.com/mailman/listinfo/hlds_linux > -- Cc2iscooL Head Admin/Owner http://www.cc2iscool.com ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
[hlds_linux] TF2 Config Help?
My server always feels a little off when I run the default kernel. So I find some guides to compile it, but they all seemed geared to making srcds get thousands of FPS. When I run them, it does seem smoother for the most part, but it starts to hiccup. Sometimes it doesn't happen very often, sometimes it happens so often, it's hard to play, and I rather use the default kernel again. I've set the sv_",,.rate" cvars to all the settings i could find, like i think i use currently, but they never seem to change anything. sv_maxrate 35000 sv_mincmdrate 45 sv_minupdaterate 45 sv_minrate 9000 sv_maxcmdrate 67 sv_maxupdaterate 67 I'm on centos 5.2 64 bit 2.6.18-128.1.6.el5 (default) I've tried 2.6.28 with RT patch/ no RT patch max preempt everything between 100 and 1000Hz tickless enabled and disabled chrt on the srcds process I really don't care what the server FPS is, as long as it's smooth in game. Like I said, these 'high fps' kernel settings kinda help, but they have bad stuttering. Basic Server specs = Intel Q9440 4g ram Linux Centos 5.2 100 mb/s transer rate Max Load EVER 50% I am wondering if there are any suggestions to smooth out gameplay? I go to other linux servers, and they use slightly weaker processors, like q6600, and it feels much a ton smoother than mine. Both linux kernel settings, and source engine settings (rates and junk) I'm tired of guessing with these kernel settings, takes too long to change setting, compile, reboot, test. :) ___ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
