Trouble connecting client to the server across LAN or WAN
This game looks fantastic. I've long been frustrated with the limitations I've seen in Artemis, and this is a breath of fresh air. Lua scripting for missions, different sized ships - including little single pilot fighters! omgomgomgomg
I'm having trouble connecting clients and actually playing, though. When I start the server on one machine (Windows 7 Pro), and connect from another on my LAN i get
"The program has encountered a serious error and needs to close."
This is running in Wine on Mac OS X, but also on another Windows machine. I've tried the last three builds. Is there a better way to try this game out?
Comments
I'm trying to get the new crash logger builds working on my Linux VM. I'll test with Wine after I get it working.
We were hoping to run EE this past Saturday and Sunday at the convention we were at, but the crash bug wouldn't allow us to connect.
Don't believe I tried the selecting scenario after connecting, but I can test to confirm using the old build.
Once this issue (https://github.com/daid/EmptyEpsilon/issues/59) is closed with a code change, you could theoretically have the clients autoconnect/reconnect using the options.ini file (or add to the end command to run the game). This is what I plan to do on my machines. Plus this way the stations can't be changed by other people (which can be a pain with people clicking on the screen with Artemis - newer versions broke this I believe)
autoconnect=#
Where # is one of the below numbers
-- 6/5 Player Crew
1 = Helms
2 = Weapons
3 = Engineering
4 = Science
5 = Relay
-- 4/3 Player Crew
6 = Tactical
7= Engineering+
8 = Operations
-- 1 player crew/extras
9 = Single Pilot
10 = Damage Control
11 = Power Management
12 = Database
13 = Main Screen (currently anything over 13 is considered a main screen)
Are you testing it on the same machine perhaps? If so, check out daid's and my discussion here: https://github.com/daid/EmptyEpsilon/issues/59