So I took the server installer linked in this topic
and I already got around the IPv6 issue (at least I think so, since I dont know WHAT is going wrong right now)
A typical log looks like this
CODE08/09 02:01:21.768 Debug level set from 1 to 2.
08/09 02:01:21.806 Running AllSrv 1.07.0.00.140525
08/09 02:01:21.806 Entering ReceiveThread
08/09 02:01:21.860 Mission Initialize id=0 this=18d1fe8 now=326938288
08/09 02:01:21.865 trekCore completed
08/09 02:01:22.025 iStaticCoreVersion = 990047673
08/09 02:01:22.025 CoCreateInstance( CLSID_DirectPlay8Server ... )
08/09 02:01:22.027 m_pDirectPlayServer->Initialize( ... )
08/09 02:01:22.030 InitDPlayServer() returned 0
08/09 02:01:22.030 CoCreateInstance( CLSID_DirectPlay8Address ... )
08/09 02:01:22.031 pDP8AddressLocal->SetSP( &CLSID_DP8SP_TCPIP )
08/09 02:01:27.132 m_pDirectPlayServer->Host( &dpnAppDesc ... ) - returned 0
08/09 02:01:27.133 LoadRankInfo result: #ranks=31
08/09 02:01:27.133 calling LoadStaticMapInfo
08/09 02:01:27.133 LoadStaticMapInfo result: #maps=4
08/09 02:01:27.134 Timer: 0.001000s spent handling single Windows msg, 0.001000s total (longest so far)
08/09 02:01:27.183 Timer: 0.050000s spent in message pump, 0.050000s total (longest so far)
08/09 02:01:27.183 Timer: 0.050000s spent between iterations in ReceiveThread loop, 0.050000s total (longest so far)
08/09 02:01:28.163 Mission Initialize id=0 this=18dc300 now=326944560
08/09 02:01:28.331 Timer: 0.169000s spent handling single Windows msg, 0.172000s total (longest so far)
08/09 02:01:28.331 Timer: 0.198000s spent in message pump, 1.198000s total (longest so far)
08/09 02:01:28.332 Timer: 0.198000s spent between iterations in ReceiveThread loop, 1.198000s total (longest so far)
08/09 02:01:49.033 New connection ID: 4891fd8a IP: 192.168.1.12
meaning the server crashes when I try to connect. I actually JIT-debugged through the crash (though I dont understand much of the code from just one look) and it looks like it crashes because of a null pointer when trying to send the first message back to the client. If anyone has an idea what this could be and how to fix it I would be very grateful.
Can't get LAN-Server to work
-
ThePhantom032
- Posts: 836
- Joined: Sat May 09, 2009 11:00 am
- Location: Germany
-
TheAlaskan
- Posts: 2256
- Joined: Tue Apr 03, 2007 2:15 am
- Location: Denver, CO
The ACSS server installer doesn't work in LAN mode because of this:
http://trac.alleg.net/ticket/340
I've installed an beta version of the server on TA's machine.
http://trac.alleg.net/ticket/340
I've installed an beta version of the server on TA's machine.
The Escapist (Justin Emerson) @ Dec 21 2010, 02:33 PM:
The history of open-source Allegiance is paved with the bodies of dead code branches, forum flame wars, and personal vendettas. But a community remains because people still love the game.
-
ThePhantom032
- Posts: 836
- Joined: Sat May 09, 2009 11:00 am
- Location: Germany
Thanks for the info - i switched my svn to compile the latest code instead of R7, compiled and can now join my server with a self compiled client.
Sadly I crash when the game starts, but I assume thats an artwork issue like usual and am trying to fix that now
EDIT: Fixed artwork, works! Thanks again!
Sadly I crash when the game starts, but I assume thats an artwork issue like usual and am trying to fix that now
EDIT: Fixed artwork, works! Thanks again!
Last edited by ThePhantom032 on Fri Aug 09, 2013 8:58 pm, edited 1 time in total.
Still ready to teach anyone who asks nicely whatever they want to know about playing alleg. Contrary to popular opinion I do not eat newbies. Voobs taste much better.