Thought this deserved a new thread to aid searchability
I'm using B4 on the master and B7 on the slave and have had this error: Every map change or round start the master server does what it's supposed to, but the slave completely pings out and then sits there loading and re-loading the map until it a)crashes or b) I restart it.
Now i read this was something to do with the number of PK3's so i did some testing and found that any more than 8 custom pk3's caused this problem. 8 or less, and the slave behaved impeccably.
Is there any fix to this? At the moment the leagues we play in have a total of 12 maps, and so we REALLY need all 12 on the server
Is this a B7 error only? If i switch versions will it help?
Thanks
B4 bug - 8 pk3 limit?
Moderators: Forum moderators, developers
CS_SYSTEMINFO was truncated improperly in ETTV, IIRC... It has of course been fixed already.
Zinx Verituse http://zinx.xmms.org/
-
- Posts: 19
- Joined: Sat Jan 07, 2006 7:35 am
It's only a small gamble but I think Zinx will recommend b9.goatherder wrote:Thanks
Which release was it fixed in Zinx? And would you recommend using that release over B4/B7?
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
-
- Posts: 19
- Joined: Sat Jan 07, 2006 7:35 am
afaik its fixed in b7 (because i reported it in b6)zinx wrote:CS_SYSTEMINFO was truncated improperly in ETTV, IIRC... It has of course been fixed already.
(m)b4 -> (s)b7 is currently the best working broadcast setup
no players whining about lagspikes
no disordered packets due to b4 rate limit (which is a good thing here)
no strange recursive snapshot re-request (feels to me like it, no proof) as on b8, b9
its really the best setup if you plan to really get smth working
101% agree.-=[VP]+arni+=- wrote:(m)b4 -> (s)b7 is currently the best working broadcast setup
no players whining about lagspikes
no disordered packets due to b4 rate limit (which is a good thing here)
no strange recursive snapshot re-request (feels to me like it, no proof) as on b8, b9
its really the best setup if you plan to really get smth working