ETTV Public beta 8
Moderators: Forum moderators, developers
That bug should have been fixed in b8 :/
Old demos will still have the problem, though.
Old demos will still have the problem, though.
Zinx Verituse http://zinx.xmms.org/
The demo was recorded today so I guess it's still there.zinx wrote:That bug should have been fixed in b8 :/
Old demos will still have the problem, though.
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
- EagleReloaded
- Posts: 278
- Joined: Fri Nov 19, 2004 9:15 pm
- Location: Sydney, Australia
Good point. Have to recheck that with B8 then.EagleReloaded wrote:But you used a B4 gameserver to record the demo, so wouldn't it still have the problem then regardless of what slave you used? B8 might indeed fix it.
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
some values of ettv_mtu between 1400 and 16000 (on the master) seem to cause the slave to get in trouble.
Various values from 1401 through 12000 seemed to give errors like
Sometimes the slave would also crash.
Both master and slave running ettv-beta8pingfix
tested with multiple masters and slaves on different networks. Masters were all playing back a demo.
13000 and above seemed to work, as does 1400
Various values from 1401 through 12000 seemed to give errors like
Code: Select all
ERROR: ettv_CL_ParseGamestate: bad command byte
********************
VM_Call with NULL vm
Code: Select all
ERROR: MSG_ReadDeltaShared: wrong magic byte 0xffffffff
********************
Both master and slave running ettv-beta8pingfix
tested with multiple masters and slaves on different networks. Masters were all playing back a demo.
13000 and above seemed to work, as does 1400
send lawyers, guns and money
That happens on the network that didn't delay toobani wrote:looks like your networks are corrupting udp fragments. and of course you already know something in your network is delaying consecutive udp packets.
edit:
it also happens for mtu's less than 1400
edit:
it also happens if the slave and master on the same box.
edit:
tried on a single box with both linux 2.4.30 and winxp, same result.
send lawyers, guns and money
i had another few crashes on borked demos, this time b8 with pingfix:
i am not sure anymore if it really only happens on certain demos or also at random, but here is the demo:
http://dl.vpclan.de/demo0000.tv_84
EDIT: Just had it crash on the same demo again - same debug message
Code: Select all
Version: etpro 3.2.0
Platform: Linux
Signal: Segmentation violation (11)
Signal code: 1
fault address: 0x14d0
Load addresses:
0x40020000 /lib/tls/libm.so.6
0x40043000 /lib/libdl.so.2
0x40048000 /lib/tls/libc.so.6
0x40000000 /lib/ld-linux.so.2
0x495ff000 /lib/libnss_compat.so.2
0x49607000 /lib/libnsl.so.1
0x4961d000 /lib/libnss_nis.so.2
0x49627000 /lib/libnss_files.so.2
0x49631000 play/pb/pbsv.so
0x4ed18000 /lib/libnss_dns.so.2
0x4ed1e000 /lib/libresolv.so.2
0x4c908000 /home/ettv/et/etpro/tvgame.mp.i386.so
EIP: 4c92f79e
edi:00000000 esi:000014d0 ebp:00000710 esp:bfff3320
eax:00000710 ebx:4c943720 ecx:000001c4 edx:00000000
stack:
4c93e988 00000000 00000000 4c943720 00000001 00000000 0805bb8d 4c92cff1
00000000 080b0e87 08dc884c 00000000 08de8c00 bfff4408 fffffffe 0808d91c
00000001 00000000 0805bb8d 080b09e4 080c15e0 0000044d 08077fd7 00000000
00000002 bfff4408 08078208 080cbf61 08dc6620 00000000 08ab1d44 08059da8
code:
f3 a5 8b bb 20 ff ff ff ff 44 24 08 81 44 24 04 c8 5b 00 00 8b 54 24 08 3b 57
0c 7c 95 83 c4 0c 5b 5e 5f 5d c3 8d 8b 80 b2 ff ff 8d ab ac e4 ff ff 89 0c 24
Stack trace:
1 entries
/home/ettv/et/etpro/tvgame.mp.i386.so[0x4c9235a8]
http://dl.vpclan.de/demo0000.tv_84
EDIT: Just had it crash on the same demo again - same debug message
-=[VP]+arni+=- wrote:i am not sure anymore if it really only happens on certain demos or also at random, but here is the demo:
http://dl.vpclan.de/demo0000.tv_84
EDIT: Just had it crash on the same demo again - same debug message
Code: Select all
-------- UNRECOVERABLE ERROR --------
This may be due to a bug in etpro
Information to be used in a bug report is being generated:
------------- CUT HERE --------------
Version: etpro 3.2.0
Platform: Linux
Signal: Watchdog (14)
Signal code: 128
Load addresses:
0x4001d000 /lib/libm.so.6
0x4003e000 /lib/libdl.so.2
0x40041000 /lib/libc.so.6
0x40000000 /lib/ld-linux.so.2
0x40012000 /lib/ld-linux.so.2
0x499e0000 /lib/libnss_compat.so.2
0x499e8000 /lib/libnsl.so.1
0x499f9000 /lib/libnsl.so.1
0x499fc000 /lib/libnss_nis.so.2
0x49a05000 /lib/libnss_files.so.2
0x49a0e000 /srv/et/ETTV/ettv_slave/pb/pbsv.so
0x4c50c000 /srv/et/ETTV/ettv_slave/etpro/tvgame.mp.i386.so
0x4e8a2000 /lib/libnss_dns.so.2
0x4e8a7000 /lib/libresolv.so.2
0x4e8b5000 /lib/libresolv.so.2
EIP: 400e9d72
edi:bffff568 esi:00000000 ebp:08dc79b0 esp:bffff530
eax:fffffffc ebx:00000010 ecx:bffff570 edx:00000000
stack:
00000010 bffff570 0000000f 0804d5e1 00000010 bffff570 00000000 00000000
bffff568 00000000 4c534e99 4c547720 00000008 0c3c6fb6 00000000 0000bb80
00008001 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
code:
5b 5e 5f 3d 01 f0 ff ff 73 39 c3 e8 ca 12 01 00 50 57 56 53 8b 7c 24 24 8b 74
24 20 8b 54 24 1c 8b 4c 24 18 8b 5c 24 14 b8 8e 00 00 00 cd 80 5b 5e 5f 87 04
Stack trace:
1 entries
/srv/et/ETTV/ettv_slave/etpro/tvgame.mp.i386.so[0x4c5275a8]
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
Works great here though.-=[VP]+arni+=- wrote:ettv_autorecord also doesnt work in b8 :-/
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
I narrowed this one a bit more down.deej wrote:Had another weird error today with the b8. I startup a slave with +map oasis to let it run standalone. Then, when I try to connect that slave to our hub it does this:
Any idea why it resolves port 50000 to -15536?Code: Select all
tv connect ettv2.fragland.org:50000 [pass] [pass] ----- Server Shutdown ----- Sending heartbeat to etmaster.idsoftware.com ==== ShutdownGame ==== --------------------------- ettv: ettv2.fragland.org:50000 resolved to 217.20.115.116:-15536 Sys_Error: VM_Call with NULL vm Shutdown tty console
- ettv_netblast 1 on the hub gets the slave into trouble like noted above
- ettv_netblast 0 does not but creates huge amount of skipped demoframes.
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
a bit late, but ettv-b8-pingtest shows very different ping and lagometer from etded.
On the same server, with myself as the only player and plenty of CPU and bandwidth to spare:
etded
~40 ping, only very occasional yellow in upper lagometer
ettv-b8-pingtest
~70 ping, long runs of yellow spikes in the lagometer.
It could be placebo, but b-8-pingtest feels laggier too. b-7 looks/feels like etded.
edit:
reproducable on multiple servers, including dedicated on the same box as the client.
On the same server, with myself as the only player and plenty of CPU and bandwidth to spare:
etded
~40 ping, only very occasional yellow in upper lagometer
ettv-b8-pingtest
~70 ping, long runs of yellow spikes in the lagometer.
It could be placebo, but b-8-pingtest feels laggier too. b-7 looks/feels like etded.
edit:
reproducable on multiple servers, including dedicated on the same box as the client.
send lawyers, guns and money