Hi,



I post this message on the forum because I have a trouble when I try to launch a game in multiplayer with my friend. We both stay on the loading screen and the game don't start. When one of us leave Endless Space with ALT+F4 , the multiplayer game starts for the other. We have tried to stay the loading screen during 5 minutes but nothing changes. The game only starts when one of us leaves . We don't know what is the reason of this problem . Our internet connections are good and fast like as our computers. In solo mode, we play in fantastic graphism level without any trouble or lags.



If someone has the same problem or had it. Or if you can help me, please answer.



(Sorry for my basic english.)



Yours faithfully

JT54fr

Sorry as I can't offer any help but I do now this problems, I've seen it in different places under different circumstances. Usually it just works when one of the involved players leaves, often it then is necessery to stay away from the game 1 or maybe even a few turns so it can go on.



To me it seems like there are some utterly incinsisten calculations in the end turn system which easily result in loops. Further the game is (like absolutely every other game ) unable to even identify loops. This is an issue I hope the devs manage to address soon. But once they have some bad stuff like that in there expect it to take at least 2 months till they got rid of all of these bugs, most likely even more though.

I don't know if it will help but I had issues with Hamachi and Endless Space multiplayer. Try ending hamachi-exe in your Windows Applications menu (alt+ctrl+del).

Ending the Hamachi process in the menu fixed the 'Endless' loading glitch.

Thank's for the help people ! I will try !



EDIT : It works ! THANKS ! I LOVE YOU

Excellent, my glitch was that I would get "%updating" instead of people's names and then it would be stuck in loading as we never actually connected.

Sparta114 wrote:
Ending the Hamachi process in the menu fixed the 'Endless' loading glitch.

This. Thank you.



Also, wrong section! But I am glad the problem is solved.



As for the %updating, this is another issue you can read about in the Technical support: this thread.