Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment   Page 1 of 2      1   2   Next
Arkantos

Avatar / Picture

Registered:
Posts: 419
Reply with quote  #1 
ArtemisDisplay is an application which can serve as a supplementary display for Artemis. Currently, it only displays an alert status screen, but I plan to add more functionality in the future.

1971756.png 
ArtemisDisplay running under Windows 7.

DOWNLOAD


Setup
  1. ArtemisDisplay requires Java 1.7 or later, and runs on any windowed OS that runs Java. See java.com for information on how to install Java.
  2. ArtemisDisplay requires no installation. Simply double-click the downloaded JAR file to run it. Alternatively, you can use the command line (see below).


Usage

By default, when you launch ArtemisDisplay, you'll get a setup dialog that looks like this:

config.png
Setup dialog under Windows 10

Here's how to set it up

  1. ArtemisDisplay needs to know where the Artemis installation is located. If you've installed Artemis in the default location on Windows, ArtemisDisplay will locate it automatically. Otherwise, you will need to select its location. Click the "..." button and select the directory where the installation is found. See below for information about running ArtemisDisplay on a machine where Artemis is not installed.
  2. You need to specify where the Artemis host is (or will be) running. By default, this blank contains "localhost", meaning that the server is running on the same machine as ArtemisDisplay. If it's located on a different machine, replace this with that machine's host name or IP address. The default port (2010) is assumed; if yours is different, append the port number to the address, separated with a colon. (ex. 192.168.1.12:8888).
  3. Set which ship's status should be reflected by the display. By default, ship #1 (Artemis) is selected.
  4. ArtemisDisplay has a feature called Red Alert Management (RAM), which will automatically activate and deactivate red alert in certain situations. This may be a nice option if you find that your comm officer routinely ignores the red alert function. Mark the checkboxes for the situations under which you'd like the ship to be under red alert. If you don't mark any checkboxes, ArtemisDisplay will not modify the ship's alert status.
Once you are ready, click "Connect."


Display Behavior

By default, ArtemisDisplay runs in fullscreen mode. To run in a window, press ESC. Maximize the window to return to fullscreen mode.

The message "Waiting for {host}" will appear when ArtemisDisplay is not connected to the Artemis server. It will continually retry the connection until it succeeds. This means you can launch ArtemisDisplay before the Artemis server is up if you like; once the server's up, ArtemisDisplay will automatically connect to it.  If the connection is ever lost, it will go back to this screen and keep trying to reconnect.

Once it connects to the server, it will display the ship's alert status if a game is in progress. Otherwise, the message "Simulation not running" will be shown.

During the game, ArtemisDisplay will show one of four possible alert conditions:
  • If the ship is at red alert, ArtemisDisplay will always show CONDITION RED. This display is always animated.
  • If the ship is not at red alert but the shields are up, it will show CONDITION YELLOW. Obviously, this will never show up if you have ArtemisDisplay set to automatically activate red alert when the shields are up. The condition yellow display is not animated.
  • If the ship is held by a starbase's tractor beam while not at condition yellow or red, it will show CONDITION BLUE. This display is animated while the ship is still being drawn in by the base; once docking has completed and resupply commences, the display stops animating.
  • If none of the above conditions apply, it will show CONDITION GREEN. This display is not animated.
The display will flicker if the ship is struck by enemy weapons fire. If the ship is destroyed, the screen will go black. Once the game ends, it will return to the "Simulation not running" screen, ready for the next game to start.

To exit ArtemisDisplay, press ESC if it's in fullscreen mode, then close the ArtemisDisplay window.


Running ArtemisDisplay on a Machine Where Artemis is Not Installed
  1. On the machine where ArtemisDisplay will run, create a directory named "artemisdisplay" and put "artemisdisplay.jar" in it.
  2. Create a subdirectory under "artemisdisplay" named "dat".
  3. On a machine that has Artemis installed, go to the "dat" directory under the Artemis install directory.
  4. Copy the "vesselData.xml" file you find there to the "dat" directory you created on the machine where ArtemisDisplay will run.
  5. When running ArtemisDisplay, select "artemisdisplay" as the Artemis directory.


Command Line Interface

The syntax for running ArtemisDisplay from the command line is as follows:

java -jar artemisdisplay.jar [configFile]

If configFile is omitted, ArtemisDisplay will launch the setup dialog, the same as if you had double-clicked the JAR file. Providing a configuration file will allow you to launch ArtemisDisplay with a predetermined configuration; ArtemisDisplay will skip the setup dialog and immediately attempt to connect to the server. Below is an example of what a configuration file looks like:

artemisInstallDir=C:\Program Files (x86)\Artemis
host=localhost:8888
shipNumber=2
redAlertOnShieldsUp=true
redAlertOnHit=true

artemisInstallDir: Where Artemis is installed. This value is required.

host: The host name or IP address where the Artemis server is (or will be) running. This value is required. If the port number is omitted, the default (2010) is assumed.

shipNumber: What ship to display. This must be a value between 1 and 8, inclusive. If omitted, 1 is assumed.

redAlertOnShieldsUp: Whether ArtemisDisplay will automatically control alert status in response to shield state. Valid values are "true" or "false". If omitted, "false" is assumed.

redAlertOnHit: Whether ArtemisDisplay will automatically control alert status in response to the ship being hit. Valid values are "true" or "false". If omitted, "false" is assumed.


Planned Future Features

  • Multi-monitor support
  • More automatic alert management states
  • More display types
  • Layout support to draw multiple displays on one screen

MEGALODONJC

Registered:
Posts: 18
Reply with quote  #2 
Arkantos thank you for ur dedicated work.On my credits for my show would you like me to make a reference in the credts such as..
Alert status display programmed by arkantos or your actual name please reply with ur preference please
Arkantos

Avatar / Picture

Registered:
Posts: 419
Reply with quote  #3 
It's not really necessary, but if you want you may credit me as Robert J. Walker. I'd love to see a link when you put up something using it!
RogerW37

Registered:
Posts: 70
Reply with quote  #4 
The Good:  Instead of COMMS doing red alert just for fun or when they are bored, the ship now automatically goes to red alert when hit and auto turns off red alert.  Sweet.  It now serves to enhance the experience and is consistent.

You also now have Yellow alert and Blue alert which is an added bonus.

I checked all conditions (based on my settings below) and everything (receiving a hit, comms issuing red alert, docking, docked, shields) seemed to work as expected.

The Bad:  You cost me another monitor! [smile]  It's worth another monitor, no worries there.

I used the following settings:

Artemis Directory:  C:\Games\Artemis
Host: localhost
Ship number: 1
Put the ship on automatic red alert when...
[ ] ...the shields are up
[x]...the ship has been hit within the last 30 seconds.

Recommendation:  Don't use "localhost", instead use the IP address.  For some reason "localhost" would drop after a few minutes (longest for me was 11 minutes) to the "Waiting for..." screen and never recover until the next game.  While I don't have a lot of time on it, it seemed to not drop when using the IP address.

Thanks again for the fun and additional immersion!
RogerW37

Registered:
Posts: 70
Reply with quote  #5 
My recommendation above seems to help (using the IP address versus localhost), but even so, after a few minutes in the game (20 minutes or so), it dropped to "Waiting for..." during a game. 

The setup is all same computer (not wireless or going through a router).

I've tried to force the issue, but can't seem to isolate it.  I kept condition red by being under attack for several minutes (everything off except shields), but it worked fine.  I ran back and forth through an enemy, letting auto red alert come on and auto turn off.

Even with the occasional disconnect, I still plan to use this next week for my "Artemis Day".

Thanks again for an awesome alert status screen.
RogerW37

Registered:
Posts: 70
Reply with quote  #6 
A simple "no man" mission where I let it sit for just under two hours and no problems.  Maybe my computer just needed to warm up.
RogerW37

Registered:
Posts: 70
Reply with quote  #7 

Still buggy.  The display can last a minute or up to 10 but ultimately disconnects.  After disconnect, I've never been able to restart and reconnect.  It takes the game ending and starting a new game.

RogerW37

Registered:
Posts: 70
Reply with quote  #8 

Discovered if run under a Standard Account, many odd problem would happen.  Trying only under Administer Account and will report back.

RogerW37

Registered:
Posts: 70
Reply with quote  #9 
After several games with an administrator account, it still disconnects.

However, we noticed that the automatic red alert still issued the red alert when the ship was hit by something, so it's "connected" but the display screen shows "Waiting for..."
EnzoMatrix

Avatar / Picture

Registered:
Posts: 10
Reply with quote  #10 
Generally appears to be working for me, thanks!

I only have two issues

1) Can't get it to run using java -jar and parameters
2) When setting auto red alert when hit, Artemis cancels red alert about after 10 seconds of no damage

Both of these are easy to get around and we will be playing for a couple of hours in a week or two, so will let you know how we go [smile]

__________________
Fleet Admiral Enzo Matrix
United Space Command
RogerW37

Registered:
Posts: 70
Reply with quote  #11 
When the connection drops, about every 2 to three seconds, an empty "error-2016##########.txt" is created in the "artemisdisplay" folder.

I have tried directly running the program, using batch files, setting up as if Artemis isn't installed (copying the vesseldData to artemisdisplay/dat and specifying this as the artemis directory), putting artemisdisplay folder in root versus on the desktop, making sure Java is up-to-date (v8 u101), etc.


Arkantos

Avatar / Picture

Registered:
Posts: 419
Reply with quote  #12 
Interesting, I was going to ask if any log files were being created. Apparently I have a bug in the log file creation! I'll look into it. Let me know if you come up with any more information.
LordEntrails

Registered:
Posts: 15
Reply with quote  #13 
I might just have to build a bridge just so I can put this on a couple of tablets and build them into the walls! I wonder if my wife would notice...
Arkantos

Avatar / Picture

Registered:
Posts: 419
Reply with quote  #14 
RogerW37, I've uploaded a new version of ArtemisDisplay. This won't fix the problem, but it will hopefully ensure that we don't get empty error dump files. I tried to duplicate that problem of ArtemisDisplay dropping, but couldn't get it to happen. Try this one and let me know what the error dump file says.
jamestjohnson

Avatar / Picture

Registered:
Posts: 102
Reply with quote  #15 
How can I get this to work with 2.7 ???
__________________
Captain
James T Johnson
The Devarden
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.