User Tools

Site Tools


en:games:star_trek_-_voyager_eliteforce

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
en:games:star_trek_-_voyager_eliteforce [2019-08-11-15-20]
127.0.0.1 external edit
en:games:star_trek_-_voyager_eliteforce [2020-02-21-23-08] (current)
7saturn [Where do my settings/mods/maps go during play/download?]
Line 3: Line 3:
   * [[https://​www.moddb.com/​games/​star-trek-voyager-elite-force/​addons/​map-package-for-ef-classic-mobile-infanterie|Mappack for Mobile Infanterie]]   * [[https://​www.moddb.com/​games/​star-trek-voyager-elite-force/​addons/​map-package-for-ef-classic-mobile-infanterie|Mappack for Mobile Infanterie]]
   * [[https://​maps.mobile-infanterie.de/​|Maps for Mobile Infanterie]] (map-repo for direct and curl downloads)   * [[https://​maps.mobile-infanterie.de/​|Maps for Mobile Infanterie]] (map-repo for direct and curl downloads)
-  * [[https://​www.mobile-infanterie.de/​lilium-voyager/​lilium_voyager_1_39_win32_x86_2019-05-12.7z|Lilium Voyager Version 1.39, Win32, x86]] +  * [[https://​www.mobile-infanterie.de/​lilium-voyager/​lilium_voyager_1_40_win32_x86_2019-12-30.7z|Lilium Voyager Version 1.40, Win32, x86]] 
-  * [[https://​www.mobile-infanterie.de/​lilium-voyager/​lilium_voyager_1_39_win32_x64_2019-05-12.7z|Lilium Voyager Version 1.39, Win32, x64]] +  * [[https://​www.mobile-infanterie.de/​lilium-voyager/​lilium_voyager_1_40_win32_x64_2019-12-30.7z|Lilium Voyager Version 1.40, Win32, x64]] 
-  * [[https://​www.mobile-infanterie.de/​lilium-voyager/​lilium_voyager_1_39_linux_x86_2019-05-12.7z|Lilium Voyager Version 1.39, Linux, x86]] +  * [[https://​www.mobile-infanterie.de/​lilium-voyager/​lilium_voyager_1_40_linux_x86_2019-12-30.7z|Lilium Voyager Version 1.40, Linux, x86]] 
-  * [[https://​www.mobile-infanterie.de/​lilium-voyager/​lilium_voyager_1_39_linux_x64_2019-05-12.7z|Lilium Voyager Version 1.39, Linux, x64]] +  * [[https://​www.mobile-infanterie.de/​lilium-voyager/​lilium_voyager_1_40_linux_x64_2019-12-30.7z|Lilium Voyager Version 1.40, Linux, x64]] 
-  * [[https://​www.mobile-infanterie.de/​lilium-voyager/​lilium_voyager_1_39_macos_x64_2019-05-12.7z|Lilium Voyager Version 1.39, MacOS, x64]]+  * [[https://​www.mobile-infanterie.de/​lilium-voyager/​lilium_voyager_1_40_macos_x64_2019-12-30.7z|Lilium Voyager Version 1.40, MacOS, x64]]
   * <​del>​[[http://​thilo.kickchat.com/​efport-progress/​bin|Elite Force - Patch 1.38 (Thilo)]]</​del>​ (went offline)   * <​del>​[[http://​thilo.kickchat.com/​efport-progress/​bin|Elite Force - Patch 1.38 (Thilo)]]</​del>​ (went offline)
   * [[http://​beer-garden.n5net.com/​downloads/?​lid=65|Elite Force - installer incl. version 1.2]]   * [[http://​beer-garden.n5net.com/​downloads/?​lid=65|Elite Force - installer incl. version 1.2]]
Line 162: Line 162:
 === What's that? === === What's that? ===
 Since Thilo has stopped maintaining his EF patches at some point, there are no newer versions of him than the 1.38 RC 1. And even this one is no longer to be found on his former pages. His work is continued by Zack Middleton in the form of the project "​Lilium Voyager"​. Since Thilo has stopped maintaining his EF patches at some point, there are no newer versions of him than the 1.38 RC 1. And even this one is no longer to be found on his former pages. His work is continued by Zack Middleton in the form of the project "​Lilium Voyager"​.
-=== Where to get ===+=== Where to get it ===
 The source files can be found [[https://​github.com/​zturtleman/​lilium-voyager|here]]. You can also find them precompiled in the [[#​Downloads]] above. The source files can be found [[https://​github.com/​zturtleman/​lilium-voyager|here]]. You can also find them precompiled in the [[#​Downloads]] above.
-=== Where do my settings go? ===+=== Where do my settings/​mods/​maps ​go during play/​download? ===
 The settings on the three major systems, Windows, Linux and MacOS, are stored here: The settings on the three major systems, Windows, Linux and MacOS, are stored here:
   * Linux: ''​~/​.local/​share/​lilium-voyager/​baseEF'',​   * Linux: ''​~/​.local/​share/​lilium-voyager/​baseEF'',​
Line 170: Line 170:
   * MacOS: ''​~/​Library/​Application Support/​Lilium Voyager/​baseEF''​   * MacOS: ''​~/​Library/​Application Support/​Lilium Voyager/​baseEF''​
 or in the corresponding mod folders. or in the corresponding mod folders.
 +
 +On ioQuake derived versions there is also the possibility to explicitly tell the game, where to look for and place downloaded data. This is done by setting the variable ''​fs_homepath''​ during server or client start. For example
 +
 +''​./​liliumvoyhm.x86_64 +set fs_homepath ~/​my_ef_folder''​
 +
 +makes the game look for data in the  folder ''​my_ef_folder''​ in the current user's home folder (for Linux systems). This way it is possible, to kind of have multiple EF installations separately, e. g. with different (incompatible) mods active while actually having it installed just once. Files present inside the games installation folder, e. g. ''​*.pk3''​ files, are always found. So for running different mods with the same installation it is advisable, to strictly separate the configurations and mod files in different folders, whil having only the basic game with only its original files inside the installation folder.
 === Building it yourself === === Building it yourself ===
-As written above, only the source files are published. You have to compile the executables ("​binaries"​) yourself. How this works for Quake 3 and derived games (32 and 64 bit, different platforms) is well described ​on the subpages ​of [[http://wiki.ioquake3.org/Building_ioquake3|this page]]. Please note that the description ​is for ioQuake3, i.ethe git links are not for Lilium Voyagerbut for ioQuake3For the source files of Lilium Voyager please use [[https://​github.com/​zturtleman/​lilium-voyager|these sources]]. For cross-compiling from Linux to Windows MingW is necessary. ​A bold ''​sudo apt-get install mingw-w64'' ​may be necessary beforehand ​(for Debian & derived distributions...).+As written above, only the source files are published. You have to compile the executables ("​binaries"​) yourself. How this works for Quake 3 and derived games (32 and 64 bit, different platforms) is described ​below. 
 + 
 +For the source files of Lilium Voyager please use [[https://github.com/zturtleman/​lilium-voyager|these sources]]. The git URL is ''​https://​github.com/​zturtleman/​lilium-voyager.git''​. 
 +== Linux == 
 +On Linux it is possible to build for both variationsx86 and amd64. It is also possible to cross compile ​for Windows (32 and 64 bit), see next section for thatTo compile on Linux you require ​the following prerequisites installed:​ 
 + 
 +  * ''​git''​ (versioning tool) and 
 +  * ''​libsdl2-dev''​ (SDL 2 development package). 
 + 
 +Once you have installed these packages, you can start with cloning the git repository on the console, containing the EF sources, like this: 
 + 
 +''​git clone https://​github.com/​zturtleman/​lilium-voyager.git''​ 
 + 
 +It will download the new source files to a newly created folder ''​lilium-voyager''​. Switch to it and run ''​make''​. This will build EF for your own platform. The resulting binaries will be placed inside the subfolder ''​build'',​ e. g. for an AMD 64 architecture the folder ''​release-linux-x86_64''​ will be created. From there you only need the following four files: 
 + 
 +  * ''​liliumvoyded.x86_64''​ (dedicated server binary, used to set up a server), 
 +  * ''​liliumvoyhm_renderer_opengl1_x86_64.so''​ (graphics library), 
 +  * ''​liliumvoyhm_renderer_opengl2_x86_64.so''​ (graphics library), 
 +  * ''​liliumvoyhm.x86_64''​ (client binary, used to play on a server). 
 + 
 +If you want to update an already existing Lilium Voyager folder, just run ''​git pull''​ for updating the source repository and run ''​make clean''​ (removing files created during earlier run) and afterwards ''​make''​ to run the compilation process again. 
 + 
 +If you want to create binaries for another architecture than you own (e. g. compile x86 binaries on an amd64 system), you can specify this with the ''​ARCH''​ property. For the former example the command would be 
 + 
 +''​make ARCH=x86''​. 
 + 
 +So what ''​make''​ actually does on an amd64 system is the same as ''​make ARCH=x86_64''​. 
 + 
 +== Cross compile for Windows via Linux == 
 +For cross-compiling from Linux to Windows ​the MingW environment ​is necessary. ​Use something like ''​sudo apt-get install mingw-w64'' ​for x64 or ''​sudo apt-get install mingw''​ for x86 Linux (here: for Debian & derived distributions...) ​to install it. Then run the compilation process like this: 
 + 
 +''​make PLATFORM=mingw32 ARCH=x86_64''​ (64 bit) or 
 + 
 +''​make PLATFORM=mingw32 ARCH=x86''​ (32 bit). 
 +== MacOS == 
 +You will need to run the bash on MacOS and also install git. Check out the source files from the git repository as described for Linux. Then run the following command: 
 + 
 +''​./​make-macosx.sh x86_64''​. 
 + 
 +As MacOS today only comes as 64 bit version, this should be all you need. From the results in the build directory, you will only need the following elements: 
 + 
 +  * ''​Lilium Voyager.app''​ (Quick starter for the game) or 
 +  * ''​liliumvoyded.x86_64''​ (for setting up a dedicated server), 
 +  * ''​liliumvoyhm_renderer_opengl1_x86_64.dylib''​ (graphics library), 
 +  * ''​liliumvoyhm_renderer_opengl2_x86_64.dylib''​ (graphics library), 
 +  * ''​liliumvoyhm.x86_64''​ (game binary) and 
 +  * ''​libSDL2-2.0.0.dylib''​ (SDL library). 
 + 
 +If you're running Mac OS 10.6.x and have the Mac OS 10.5 developer SDK you can make a universal binary for ppc, x86, and x86_64 that is compatible with OS X 10.5 or later Mac OS versions. 
 + 
 +  * Remove the build directory if you previously built ioq3 using make, because it defaults to 10.7 compatibility. 
 +* Run ''​./​make-macosx-ub.sh''​ 
 + 
 +If you're running Mac OS 10.7 or newer you can build a x86 / x86_64 universal binary that is compatible with 10.7 or later. (Not particularly useful since all Mac OS 10.7 and later are x86_64.) 
 + 
 +  * Run ''​make ARCH=x86''​ or 
 +  * ''​make ARCH=x86_64''​ and 
 +  * run ''​./​make-macosx-app.sh release''​. 
 +== Windows - msys2 == 
 +**64-Bit Binaries** 
 + 
 +To build 64-bit binaries, follow these instructions:​ 
 + 
 +  - Ordered List ItemInstall msys2 from https://​msys2.github.io/​ , following the instructions there. It doesn'​t matter which version you download, just get one appropriate for your OS. 
 +  - Start "MSYS2 MinGW 64-bit"​ from the Start Menu. 
 +  - Install mingw-w64-x86_64:​ ''​pacman -S mingw-w64-x86_64-gcc''​ 
 +  - Install make: ''​pacman -S make''​ 
 +  - Grab latest ioq3 source code from github. Use git, or just grab https://​github.com/​ioquake/​ioq3/​archive/​master.zip and unzip it somewhere. 
 +  - Change directory to where you put the source and run make. Note that in msys2, your drives are linked as folders in the root directory: C:\ is /c/, D:\ is /d/, and so on: 
 +<​code>​cd /c/ioq3 
 +make ARCH=x86_64</​code>​ 
 +  - Find the executables and dlls in ''​build/​release-mingw64-x86_64''​. 
 +**32-Bit Binaries** 
 + 
 +To build 32-bit binaries, follow these instructions:​ 
 +  - Install msys2 from https://​msys2.github.io/,​ following the instructions there. It doesn'​t matter which version you download, just get one appropriate for your OS. 
 +  - Start "MSYS2 MinGW 32-bit"​ from the Start Menu. 
 +  - Install mingw-w64-i686-gcc:​ ''​pacman -S mingw-w64-i686-gcc''​ 
 +  - Install make from msys: ''​pacman -S make''​ 
 +  - Grab latest ioq3 source code from github Use git, or just grab https://​github.com/​ioquake/​ioq3/​archive/​master.zip and unzip it somewhere. 
 +  - Change directory to where you put the source and run make. Note that in msys2, your drives are linked as folders in the root directory: C:\ is /c/, D:\ is /d/, and so on. 
 +<​code>​cd /c/ioq3 
 +make ARCH=x86 WINDRES="​windres -F pe-i386"</​code>​ 
 +  - Find the executables and dlls in build/​release-mingw32-x86 .  
 +== Windows - cygwin == 
 +**1. Install Cygwin** 
 + 
 +Download the Cygwin setup package from http://​cygwin.com/​install.html. 
 + 
 +Choose either the 32-bit or 64-bit environment. 32-bit will work fine on both 32 and 64 bit versions of Windows. The setup program is also your Cygwin environment updater. If you have an existing Cygwin environment,​ the setup program will, by default, update your existing packages. 
 + 
 +Choose where you want to install Cygwin. The entire environment is self-contained in it's own folder, but you can also interact with files from outside the environment if you want to as well. The default install path is ''​C:​\Cygwin''​. 
 +  - Choose a mirror to download packages from, such as the kernel.org mirrors. 
 +  - Choose a "​storage area" for your package downloads. 
 + 
 +**2. Package selection** 
 + 
 +The next screen you see will be the package selections screen. In the upper left is a search box. This is where you will want to search for the necessary packages. 
 + 
 +These are the package names you'll want to search for: 
 + 
 +  * ''​mingw64-i686-gcc-core''​ (for building 32bit binaries),​ 
 +  * ''​mingw64-i686-gcc-g++''​ (also for 32bit... C++ support... not required for ioquake3, but useful for compiling other software),​ 
 +  * ''​mingw64-x86_64-gcc-core''​ (for building 64bit binaries),​ 
 +  * ''​mingw64-x86_64-gcc-g++''​ (for 64bit, same as above), 
 +  * ''​make'',​ 
 +  * ''​bison''​ and 
 +  * ''​git''​. 
 + 
 +When you search for your packages you'll see category listings. These packages would all be under the "​Devel"​ category. 
 + 
 +To select a package, change the '​Skip'​ to the version of the package you want to install. The first click will be the newest version and subsequent clicks will allow you to choose older versions of the package. In our case here, you're probably good choosing the latest and greatest. 
 + 
 +**3. Install packages** 
 + 
 +After you have selected your packages, just hit '​Next'​ in the lower right. Cygwin will automatically add package dependencies. Hit next again to let the install run. Done. 
 + 
 +The entire environment uses about 1GB of disk space (as opposed to about 6GB for a Visual Studio install). 
 + 
 +**4. Using Cygwin to check out and build ioquake3** 
 + 
 +After the install has completed you should have a '​Cygwin Terminal'​ icon on your Desktop. This is the bash shell for Cygwin, so go ahead and run it. 
 + 
 +At the command prompt type: ''​git clone https://​github.com/​zturtleman/​lilium-voyager.git''​ 
 + 
 +This will download the Lilium Voyager master branch source into a new ''​lilium-voyager''​ folder. 
 + 
 +Change to the folder that was created: ''​cd lilium-voyager''​ 
 + 
 +You can build EF for 32 or 64 bit Windows by running one of the following 
 + 
 +  * ''​make ARCH=x86''​ (32 bit) or 
 +  * ''​make ARCH=x86_64''​ (64 bit). 
 + 
 +After the build completes the output files will be in the ''​build''​ folder. The path would be ''​C:​\Cygwin\home\<​nowiki><​username></​nowiki>​\lilium-voyager\build\release-mingw32-arch''​ for the default Cygwin install.
 ===== Graphic settings ===== ===== Graphic settings =====
 There is not much to say about the individual graphic settings in ''​graphic data''​. The effects should be known. However, the brightness control described in the next section can be found in ''​Graphic data II'',​ if something needs to be readjusted. There is not much to say about the individual graphic settings in ''​graphic data''​. The effects should be known. However, the brightness control described in the next section can be found in ''​Graphic data II'',​ if something needs to be readjusted.
Line 1115: Line 1255:
 Apparently there is an additional mechanism in Eliteforce which is probably intended to explicitly withdraw from the master server. This is done with the following string: ''​ÿÿÿÿheartstop\27960\gamename\STEF1\''​. Also here the digit series ''​27960''​ is the port of the logging out game server. This logout is actually not necessary and deviates from the original Quake 3 implementation,​ see previous section [[#Announce Game Server to Masterserver (Heartbeat)]]. Apparently there is an additional mechanism in Eliteforce which is probably intended to explicitly withdraw from the master server. This is done with the following string: ''​ÿÿÿÿheartstop\27960\gamename\STEF1\''​. Also here the digit series ''​27960''​ is the port of the logging out game server. This logout is actually not necessary and deviates from the original Quake 3 implementation,​ see previous section [[#Announce Game Server to Masterserver (Heartbeat)]].
 == Server List Query == == Server List Query ==
-The query of the game servers known to the master server by a client is initiated as follows: ''​ÿÿÿÿtservers ​xx'',​ with ''​xx''​ as a numeric specification of the game protocol version. For Eliteforce since version 1.2 this is ''​24''​. Version 0.28 still had ''​22''​ as specification. Furthermore,​ the query can be extended by the extensions ''​full''​ (also returns full servers) and ''​empty''​ (also returns empty servers) (separated by space 0x20, ASCII character no. 32). A query that returns all Eliteforce 1.2 servers that the master server knows would look like this: ''​ÿÿÿÿgetservers 24 empty full''​.+The query of the game servers known to the master server by a client is initiated as follows: ''​ÿÿÿÿgetservers ​xx'',​ with ''​xx''​ as a numeric specification of the game protocol version. For Eliteforce since version 1.2 this is ''​24''​. Version 0.28 still had ''​22''​ as specification. Furthermore,​ the query can be extended by the extensions ''​full''​ (also returns full servers) and ''​empty''​ (also returns empty servers) (separated by space 0x20, ASCII character no. 32). A query that returns all Eliteforce 1.2 servers that the master server knows would look like this: ''​ÿÿÿÿgetservers 24 empty full''​.
 == Server List Response == == Server List Response ==
 The answer to the client then looks like this: The answer to the client then looks like this:
Line 1237: Line 1377:
   * [[http://​www.bradandsandra.com/​stvef/​index.html|Basic configuration for an Elite Force Linux dedicated server version 1.2]]   * [[http://​www.bradandsandra.com/​stvef/​index.html|Basic configuration for an Elite Force Linux dedicated server version 1.2]]
   * [[http://​gagius.co.uk/​eliteforce.html]]:​ Page with bomb defusing mod, a master server and a master server query tool.   * [[http://​gagius.co.uk/​eliteforce.html]]:​ Page with bomb defusing mod, a master server and a master server query tool.
 +  * [[http://​wwazman2001.tripod.com/​voyager/​index.html]]:​ Page with some Maps of a certain Eric Sahlstrom (really awesomly old school)
   * [[http://​amp.denofgeek.com/​us/​games/​star-trek/​273174/​star-trek-the-activision-years-and-the-making-of-elite-force-i-ii|Interview with the developers of EF 1 and 2]]   * [[http://​amp.denofgeek.com/​us/​games/​star-trek/​273174/​star-trek-the-activision-years-and-the-making-of-elite-force-i-ii|Interview with the developers of EF 1 and 2]]
   * [[https://​www.stvef.org]] Beautiful page with background info about EF, and also some mods.   * [[https://​www.stvef.org]] Beautiful page with background info about EF, and also some mods.
en/games/star_trek_-_voyager_eliteforce.1565529644.txt.gz · Last modified: 2019-08-11-15-20 by 127.0.0.1