Dinosawer Posted December 30, 2016 Share Posted December 30, 2016 Very odd problem - game was working fine yesterday, but today it consistently gets stuck on "loading". logs: client https://app.box.com/s/fov3g49nnq3md832dadt2nmkudzcxfd0 server https://app.box.com/s/0v529kqcvdw9xm0ss9rlx15d4d1olnlr says Client UDP: Error receiving from 127.0.0.1, error: An existing connection was forcibly closed by the remote host, received bytes: 0 [...] Querying for an authentication session ticket and then just does nothing. Server doesn't give any problems. Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted December 30, 2016 Boxelware Team Share Posted December 30, 2016 Thanks. It looks like a communication issue with the steam servers. Have you tried a few hours later? Link to comment Share on other sites More sharing options...
Dinosawer Posted December 30, 2016 Author Share Posted December 30, 2016 Just tried again, still nothing. Link to comment Share on other sites More sharing options...
Dinosawer Posted December 30, 2016 Author Share Posted December 30, 2016 Actually, just tried in offline mode and it does the same thing, so it can't be steam. client: Connecting to server at 127.0.0.1:27000:27000 Client UDP: Error receiving from 127.0.0.1, error: An existing connection was forcibly closed by the remote host, received bytes: 0 [...] UDP closed Fri Dec 30 20:25:35 2016| Client UDP: Connection closed Fri Dec 30 20:25:35 2016| desired: ip, init: ip Fri Dec 30 20:25:35 2016| Client: attempting to connect to 127.0.0.1:27000 Fri Dec 30 20:25:35 2016| Client UDP: Error receiving from 127.0.0.1, error: An existing connection was forcibly closed by the remote host, received bytes: 0 Fri Dec 30 20:25:35 2016| Client UDP: Error receiving from 127.0.0.1, error: An existing connection was forcibly closed by the remote host, received bytes: 0 Fri Dec 30 20:25:35 2016| UDP closed Fri Dec 30 20:25:35 2016| Client UDP: Connection closed Fri Dec 30 20:25:35 2016| Server: Fri Dec 30 20:25:15 2016| Server UDP: Error receiving from 127.0.0.1, error: An existing connection was forcibly closed by the remote host, received bytes: 0 Fri Dec 30 20:25:15 2016| Server UDP: Error receiving from 127.0.0.1, error: An existing connection was forcibly closed by the remote host, received bytes: 0 Fri Dec 30 20:25:15 2016| The server will not be authenticated via Steam and won't show up in public server lists. Fri Dec 30 20:25:35 2016| Connection to player established Fri Dec 30 20:28:44 2016| <Server> Player Dinosawer joined the galaxy Fri Dec 30 20:28:44 2016| Player logged in: Dinosawer, index: 1 Fri Dec 30 20:30:12 2016| Server: connection 127.0.0.1:62543 was closed by remote Fri Dec 30 20:30:12 2016| Server UDP: Error receiving from 127.0.0.1, error: No connection could be made because the target machine actively refused it, received bytes: 0 Fri Dec 30 20:30:12 2016| Server TCP: Error occurred in send: An existing connection was forcibly closed by the remote host Fri Dec 30 20:30:12 2016| Server TCP: Error occurred in send: An existing connection was forcibly closed by the remote host Fri Dec 30 20:30:12 2016| <Server> Player Dinosawer left the galaxy Fri Dec 30 20:30:12 2016| Player logged off: Dinosawer, index: 1 Fri Dec 30 20:30:12 2016| Server is shutting down. Fri Dec 30 20:30:12 2016| Saving factions... Fri Dec 30 20:30:22 2016| Saving sectors... Fri Dec 30 20:30:22 2016| Saving jumping ships... Fri Dec 30 20:30:22 2016| Saving settings... Fri Dec 30 20:30:22 2016| shutting down networking... Fri Dec 30 20:30:22 2016| UDP closed Fri Dec 30 20:30:22 2016| Server UDP: Connection closed Fri Dec 30 20:30:22 2016| UDP closed Fri Dec 30 20:30:22 2016| Server UDP: Connection closed Fri Dec 30 20:30:22 2016| cleaning up communicators... Game eventually says "Avorion is not responding" and windows closes it. Link to comment Share on other sites More sharing options...
Dinosawer Posted January 15, 2017 Author Share Posted January 15, 2017 Still happening on the latest patch... (well, now it says "couldn't connect: no response from server" or something) Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted January 15, 2017 Boxelware Team Share Posted January 15, 2017 Does it work when starting the server with a new galaxy? Link to comment Share on other sites More sharing options...
Dinosawer Posted January 15, 2017 Author Share Posted January 15, 2017 Yes, it does. ...and apparently my standard galaxy can load again too! Now it's just the creative one having issues. Odd, but I cam play again so I'm happy ^.^ Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted January 15, 2017 Boxelware Team Share Posted January 15, 2017 Nice! Can you send me a .zip of the creative galaxy so I can debug it? Either via email or file hoster or whatever suits you best. Link to comment Share on other sites More sharing options...
Archmage67 Posted February 18, 2017 Share Posted February 18, 2017 Koonschi, Were you able to figure anything out? this has happened to 2 different people on 2 different galaxies. During debugging the first person to get this I tried to delete just their player dat file and initially it worked however then they began appearing in the index file repeatedly and were unable to continue when relogging in because each time the game would see them as a new person and assign a new index to that person. I tried hex-editing the index file but that was unsuccessful and was forced to restart the galaxy. So clearly the problem seems to be with just the specific person loading in. I wish I had a command or script that would reset a specific player only instead of the whole galaxy until you can resolve the cause of the issue. Do you want me to send you the current galaxy with the new person that is stuck and can not log in? Thanks Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted February 21, 2017 Boxelware Team Share Posted February 21, 2017 I've fixed an issue related to this, not sure if it's yours as well. Deleting player data is a bad idea, but it didn't have anything to do with the problem that I fixed. Link to comment Share on other sites More sharing options...
Archmage67 Posted February 22, 2017 Share Posted February 22, 2017 Well the only reason I was attempting to delete player data is because they were hung at loading or they crashed their client on loading. Link to comment Share on other sites More sharing options...
Shyassasain Posted February 28, 2017 Share Posted February 28, 2017 I've also had this bug, whenever I try to load up a server it crashes upon loading. It's strange because it was working before I restarted my computer. Link to comment Share on other sites More sharing options...
thedamngod Posted March 1, 2017 Share Posted March 1, 2017 Please add the logs. You will find instructions in the link on bug reports from my signature :) Link to comment Share on other sites More sharing options...
Devious Posted March 1, 2017 Share Posted March 1, 2017 Are logs still needed about this problem? This keeps happening for some players while authentication is turned on. Turning it off does seem to fix the problem, but that opens another array of troubles. Link to comment Share on other sites More sharing options...
Boxelware Team koonschi Posted March 1, 2017 Boxelware Team Share Posted March 1, 2017 If a galaxy crashes reliably on player login, please send the galaxy with an EXTENSIVE report on what player makes it crash upon login. This goes for client and server crashes. This is a data driven error and I need the save that causes this, or I can't fix it. 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