Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment  
Zetner

Registered:
Posts: 4
Reply with quote  #1 
Yesterday I ran a game with four PCs on a LAN. The server was hosted on my PC (Windows 10). We were able to play several games, with no lagging or anything what-so-ever. But, sometimes when using our jump drive, the server instance crashed/shut down. There was no message as to what happened, it just shut down, and we all lost connection to the host.
Over the course of an evening, this happened 4-5 times. For our last game, we decided to use a warp-drive, rather than jump-drive, as that seemed to cause the crashes. But, we still had a crash, when engaging several enemy ships.
Does anyone have any idea what might be causing this? It didn't seem laggy or anything - we don't really think it's a hardware issue?
We did host the game from a PC having two instances of the game open - we all had installations through Steam.
Darrin

Registered:
Posts: 168
Reply with quote  #2 
Hmm. Jump drive, eh? I haven't heard anyone else having problems with jump drives.

Do you recall the difficulty setting and how long the game had progressed when it crashed? When 2.7.2 came out, we were seeing server crashes sometime around or after the 30-minute mark. We suspected this had something to do with a second wave of enemies coming in, usually Skaraans with new elite abilities. We thought these Skaraan abilities were causing crashes when they interacted with monsters/stations, but we weren't able to nail down anything specific.

At conventions, we were able to set the difficulty lower (usually at 3) so that Skaraans weren't showing up all that often, and that appeared to cut down the number of crashes. 

Another solution might be running scripts rather than the procgen missions. I've been writing mission scripts for 2.7.x for over a year, and haven't noticed any unexplained crashes in mission scripts.




Zetner

Registered:
Posts: 4
Reply with quote  #3 

Yeah, oddly enough, most of the times we crashed, it was while jumping?

Difficulty settings were 5 or 6. Terrain, Lethal Terrain, Friendly Ships, Monsters and Anomalies were all set to "Some". Scenario Siege. 
The 30 minutes sound about right? We never crashed right away - we always managed to do a few battles, and dock once or twice, before we crashed.

Forgive my noobishness: I might need you to elaborate on your last point. I don't know how to run scripts, or what procgen missions are?

Last time I played Artemis was several years ago 😃

Darrin

Registered:
Posts: 168
Reply with quote  #4 
Quote:
Originally Posted by Zetner

Forgive my noobishness: I might need you to elaborate on your last point. I don't know how to run scripts, or what procgen missions are?



procgen = procedurally generated. Those are under "Solo Game" and include "Siege", "Single Front", "Double Front", "Deep Strike", etc. Thom wrote the code to generate randomized missions. Most players play some variation of "Siege" when they play Artemis.

"Scripted Game" is the fourth option when you start the server, under "Solo Game", "PvP Game", and "Co-Op Game". Artemis comes already bundled with several scripts. This includes "TheWaningDark", "TheEndofPeace", "SiriusFeint", etc. These missions are written in an XML script, and they usually present some unique challenge or problem that is different from the procedurally generated missions. There are also dozens of scripted missions written by other Artemis players that you can find in these forums or on various websites. 

However... some caveats. Most of the mission scripts were written for versions of Artemis that are much older than 2.7.4, and they may crash or not function properly. 

Most of the scripts I've been writing recently are for 2.7.5, and I haven't been posting them because I'm saving them for Armada V. They also don't use a lot of Skaraans or jump drives, so when I say I haven't been having crash problems with my scripts, there may be a selection bias involved.


Zetner

Registered:
Posts: 4
Reply with quote  #5 
Cool! Thanks a bunch - When we get to play it again, we'll play around with a few different settings, to see if we can find something that doesn't crash the game.
LawsonThompson

Registered:
Posts: 625
Reply with quote  #6 
We just ran a 3-day Artemis event at a convention. We had only one server crash. That said: we ran a modified "Armada IV" script with difficulty level 4, instead of using the random Solo mission generator this year. Scripted GM missions provide far more control of scaling the mission challenge based on the skill (or lack thereof) of the crew.

I still suspect there could be stability issues with difficulty 5+, but we didn't try it.

__________________
----
Visit us at http://www.ltebridge.com
DupeOfURL

Registered:
Posts: 311
Reply with quote  #7 
Zetner - The folks I play with on the InterNet have a STRONG preference for Warp drives, but every now and then I convince them to take out a Jump drive boat.  Usually a Ximni make.  Maybe a stray Pirate jumper or 2.  Cannot recall ant TSN jumpers.  BUT we have not run into this issue.  Ran v 2.71 until v 2.7.4 came out late December. 
     You had another crash, with a Warp drive, and during an engagement.  How is your LAN connected?  I used to be able to use a Wi-Fi router for LAN connections a couple versions ago.  Then I started having problems with a station "locking up".  Depending on situation, "might" be able to "wait it out", but Not Good.  Started using a switch and, Voila!. no more problem.  Did you happen to have Task Manager running?  I am curious about CPU and/or RAM usage.  The fact it was the server crashing makes me wonder about that. 
    How did you get Artemis?  IF Steam, I'd suggest you make a "working copy" of Artemis from there to somewhere else on the Hard Drive.  IF bought from here, I'd consider making a fresh install and upgrade that to see if that fixes.  Might be some sort of strange unzipping error {maybe}...?? 
    Good Luck! 

__________________
on TeamSpeak as GrayBeard {the Grim}  ;-) 
on Twitter as   @GrayberdTheGrim 

Chief Engineer of the Fulminata, one of the Pirates Of BeechWood! 
Mike Substelny

Avatar / Picture

Administrator
Registered:
Posts: 2,408
Reply with quote  #8 
Quote:
Originally Posted by Zetner
Yeah, oddly enough, most of the times we crashed, it was while jumping?


Difficulty settings were 5 or 6. Terrain, Lethal Terrain, Friendly Ships, Monsters and Anomalies were all set to "Some". Scenario Siege. 
The 30 minutes sound about right? We never crashed right away - we always managed to do a few battles, and dock once or twice, before we crashed.

This is just speculation, but I think it's possible that your crashes were triggered by this chain of events:

  • The second wave of Skaraans spawns.
  • Your crew notices the Skaraans and jumps toward one of them.
  • The Skaraan sees you and immediately triggers an elite ability.
  • The elite ability triggers the crash.

This would be consistent with the theory that one of the new elite abilities can cause crashes. While our tests have always failed to observe the theoretical elite ability crash in captivity, I have faith that Thom fixed the crash bug in Artemis 2.7.5.

__________________
"The Admiralty had demanded six ships; the economists offered four; and we finally compromised on eight."
- Winston Churchill
Zetner

Registered:
Posts: 4
Reply with quote  #9 
Thanks for all of your replies! Next time we play, I hope it'll go smoother. We played on a LAN via Wi-Fi. Looking forward to trying it again in 2.7.5!
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.