ETTV Public beta 9
Moderators: Forum moderators, developers
ETTV Public beta 9
ETTV is now available for public beta testing.
Download it here.
Documentation is here.
New:
tv_noreinforcetime (default 0, disabled) - don't show reinforcement times to spectators
signals sent to server which would normally cause it to silently shutdown are now verbosely logged (linux only).
watchdog timer now defaults to 70 seconds (to prevent it tripping before com_watchdog default of 60 seconds).
zinx's new packet reassembly code, ettv should now handle poor links much better (eg links which send udp packets out of order)
Bugfixes
ping calculation is now fixed.
gamestate is sent throttled to slaves to prevent network flooding on poor links
various demo playback crashes fixed (eg playing same demo repeatedly)
in some cases, slaves could get corrupted on map changes. fixed.
don't send etpro-specific messages to non-etpro clients (eg, should fix etpub)
Download it here.
Documentation is here.
New:
tv_noreinforcetime (default 0, disabled) - don't show reinforcement times to spectators
signals sent to server which would normally cause it to silently shutdown are now verbosely logged (linux only).
watchdog timer now defaults to 70 seconds (to prevent it tripping before com_watchdog default of 60 seconds).
zinx's new packet reassembly code, ettv should now handle poor links much better (eg links which send udp packets out of order)
Bugfixes
ping calculation is now fixed.
gamestate is sent throttled to slaves to prevent network flooding on poor links
various demo playback crashes fixed (eg playing same demo repeatedly)
in some cases, slaves could get corrupted on map changes. fixed.
don't send etpro-specific messages to non-etpro clients (eg, should fix etpub)
Last edited by bani on Sat Jul 22, 2006 6:42 pm, edited 1 time in total.
There's not really any way to avoid flooding clients off during ff...
ET sends reliable commands during ff (it has to to keep stuff synced)
Reliable commands must be acknowledged, and you can only have 256 of them in-transit (sent, but unacknowledged).
ET sends reliable commands during ff (it has to to keep stuff synced)
Reliable commands must be acknowledged, and you can only have 256 of them in-transit (sent, but unacknowledged).
Zinx Verituse http://zinx.xmms.org/
Hmm CPU utilisation is problematic. Can it be that b9 is optimised for PIV and doesn't scale well on Athlon64?
We have a server with a PIV 2.8 1 GB ram and one with an Athlon64 3000+ 1 GB RAM and the Athlon chokes much more on ettv then the PIV. PIV handles 75 slots easily, Athlon chokes on 50.
What can we do to further optimise our OSs for ETTV then?
We have a server with a PIV 2.8 1 GB ram and one with an Athlon64 3000+ 1 GB RAM and the Athlon chokes much more on ettv then the PIV. PIV handles 75 slots easily, Athlon chokes on 50.
What can we do to further optimise our OSs for ETTV then?
Our servers now run on 64 bit steroids. Point your ET to:
- Forgotten Ground StopWatch Server with occasional wolfrof 1
- Fraggle Rock ETPub Server - Mix up ET/UT & Duke Nukem
- Forgotten Ground StopWatch Server with occasional wolfrof 1
- Fraggle Rock ETPub Server - Mix up ET/UT & Duke Nukem
Really? My CPU shoots up to 99% on a Suse 9.1 64 bit Athlon 3000+...
Can anyone shed some more light on this then?
Can anyone shed some more light on this then?
Our servers now run on 64 bit steroids. Point your ET to:
- Forgotten Ground StopWatch Server with occasional wolfrof 1
- Fraggle Rock ETPub Server - Mix up ET/UT & Duke Nukem
- Forgotten Ground StopWatch Server with occasional wolfrof 1
- Fraggle Rock ETPub Server - Mix up ET/UT & Duke Nukem
b9 fixed the lag problems, unless your network is dropping packets altogether.
EDIT: Do note that you should run b9 on both the master and the slave for the fixes to be noticable..
EDIT: Do note that you should run b9 on both the master and the slave for the fixes to be noticable..
Zinx Verituse http://zinx.xmms.org/
deej wrote:Really? My CPU shoots up to 99% on a Suse 9.1 64 bit Athlon 3000+...
Can anyone shed some more light on this then?
![Image](http://www.userbase.be/forum/images/smiles/icon_help.gif)
Our servers now run on 64 bit steroids. Point your ET to:
- Forgotten Ground StopWatch Server with occasional wolfrof 1
- Fraggle Rock ETPub Server - Mix up ET/UT & Duke Nukem
- Forgotten Ground StopWatch Server with occasional wolfrof 1
- Fraggle Rock ETPub Server - Mix up ET/UT & Duke Nukem
Yeah Roadkillpuppy told me that I should start by disabling acpi because it's buggy on Suse and could be the culprid.
So I booted the machine with acpi=off appended in my grub. Now we'll see what it gives at the next broadcast.
So I booted the machine with acpi=off appended in my grub. Now we'll see what it gives at the next broadcast.
Our servers now run on 64 bit steroids. Point your ET to:
- Forgotten Ground StopWatch Server with occasional wolfrof 1
- Fraggle Rock ETPub Server - Mix up ET/UT & Duke Nukem
- Forgotten Ground StopWatch Server with occasional wolfrof 1
- Fraggle Rock ETPub Server - Mix up ET/UT & Duke Nukem
- RoadKillPuppy
- Posts: 207
- Joined: Thu Apr 08, 2004 9:21 am
- Location: Belgium!
- Contact:
Oh lol I thought you meant ACPI.RoadKillPuppy wrote:Did I ?![]()
Ps. I was thinking about a daemon called "cpuspeed" on fedora when I asked you about cpu thottling...
Anyway to set it all straight, RKP said something about throttling and google told me that ACPI was buggy in Suse. There!
RKP != Google (although close
![Wink ;)](./images/smilies/icon_wink.gif)
Our servers now run on 64 bit steroids. Point your ET to:
- Forgotten Ground StopWatch Server with occasional wolfrof 1
- Fraggle Rock ETPub Server - Mix up ET/UT & Duke Nukem
- Forgotten Ground StopWatch Server with occasional wolfrof 1
- Fraggle Rock ETPub Server - Mix up ET/UT & Duke Nukem