You have OpenSP integrated with your mod. Use my Alternative OpenSP or a variant, instead.
Weird error
-
-
How so, which part would be considered open SP. All I have is new systems and ships. I didn´t put anything in that would make it open SP, that I am aware of. Ah, hang on, I did use Freelancer SDK 1.5 Would that do it? Buck Rogers Server Admin Colours Elite UK http://www.colourselite.co.uk Edited by - Buck on 10/13/2005 2:58:15 PM Edited by - Buck on 10/13/2005 2:59:26 PM
-
Buck - I have to disagre with Argh here, that´s nothing to do with OpenSP i dont think - I havent got a network to test multiplayer on but do loopback via my router. I get those messages when i use a jumpgate/jumphole. I´m as certain as i can be that they are simply debug messages to show devs when a jump has taken place with CLI(<n><img src=smilies/icon_smile_wink.gif width=15 height=15 border=0 align=middle> (which i dont see) being the player index. Edit : CLI(33) is strange I spose but on an index starting at 1 (the host/server) then 32 players on top... +++ out of cheese error - redo from start +++ Edited by - anton on 10/14/2005 7:50:18 AM
-
I do get this when i run my test server and connect via LAN but this is suggesting that all players are connected via LAN and this not true as my server is hosted. Buck Rogers Server Admin Colours Elite UK http://www.colourselite.co.uk
-
I get this error when I run my test server without the 1.1 patch in, always thought it was normal. Installing the patch seems to get rid of it. Probably just a bit of verbose legacy code left in by the dev team for whatever reason.
-
Hmm. Well, I guess I was wrong (wouldn´t be the first time, lol), maybe it´s not related to OpenSP´s modded DLL. The reason I said that in the first place is that I made it go away when I started commenting out the Missions INIs- whatever this "bug" is, it´s related to whatever in FL is paying attention to whatever area players are in, and I think it has to do with the Missions code. I don´t think it´s a crash bug of any kind- I can see that error over and over again without any problems.