| 
  • If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Buried in cloud files? We can help with Spring cleaning!

    Whether you use Dropbox, Drive, G-Suite, OneDrive, Gmail, Slack, Notion, or all of the above, Dokkio will organize your files for you. Try Dokkio (from the makers of PBworks) for free today.

  • Dokkio (from the makers of PBworks) was #2 on Product Hunt! Check out what people are saying by clicking here.

View
 

How to run Artemis on the Mac

Page history last edited by T. L. Ford 5 years, 4 months ago

How to run Artemis on a Mac (documented by MobileMacTech)

 

=====================================================

IMPORTANT: Currently some emulator software is incompatible with Artemis 2.0

=====================================================

 

Note: Due to this incompatibility, Artemis cannot be run by Crossover. You will only be able to use virtualization software (VirtualBox, Parallels, or VMware Fusion) or Bootcamp.

 

----------------

Update 11/11/13

Artemis 2.0 seems to be working fine using PlayOnMac as of version 4.1. Current version of PlayOnMac is 4.2.1. I had a chance to test it this weekend as the Artemis server on a MacBook Air and it worked perfectly.

 

Update 3/22/14

The latest Engines valuable in Wineskin Winery will now allow you to create a stable Wine application for Artemis 2.0/2.5.0-101.  Last holdout is Crossover as soon as they update their Wine libraries (fingers crossed). 

 

First of all, you need to have an Intel Mac to do this, however, if you have a PowerPC Mac running VirtualPC with at least Windows XP it may work, in theory. I have tested this on an iMac Core 2 Duo, MacBook Air (1st gen), and MacBook Air (11 in mid-2011), and it works great, although the graphics on the Air are pushed to the limits and sometimes get choppy. Your results may vary. Also, I have personally only tested this on OS X 10.6.8, 10.7.4, and 10.8.x so far. It should work fine on any minor update to these OSes. According to the developers, Wineskin Winery 1.7 (latest) is compatible with 10.6, 10.7, and 10.8.

 

Artemis needs to be installed for the licensing to be registered whether in a virtual machine or in an emulator.  Once it is registered, you can copy/modify the Artemis installation.  You can also copy the configured virtual machine or the Wineskin Winery app to another computer with the same host configuration (i.e. OS X 10.7 with Wineskin Winery to OS X 10.7 with Wineskin Winery).  You can definitely make it work by building the app from scratch on each computer with Wineskin Winery.

 

If you already have virtualization software, such as Parallels, or have your computer set up with Boot Camp, you can just install Artemis within the Windows environment. The benefit of the method explained here is that you do not have to reboot your Mac, or wait for Windows to start up.  See below for advanced disk space saving and modding optimization.

 

Update 3/29/12: Oracle's VirtualBox seems to have glitches with the virtual video drivers which causes serious display issues. Other VM software may work better. 5/21/12: VirtualBox 4.1.14 on Mac OS X 10.7, with Windows XP SP 3 does not work properly due to graphical problems.

 

Update 5/21/12: Parallels 6.0 with Windows XP SP 3 works perfectly. It can be a problem to run the server from the virtual machine, however, as other computers may not be able to find the Parallels virtual machine on the network. It is easiest to run the server using a native Windows client or by using Wineskin Winery (described below).

 

Wineskin Winery is probably the best solution if you don't already have a virtual machine running (plus, it does not require a copy of Windows). It does very occasionally crash, so it is probably not ideal for the server. There are a number of alternative "wrapper" programs such as CrossOver that will run Windows programs on Mac OS X and Linux operating systems, but I've had the best luck with Wine, which is Open Source and free.

 

Artemis on the Mac using Wineskin

 

Install Wineskin

 

  • Download Wineskin from http://wineskin.urgesoftware.com/tiki-index.php?page=Downloads
  • Unzip and copy the binary into ~/Applications, that is, the "Applications" folder that lives inside of your home folder.  Installing to the home directory instead of the root /Applications is personal preference, but for security, I prefer the Windows emulator and the binaries it produces to live in my home folder rather than the system.

 

Set up Wineskin

 

  • Double-click to launch.
  • Wineskin has two components you must first download: an engine and a wrapper.  The engine is the stock version of WINE (the free and Open Source Windows Emulator), providing the runtime and API calls and whatnot.  The wrapper is the Mac app and user interface glue that gives you an app icon and a GUI for configuration options.  It also bundles up and maintains the virtual filesystem of your "C:\" drive.
  • Engine
    • Click on the "+" button in the "Installed Engines" section.
    •  
    • The latest WINE engine will be selected.  Unless you have reason to pick a specific version, just use the default.
    •  
    • Click "Download and Install" 
    • It will ask you to name the engine -- just go with the default.
    •  
    • Wait for it to download.
    •  
    • Congratulations, you now have a WINE engine.
    •  
  • Wrapper
    • Click on "Update" in the wrapper section.
    • Go with the default name and wait for it to download.
    •  

 

Create a wrapper for Artemis

 

  • Click on "Create New Blank Wrapper"
  • Give your new wrapper a name.  This is how the application will appear on your Mac.  I used Artemis plus the version number: "Aretmis-1.70"
  •  
  • Wait.  Select the defaults for whatever installation prompts come up.  (One of them is Mono, which probably isn't specifically needed by Artemis, but at at least gives you a more full-featured fake-Windows system.)
  • Eventually, you will get "Wrapper Creation Finished" and a button for "View wrapper in Finder."  Note the location (probably in the Applications/Wineskin folder of your home directory).  Click the view button and locate the wrapper app.
  •  

 

Install Artemis into the wrapper

 

  • Locate the wrapper app (probably in Applications/Wineskin in your home folder) and double-click it.
  • Since there is no main application installed, a configuration dialog appears.  Click on "Install Software" and "Choose Setup Executable."
  •  
  • Point to your Artemis installer EXE, choose the install defaults, and wait for it to install.
  •  
  • Wineskin should automatically detect the Artemis executable as being freshly installed.  Go with it.
  •  
  • Quit.

 

Launch Artemis

 

  • Locate the wrapper app (probably in Applications/Wineskin in your home folder) and double-click it.
  • If all goes well, it should launch.  You'll get a display resolution selector.  I get best results (on a Retina MacBook Pro) by using a Windowed interface instead of Full Screen.  Your mileage may vary.
  •  

 

Problems launching Artemis?

 

Occasionally I'll get the Install / Screen Options / Advanced dialog pop up instead of launching Artemis.  I'll usually just go to "Advanced" and click the "Test Run" button in the corner.  It's not elegant, but it works.  If you get an error, view the logs and Google.  Make sure you have installed your licensed version of Artemis, not one of the "updates" as the baseline.

 

 

Installing Content

 

If you need to get at the Aretmis install folder, for instance to install modules, missions, and other content:

 

  • Right-click (or Ctrl-click) on your Artemis wraper app (probably in Applications/Wineskin in your home folder) and select Show Package Contents.
  •  
  • This will bring up a Finder window that gives you access to the virtual filesystem.
  • Traverse to "drive_c", "Program Files", and "Artemis".

 

NOTE: I recommend keeping track of all file changes you make, as well as making a copy of your Artemis app before any mods have been installed. It is possible that a future update to Artemis may be incompatible with a given mod or Mission file and crash the program. It is much easier to start with a "stock" version (unmodified) of the Artemis app so you can keep playing, or for determining which mod is suspect by adding them one at a time and running Artemis after each install. You should try using both server and client modes, since some mods do not kick in until the simulation is started.

 

Instructions for installing Tre Chipman's ST_TMP mod in Wine (and Windows) can be found here.

 

If you have any questions about the Wine or Mac portions, email me

 

Updates

 

2013-03-28: With the latest Wine components and running Artemis 1.70, all stations and views seem to be working fine. Occasional, random crashes of the app have occurred during testing, but with relaunching seems to be fine.

 

Advanced Disk Space Saving and Modding Optimization

 

It is possible to have 1 directory of installed Artemis and run it from multiple environments (Parallels and/or Wineskin), achieving multiple screens with only one directory that needs to be updated for a mod.  This saves disk space for large mods and significantly reduces update time.

 

First, create a correctly installed and licensed version of the vanilla version of Artemis.  Then copy the Artemis folder to your Mac, and make copies for mods, keeping it nicely organized.

 

For Wineskin:

Using the terminal, remove (or rename) the wrapper's Artemis directory (which was installed so the license is properly registered), and create a soft link to your desired convenient and organized installation directory (that you copied and set up earlier).

 

rm {Wineskin}/Artemis_250_101_Ben.app/Contents/Resources/drive_c/Program Files/Artemis
ln -s {installation}/25101/Artemis_25101_Ben 
      {Wineskin}/Artemis_250_101_Ben.app/Contents/Resources/drive_c/Program Files/Artemis

 

For Parallels:

Remove or rename the virtual machine's Artemis directory (installed so the license is registered) and run Artemis from the network location.  You may need to copy your network location to the local VM to run Artemis as a server due to security that seems to object to network-residing applications accepting client connections.

 

Once the Wineskin wrapper and/or VM is set up, you can then copy the wrapper or VM to have multiple instances (to another machine or to get multiple wrapper windows).  When a new mod comes out, update the installation directory using your preferred method and all the "copies" are updated at the same time.

 

How to run multiple instances of Artemis in a single Wineskin.

 

Benefits: faster response, only entering server IP once for all instances.

 

  1.  Create a text file in your Artemis folder named art.bat.
    REM START JoyToKey.exe
    START Artemis.exe
    START Artemis.exe
    START Artemis.exe
     
     
     
     
  2. Change your wineskin that is configured to run Artemis (instructions above), to run nothing.exe instead. Open your wineskin holding down the Option key, and select Advanced.  
     
     
     
  3. Under Wineskin / Wineskin Advanced / Tools, use Custom EXE Creator to create an embedded wrapper app that will launch the art.bat file.  
     
     
     
     
     
    Make sure you check "Use Start.exe".  
    You may need to manually type in art.bat if the file browse does not work correctly.  
     
     
     
     
  4. Find the newly created "custom exe" and create a shortcut to it in an easy to launch location. Navigate to your wineskin app file. Right-click and show package contents.  
     
     
     
    Find the newly created art.app  
     
     
     
    Drag the file while holding down the Option and Command keys to the new location (like your desktop).  
     

 

How to use a single Wineskin to host multiple versions Artemis. (running multiple instances of the launched version)

 

  1. Set up a single wineskin for multiple instances of ONE version (above instructions).
  2. Use Terminal to create soft links to the other Artemis version installation folders. (same instructions as above)
  3. Set up art.bat files in those installation directories (the Artemis folders) - you can just copy from your original.
  4. Use the Wineskin Custom Exe Creator to create additional embedded "custom exe"'s. (same instructions as above)
  5. Create shortcuts to the new embedded "custom exe"'s. (same instructions as above)

 

 

 

 

 

Comments (0)

You don't have permission to comment on this page.