Freejack Posted February 4, 2014 Share Posted February 4, 2014 It will not let you mine/salvage or interact with anything in the sector. It will let you give your fleet commands. Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted February 4, 2014 Boxelware Team Share Posted February 4, 2014 Have you tried the actual version 0.5.5? Because that should be fixed there. Link to comment Share on other sites More sharing options...
Freejack Posted February 4, 2014 Author Share Posted February 4, 2014 Yes 5.5 server and 5.5 client and once in can not do anything. Have to use IP. Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted February 4, 2014 Boxelware Team Share Posted February 4, 2014 I'm not sure how this is possible, this worked for me. But it looks like this is a bigger issue than I first thought. Post the server log and the client log with network tracing enabled, please, otherwise I won't be able to help you. You can enable network tracing by adding -t network to the command line options of server and client. Start the server with network tracing enabled, log in with URL, try to mine something, then log out and send me both logs. Link to comment Share on other sites More sharing options...
Freejack Posted February 4, 2014 Author Share Posted February 4, 2014 will do that for you later today. Link to comment Share on other sites More sharing options...
Freejack Posted February 4, 2014 Author Share Posted February 4, 2014 Here is server :  Incoming connection from 68.117.251.9:39492                                                                Connection to player established                                                                      Server TCP: Error occurred in async_receive: End of file. Bytes transferred: 0                                               Incoming connection from 68.117.251.9:39493                                                                Server: connection 0 was closed by remote                                                                 Connection to player established                                                                      Player logged in: Freejack, index: 1                                                                    <SERVER> The Nav-Computer is calculating the jump route. Please stand by.                                                 <SERVER> Jump route calculated.                                                                      <SERVER> Your ship is facing in the wrong direction.                                                            <SERVER> Your ship is facing in the wrong direction.                                                            <SERVER> Your ship is facing in the wrong direction.                                                            <SERVER> Your ship is facing in the wrong direction.                                                            <SERVER> Your ship is facing in the wrong direction.                                                            <SERVER> Your ship is facing in the wrong direction.                                                            <SERVER> Your ship is facing in the wrong direction.                                                            Server TCP: Error occurred in async_receive: End of file. Bytes transferred: 0                                               Server: connection 1 was closed by remote                                                                 Player logged off: Freejack, index: 1                 Client Log:  Client: attempting to connect to fjbbs.gotdns.com:24000 Client: connection established Client UDP: Connection closed Client TCP: Error occurred in handleReceive: Operation canceled. bytes transferred: 0 Client: attempting to connect to fjbbs.gotdns.com:24000 Client: connection established <Server> Player Freejack logged in <SERVER> The Nav-Computer is calculating the jump route. Please stand by. <SERVER> Jump route calculated. <SERVER> Your ship is facing in the wrong direction. <SERVER> Your ship is facing in the wrong direction. <SERVER> Your ship is facing in the wrong direction. <SERVER> Your ship is facing in the wrong direction. <SERVER> Your ship is facing in the wrong direction. <SERVER> Your ship is facing in the wrong direction. <SERVER> Your ship is facing in the wrong direction. Client UDP: Connection closed  Hope this helps.  Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted February 4, 2014 Boxelware Team Share Posted February 4, 2014 I'm afraid it doesn't help. You need to turn on network tracing on both client and server. You can enable network tracing by adding -t network to the command line options of server and client. Please enable this on both client and server, then post both client and server logs. Link to comment Share on other sites More sharing options...
Freejack Posted February 4, 2014 Author Share Posted February 4, 2014 i added -t network to both.  Client  client.sh -t network Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted February 5, 2014 Boxelware Team Share Posted February 5, 2014 You have to add the options to the command line options of the application, not the script. Open the .sh files, add -t network to the invocation of the applications, then execute the script. Link to comment Share on other sites More sharing options...
Freejack Posted February 5, 2014 Author Share Posted February 5, 2014 ok gotcha will do. Link to comment Share on other sites More sharing options...
Freejack Posted February 6, 2014 Author Share Posted February 6, 2014 i am unable to post the 2 files in here they exceed the limits I have tried pastebin and susepaste of which it also exceeds. Read your PM .... Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted February 6, 2014 Boxelware Team Share Posted February 6, 2014 It looks like your UDP port changed during play. Your client identified to the server with a certain port for UDP (which is good), then used another one to actually do communication (which is bad), this means the UDP packets from the server get lost and the server won't accept the packets from the client, as they're coming from an unexpected port. I'll investigate how this can happen. Link to comment Share on other sites More sharing options...
Freejack Posted February 6, 2014 Author Share Posted February 6, 2014 Before you go to far, could this be an issue where the url resolves and the game changes the UDP due to being inside the network? Even though the system routes the url from within the network? I gues the only true test would be someone on the outside trying the url and playing the game. Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted February 6, 2014 Boxelware Team Share Posted February 6, 2014 This is nothing the game actively changes. I rather think it's a problem caused by ephemeral ports. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now