Difference between revisions of "Running Oolite-Windows"
m (Update download link) |
m (→Errata) |
||
Line 17: | Line 17: | ||
===Errata=== |
===Errata=== |
||
− | There was a problem in the 1.62 build that caused memory exhaustion. [http://www.aegidian.org/bb/viewtopic.php?t=1416 Please read this page] to find out how to manually patch the Windows installation. |
+ | There was a problem in the 1.62 build that caused memory exhaustion. [http://www.aegidian.org/bb/viewtopic.php?t=1416 Please read this page] to find out how to manually patch the Windows installation. Users of later builds (for example, the current -344 build on the BerliOS site) will not suffer from this issue. |
==Running the game== |
==Running the game== |
Revision as of 11:48, 28 March 2006
Contents
Overview
The Windows port of Oolite is built from the same source as the Linux and OS-X versions, and has all the features of those versions.
All OXPs should be compatible with the Windows port.
Getting and installing the game
The game may be downloaded from the BerliOS project page for Oolite-PC.
To install, run the executable that you have just downloaded. You will get the familiar Windows installer.
Note that the installer was mirrored on alioth.net, but this site has not kept up to date with the later builds.
A regular build of changes from the SVN source is being carried out on a regular basis. The complete installer above must be installed before any of the updates will work. The update filename changes with each build, so get the latest update file by following the link here: [1].
The game has been tested on Windows XP and Windows 2000. It will not run on the DOS-extender versions of Windows such as Windows 95, 98 or ME. It is expected it will run with Vista, so long as drivers are available for the hardware you have. You are advised to run the latest 3D graphics drivers from your 3D card manufacturer.
Errata
There was a problem in the 1.62 build that caused memory exhaustion. Please read this page to find out how to manually patch the Windows installation. Users of later builds (for example, the current -344 build on the BerliOS site) will not suffer from this issue.
Running the game
Find the Oolite icon in the Start -> Programs menu and click on it. Alternatively double click the Oolite program icon on the desktop.
Installing OXPs
You will need to find where the oolite.app folder is placed: it should be in C:\Program Files\Oolite. Create an AddOns folder beside the oolite.app folder. Put OXPs in here. Note that some OXPs when unzipped contain a folder with a README file and then the OXP - in this case, it's best to unzip the OXP somewhere other than AddOns and copy the OXP folder once unpacked into AddOns.
Notes for amd64 users
No builds for 64-bit versions of Windows have yet been made, however, given the proper availability of graphics and sound drivers, the 32-bit version should run on 64-bit Windows. 32 bit Windows running on amd64 hardware should not have an issue.
Building Oolite from source
- Download and install the necessary software
- Get the source and build it (note, the source comes from the oolite-linux project)
- Start the GNUstep command line (Start -> Programs -> GNUstep Development -> MSYS for GNUstep) and issue the following commands:
cd $GNUSTEP_LOCAL_ROOT
export PATH=$PATH:$GNUSTEP_LOCAL_ROOT/bin
mkdir oolite
cd oolite
svn checkout svn://svn.berlios.de/oolite-linux/trunk
cd trunk
make
- To run the game in the build environment:
- Before running the first time:
cp $GNUSTEP_LOCAL_ROOT/bin/*.dll oolite.app
openapp oolite.app
- Before running the first time:
Assuming you have installed one of Nic's releases as detailed above, you can easily keep updating the installation from the latest source. In the $GNUSTEP_LOCAL_ROOT/oolite/trunk
directory, issue the commands:
export PATH=$PATH:$GNUSTEP_LOCAL_ROOT/bin
svn up
rm -rf oolite.app/Resources; make
You only need to issue the export PATH command when you first start the command line. The rm -rf command before make is required because GNUstep for Windows cannot parse the XML plist file format, and the build fails when it tries to read one of these generated each time the build is performed. This failure is not important, and the process still works, but it is annoying.
Then use the following script to copy the new files over the existing installation:
OA="/c/Program Files/Oolite/oolite.app" cd $GNUSTEP_LOCAL_ROOT/oolite/trunk if [ oolite.app/oolite.exe -nt "$OA/oolite.exe" ]; then echo "Updating oolite.exe" cp oolite.app/oolite.exe "$OA/oolite.exe" fi for a in AIs Config Images Models Music Sounds Textures; do for b in Resources/$a/*; do c=`basename $b` if [ $b -nt "$OA/Contents/Resources/$a/$c" ]; then echo "Updating with $b" cp $b "$OA/Contents/Resources/$a/$c" fi done done
Also see the Oolite-PC forum: [5]