Editing Mission Editor in WINE

Jump to navigation Jump to search

Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
== Introduction ==
+
= Introduction =
 
This page is about making missions on Linux. It will document the installation of and problems with the mission editor in WINE. This guide assumes knowledge of WINE, should you not understand something it will be well documented elsewhere on the internet.
 
This page is about making missions on Linux. It will document the installation of and problems with the mission editor in WINE. This guide assumes knowledge of WINE, should you not understand something it will be well documented elsewhere on the internet.
  
== Details ==
+
= Details =
 
First create a new wineprefix. This is to ensure that there are no other applications complicating matters.
 
First create a new wineprefix. This is to ensure that there are no other applications complicating matters.
  
 
In order to install the Mission editor you must first install .net 4.0. To do this, run: (replace "(wineprefix)" with the filepath to your wineprefix)
 
In order to install the Mission editor you must first install .net 4.0. To do this, run: (replace "(wineprefix)" with the filepath to your wineprefix)
 
 
<code>
 
<code>
 
WINEPREFIX=(wineprefix) winetricks dotnet40
 
WINEPREFIX=(wineprefix) winetricks dotnet40
 
</code>
 
</code>
 
 
Download the mission editor executable [http://zero-k.info/missioneditor/setup.exe here]. From a terminal at the location of the downloaded file, run: (replacing "(wineprefix)" again)
 
Download the mission editor executable [http://zero-k.info/missioneditor/setup.exe here]. From a terminal at the location of the downloaded file, run: (replacing "(wineprefix)" again)
 
 
<code>
 
<code>
 
WINEPREFIX=(wineprefix) wine MissionEditor.exe
 
WINEPREFIX=(wineprefix) wine MissionEditor.exe
 
</code>
 
</code>
 
 
You will likely have to give the executable permission to run as a program.
 
You will likely have to give the executable permission to run as a program.
  
 
You now have the mission editor installed. Run the executable you downloaded with the above command whenever you want to run it.
 
You now have the mission editor installed. Run the executable you downloaded with the above command whenever you want to run it.
  
== Bugs ==
+
= Bugs =
 
There are a few bugs with this:
 
There are a few bugs with this:
 
* You must run this program WITHOUT a virtual desktop. If run in a virtual desktop you will have to reboot every time you wish to open the mission editor.
 
* You must run this program WITHOUT a virtual desktop. If run in a virtual desktop you will have to reboot every time you wish to open the mission editor.

Please note that all contributions to Zero-K are considered to be released under the Creative Commons Attribution-ShareAlike (see Zero-K:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

Cancel Editing help (opens in new window)