VsWiki - User contributions [en]

HowTo:Compile from SVN on Linux

2008-10-20T04:01:54Z

Nachtwolf: /* Requirements */ oops, forgot to remove inetutils

{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
----
How to compile from SVN under Linux.

''See also: [[HowTo:Cygwin Compiling]], [[HowTo:VCPP Compiling]]''

==Getting the SVN-files==

* Checkout the following modules ...
** data package: '''data''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data)
** code package: '''vegastrike''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike)
* Visit [[HowTo:Checkout SVN]] to see how you check these modules out.

==Requirements==
In order to compile Vegastrike there are a few things to check:
* Make sure you have these packages installed ...
** '''make'''
** '''gcc'''
** '''automake''' at least version 1.6
** '''autoconf''' at least version 2.53
** '''X11'''...
** '''libpng''' + '''libpng-devel''' <-- libpng 3 is recommended.
** '''python''' and '''python-dev''' <-- 2.2.1
** '''expat''' + '''expat-devel'''
** '''(lib)jpeg''' + '''libjpeg-devel'''
** '''opengl''' (see below) (you probably already have it)
** '''glut''' + '''glut-devel'''
** '''openal''' + '''openal-devel'''
** '''libgtk2.0''' + '''libgtk2.0-devel'''

This probably should do the trick in debian/ubuntu:

<pre>
sudo apt-get install libpng12-0 libpng12-dev python2.5-dev libexpat1-dev \
libjpeg62-dev glutg3-dev libopenal-dev libgtk2.0-dev \
build-essential libgl1-mesa-dev automake autoconf
</pre>

==Compiling==
The compile procedure should look like the following listing. Remember the configure part depends on above requirements. Though autoconf may not work, if so just skip it.
<pre>
cd ./vegastrike
./bootstrap-sh
./configure --enable-debug
make
make install # [AS ROOT]
</pre>

* To be sure '''set the data dir''' to your vs-data dir:
<pre>
./configure --with-data-dir=<DIR> ........
</pre>
* When using '''libpng 1.2''',
<pre>
--with-png-inc=<DIR>
</pre>
is needed. An example is
<pre>
--with-png-inc=/usr/include/libpng12/
</pre>
* If you don't want to compile with '''GTK''' just turn it off, however you will not get a setup program if you do this:
<pre>
./configure --disable-gtk ...........
</pre>
* If you only want the server, and want to disable all GUI components--This removes the dependency on X11, OpenGL, SDL, GLUT, OpenAL.
<pre>
./configure --disable-client ...........
</pre>
* See [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=1147 this] thread about boost versions. Set this option to 1.28, 1.29, 1.33, or "system" if the default does not compile.
<pre>
./configure --with-boost=<VER> ...........
</pre>

You will likely receive some error messages during any of these stages, especially during the configure part. If they tell you that your system is missing some development libraries, install them. How this is done depends strongly on your Linux distribution, but we will assist you in the [http://vegastrike.sourceforge.net/forums/viewforum.php?f=5 Compiling Problems forums]. You will be left with a file called "config.log" please attach that instead of copy-and-pasting thousands of lines of error messages. It's all in this file.

After you installed the missing libraries repeat the last (failed) step and continue.

'''Note:''' The configure script currently has a bug that can cause it to incorrectly report on the absence of GLUT. If you are sure you have installed glut-devel and are still seeing this error, check near the end of config.log to see if another library (such as libxmu or libxi) is the true culprit. [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=7562]

===Make===
Th final step for compiling is the make command. The Makefile should be able to compile most of the included utilities.

To compile mesher, for example, type:
<pre>make mesher</pre>
* Running
<pre>make all-am</pre>
reduces memory usage while compiling because there's only one instance of make instead of two. From [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=9510 this forum thread].
* The step
<pre>
make install
</pre>
is optional as the program is quite happy running in userland.

=See also=
* [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=4185 "make clean/distclean" thread in the forum] - A quite helpful thread about the make process.

----
{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
[[Category:HowTos|Compile from CVS]]

HowTo:Compile from SVN on Linux

2008-10-20T04:01:19Z

Nachtwolf: /* Requirements */ updated dependencies and took out inetutils entry that I think was intended for Cygwin users

{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
----
How to compile from SVN under Linux.

''See also: [[HowTo:Cygwin Compiling]], [[HowTo:VCPP Compiling]]''

==Getting the SVN-files==

* Checkout the following modules ...
** data package: '''data''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data)
** code package: '''vegastrike''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike)
* Visit [[HowTo:Checkout SVN]] to see how you check these modules out.

==Requirements==
In order to compile Vegastrike there are a few things to check:
* Make sure you have these packages installed ...
** '''make'''
** '''gcc'''
** '''automake''' at least version 1.6
** '''autoconf''' at least version 2.53
** '''X11'''...
** '''libpng''' + '''libpng-devel''' <-- libpng 3 is recommended.
** '''python''' and '''python-dev''' <-- 2.2.1
** '''expat''' + '''expat-devel'''
** '''(lib)jpeg''' + '''libjpeg-devel'''
** '''opengl''' (see below) (you probably already have it)
** '''glut''' + '''glut-devel'''
** '''openal''' + '''openal-devel'''
** '''libgtk2.0''' + '''libgtk2.0-devel'''

This probably should do the trick in debian/ubuntu:

<pre>
sudo apt-get install libpng12-0 libpng12-dev python2.5-dev libexpat1-dev \
libjpeg62-dev glutg3-dev libopenal-dev libgtk2.0-dev inetutils-inetd \
build-essential libgl1-mesa-dev automake autoconf
</pre>

==Compiling==
The compile procedure should look like the following listing. Remember the configure part depends on above requirements. Though autoconf may not work, if so just skip it.
<pre>
cd ./vegastrike
./bootstrap-sh
./configure --enable-debug
make
make install # [AS ROOT]
</pre>

* To be sure '''set the data dir''' to your vs-data dir:
<pre>
./configure --with-data-dir=<DIR> ........
</pre>
* When using '''libpng 1.2''',
<pre>
--with-png-inc=<DIR>
</pre>
is needed. An example is
<pre>
--with-png-inc=/usr/include/libpng12/
</pre>
* If you don't want to compile with '''GTK''' just turn it off, however you will not get a setup program if you do this:
<pre>
./configure --disable-gtk ...........
</pre>
* If you only want the server, and want to disable all GUI components--This removes the dependency on X11, OpenGL, SDL, GLUT, OpenAL.
<pre>
./configure --disable-client ...........
</pre>
* See [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=1147 this] thread about boost versions. Set this option to 1.28, 1.29, 1.33, or "system" if the default does not compile.
<pre>
./configure --with-boost=<VER> ...........
</pre>

You will likely receive some error messages during any of these stages, especially during the configure part. If they tell you that your system is missing some development libraries, install them. How this is done depends strongly on your Linux distribution, but we will assist you in the [http://vegastrike.sourceforge.net/forums/viewforum.php?f=5 Compiling Problems forums]. You will be left with a file called "config.log" please attach that instead of copy-and-pasting thousands of lines of error messages. It's all in this file.

After you installed the missing libraries repeat the last (failed) step and continue.

'''Note:''' The configure script currently has a bug that can cause it to incorrectly report on the absence of GLUT. If you are sure you have installed glut-devel and are still seeing this error, check near the end of config.log to see if another library (such as libxmu or libxi) is the true culprit. [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=7562]

===Make===
Th final step for compiling is the make command. The Makefile should be able to compile most of the included utilities.

To compile mesher, for example, type:
<pre>make mesher</pre>
* Running
<pre>make all-am</pre>
reduces memory usage while compiling because there's only one instance of make instead of two. From [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=9510 this forum thread].
* The step
<pre>
make install
</pre>
is optional as the program is quite happy running in userland.

=See also=
* [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=4185 "make clean/distclean" thread in the forum] - A quite helpful thread about the make process.

----
{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
[[Category:HowTos|Compile from CVS]]

SandBox

2008-10-11T10:04:40Z

Nachtwolf: test edits

Welcome to the SandBox:

test

Here you can practice your wiki skills!

= Templates! =
{{SandBox|En|SandBox}}

= Header #1 =
== Double header ==
=== Triple header ===
=== Triple header ===
== Double header ==
= Header #2 =
== Subsection ==
=== Subsubsection ===
==== Subsubsubsection ====
===== Subsubsubsubsection =====
====== Subsubsubsubsubsection ======
======= Subsubsubsubsubsubsection =======
======== Subsubsubsubsubsubsubsection ========

= Wiki content =
== Lists ==
* list 1
* list 2
* list 5
** (Three, sir, three)
Bulleted lists:
* * Bulleted lists
* # Numbered lists
Numbered lists:
# List item
# List item
## List temp
##* Bulleted list in a numbered list. Ooh tricky! I want one!

== Formatting ==
* ''Italic''
** ''Text to make italic''
* Underline
** Text to make underlined
* '''Bold'''
** '''Text to make bold'''

== Headers ==
* = Top Level Header =
* == Second-level Header ==
* === Third-level header ===
* etc. etc. etc.

== Templates ==
* Use <nowiki>{{XX ...}}</nowiki> to include a template named "Template:XX".
* Example: <nowiki>{{Key:Up}}</nowiki> would be {{Key:Up}}

== Thumbnails ==
Using thumbnails from gallery v2 is more difficult than using ones from gallery v1. See [[VsWiki:Manual_of_Style#Images]] for info on how to use gallery v2 thumbnails in the wiki.

http://vegastrike.sourceforge.net/albums/wiki_manual/APPLE_GENERAL.png

== Linking to the forum ==
* Use <nowiki>[http://vegastrike.sourceforge.net/forums/ This is a link to the forums]</nowiki> Note the space between the end of the address and the link text.

[http://vegastrike.sourceforge.net/forums/ This is a link to the forums]. - [[User:Stevie D|Stevie D]] 03:06, 31 October 2006 (PST)

Vessels and Installations

2008-10-11T10:03:07Z

Nachtwolf: Vessels & Installations moved to Vessels and Installations

{{Languages|En|Vessels & Installations}}
[[Category:Database]] [[Category:VS Tech]] [[Category:Vessels]] [[Category:Cargo|Vessels]][[Category:Cargo:Vessels|Vessels]][[Category:Installations]]
{{NAV_Database |
| previous=[[Factions]]
| up=[[Database]]
| next=[[Upgrades]]
}}
----
{{warning_text |
| text= Please see the '''Talk page'''
}}

=Vessels & Installations=
==By Associated Vessel Category==
(categories are not disjoint)
{|
|
* [[:Category:Vessels:Aerospace|Aerospace]]
* [[:Category:Vessels:Assault|Assault]]
* [[:Category:Vessels:Atmospheric|Atmospheric]]
* [[:Category:Vessels:Battle Cruiser|Battle Cruiser]]
* [[:Category:Vessels:Battleship|Battleship]]
* [[:Category:Vessels:Boarding Craft|Boarding Craft]]
* [[:Category:Vessels:Bomber|Bomber]]
* [[:Category:Vessels:Capital Escort|Capital Escort]]
* [[:Category:Vessels:Cargo|Cargo]]
* [[:Category:Vessels:Carrier|Carrier]]
* [[:Category:Vessels:Civilian|Civilian]]
* [[:Category:Vessels:Colonization|Colonization]]
* [[:Category:Vessels:Commerce Raider|Commerce Raider]]
* [[:Category:Vessels:Corvette|Corvette]]
|width="100pt"|
|
* [[:Category:Vessels:Courier|Courier]]
* [[:Category:Vessels:Cruiser|Cruiser]]
* [[:Category:Vessels:Destroyer|Destroyer]]
* [[:Category:Vessels:Diplomatic|Diplomatic]]
* [[:Category:Vessels:Dreadnaught|Dreadnaught]]
* [[:Category:Vessels:Enforcement|Enforcement]]
* [[:Category:Vessels:Exploration|Exploration]]
* [[:Category:Vessels:Fighter|Fighter]]
* [[:Category:Vessels:Frigate|Frigate]]
* [[:Category:Vessels:Gunboat|Gunboat]]
* [[:Category:Vessels:Insystem|Insystem]]
* [[:Category:Vessels:Interceptor|Interceptor]]
* [[:Category:Vessels:Mass Transit|Mass Transit]]
* [[:Category:Vessels:Military|Military]]
|width="100pt"|
|
* [[:Category:Vessels:Orbital|Orbital]]
* [[:Category:Vessels:Passenger|Passenger]]
* [[:Category:Vessels:Patrol|Patrol]]
* [[:Category:Vessels:Personal Transport|Personal Transport]]
* [[:Category:Vessels:Racing|Racing]]
* [[:Category:Vessels:Reconnaissance|Reconnaissance]]
* [[:Category:Vessels:Resource Gathering|Resource Gathering]]
* [[:Category:Vessels:Salvage|Salvage]]
* [[:Category:Vessels:Seige|Seige]]
* [[:Category:Vessels:Service|Service]]
* [[:Category:Vessels:Support|Support]]
* [[:Category:Vessels:Terraforming|Terraforming]]
* [[:Category:Vessels:Troop Transport|Troop Transport]]
|}
==By Manufacturing Group==
{|
|
* [[:Category:Produced By:Aera|Aera]]
* [[:Category:Produced By:Andolian Protectorate|Andolian Protectorate]]
* [[:Category:Produced By:Andolians|Andolians]]
* [[:Category:Produced By:Confederation|Confederation]]
* [[:Category:Produced By:Forsaken|Forsaken]]
* [[:Category:Produced By:High-Born|High-Born]]
* [[:Category:Produced By:Interstellar Church of True Form's Return|Interstellar Church of True Form's Return]]
|width="100pt"|
|
* [[:Category:Produced By:Klk'k|Klk'k]]
* [[:Category:Produced By:LIHW|League of Independent Human Worlds]]
* [[:Category:Produced By:Luxury Travel Conglomerate|Luxury Travel Conglomerate]]
* [[:Category:Produced By:Mechanists|Mechanists]]
* [[:Category:Produced By:Merchants|Interstellar Shipping and Mercantile Guild]]
* [[:Category:Produced By:Purists|Purists]]
* [[:Category:Produced By:Rlaan|Rlaan]]
|width="100pt"|
|
* [[:Category:Produced By:Shapers|Shapers]]
* [[:Category:Produced By:Shmrn|Shmrn]]
* [[:Category:Produced By:Spaceborn|Spaceborn]]
* [[:Category:Produced By:Uln|Uln]]
* [[:Category:Produced By:Unadorned|Unadorned]]
|}
==By Usage==
{|
|
* [[:Category:Used By:Aera|Aera]]
* [[:Category:Used By:Aeran Merchant Marine|Aeran Merchant Marine]]
* [[:Category:Used By:Andolian Protectorate|Andolian Protectorate]]
* [[:Category:Used By:Andolians|Andolians]]
* [[:Category:Used By:Bzbr|Bzbr]]
* [[:Category:Used By:Confederation|Confederation]]
* [[:Category:Used By:Confederation Joint Fleet|Confederation Joint Fleet]]
* [[:Category:Used By:Dgn|Dgn]]
* [[:Category:Used By:Forsaken|Forsaken]]
* [[:Category:Used By:High-Born|High-Born]]
* [[:Category:Used By:Homeland Security|Homeland Security]]
* [[:Category:Used By:Hunters|Hunters]]
|width="100pt"|
|
* [[:Category:Used By:ISO|ISO]]
* [[:Category:Used By:Interstellar Church of True Form's Return|Interstellar Church of True Form's Return]]
* [[:Category:Used By:Keepers|Keepers]]
* [[:Category:Used By:Klk'k|Klk'k]]
* [[:Category:Used By:LIHW|League of Independent Human Worlds]]
* [[:Category:Used By:Lmpl|Lmpl]]
* [[:Category:Used By:Luxury Travel Conglomerate|Luxury Travel Conglomerate]]
* [[:Category:Used By:Mechanists|Mechanists]]
* [[:Category:Used By:Merchants|Merchants]]
* [[:Category:Used By:Mishtali|Mishtali]]
* [[:Category:Used By:Nuhln|Nuhln]]
* [[:Category:Used By:Pirates|Pirates]]
|width="100pt"|
|
* [[:Category:Used By:Purists|Purists]]
* [[:Category:Used By:Purth|Purth]]
* [[:Category:Used By:Rlaan|Rlaan]]
* [[:Category:Used By:Rlaan-Briin|Rlaan-Briin]]
* [[:Category:Used By:Rlaan Enforcers|Rlaan Enforcers]]
* [[:Category:Used By:Saahasayaay|Saahasayaay]]
* [[:Category:Used By:Shapers|Shapers]]
* [[:Category:Used By:Shmrn|Shmrn]]
* [[:Category:Used By:Spaceborn|Spaceborn]]
* [[:Category:Used By:Uln|Uln]]
* [[:Category:Used By:Uln(Ranks of Lords)|Uln(Ranks of Lords)]]
* [[:Category:Used By:Unadorned|Unadorned]]
|}
==Alphabetical Listing of Vessels==
{|
|
[[Vessel:Acrotatus|Acrotatus]]

[[Vessel:Admonisher|Admonisher]]

[[Vessel:Agasicles|Agasicles]]

[[Vessel:Agesilaus|Agesilaus]]

[[Vessel:Agesipolis|Agesipolis]]

[[Vessel:Agis|Agis]]

[[Vessel:Aidi|Aidi]]

[[Vessel:Alcmenes|Alcmenes]]

[[Vessel:Anaxander|Anaxander]]

[[Vessel:Anaxandridas|Anaxandridas]]

[[Vessel:Anaxidamus|Anaxidamus]]

[[Vessel:Andi|Andi]]

[[Vessel:Ancestor|Ancestor]]

[[Vessel:Archimedes|Archimedes]]

[[Vessel:Areus|Areus]]

[[Vessel:Ariston|Ariston]]

[[Vessel:Assault Shuttle Mk. 85|Assault Shuttle Mk. 85]]

[[Vessel:Baird|Baird]]

[[Vessel:Baron|Baron]]

[[Vessel:Baronet|Baronet]]

[[Vessel:Battle Cruiser Mk. 32|Battle Cruiser Mk. 32]]

[[Vessel:Beauvoir|Beauvoir]]

[[Vessel:Beholder|Beholder]]

[[Vessel:Bell|Bell]]

[[Vessel:Bomber Mk. 37|Bomber Mk. 37]]

[[Vessel:Camus|Camus]]

[[Vessel:Capybara|Capybara]]

[[Vessel:CARD|CARD]]

[[Vessel:Catfish|Catfish]]

[[Vessel:Charillus|Charillus]]

[[Vessel:CHARM|CHARM]]

[[Vessel:Chengdi|Chengdi]]

[[Vessel:Chengzong|Chengzong]]

[[Vessel:Chongdi|Chongdi]]

[[Vessel:Chudi|Chudi]]

[[Vessel:CILiA|CILiA]]

[[Vessel:Cleombrotus|Cleombrotus]]

[[Vessel:Cleomenes|Cleomenes]]

[[Vessel:Clydesdale|Clydesdale]]

[[Vessel:COMB|COMB]]

[[Vessel:Condor|Condor]]

[[Vessel:Continuity|Continuity]]

[[Vessel:Consequence|Consequence]]

[[Vessel:Convolution|Convolution]]

[[Vessel:CoTTON|CoTTON]]

[[Vessel:Crayfish|Crayfish]]

[[Vessel:Cultivator|Cultivator]]

[[Vessel:CUSP|CUSP]]

[[Vessel:Daizong|Daizong]]

[[Vessel:Demaratus|Demaratus]]

[[Vessel:Dependent|Dependent]]

[[Vessel:Derivative|Derivative]]

[[Vessel:Determinant|Determinant]]

[[Vessel:Dezong|Dezong]]

[[Vessel:Diligence|Diligence]]

[[Vessel:Dirge|Dirge]]

[[Vessel:Dodo|Dodo]]

[[Vessel:Dorissus|Dorissus]]

[[Vessel:Dostoevsky|Dostoevsky]]

[[Vessel:Dropship Mk. 302|Dropship Mk. 302]]

[[Vessel:Duanzong|Duanzong]]

[[Vessel:Duelist|Duelist]]

[[Vessel:Duke|Duke]]

[[Vessel:Duzong|Duzong]]

[[Vessel:Echestratus|Echestratus]]

[[Vessel:Edison|Edison]]
|width="100pt"|
|
[[Vessel:Elephant|Elephant]]

[[Vessel:Ellison|Ellison]]

[[Vessel:Emu|Emu]]

[[Vessel:Entourage|Entourage]]

[[Vessel:Eurycratides|Eurycratides]]

[[Vessel:Eurypon|Eurypon]]

[[Vessel:Faraday|Faraday]]

[[Vessel:Feidi|Feidi]]

[[Vessel:Forebear|Forebear]]

[[Vessel:Fortitude|Fortitude]]

[[Vessel:Franklin|Franklin]]

[[Vessel:Galahad|Galahad]]

[[Vessel:Gaodi|Gaodi]]

[[Vessel:Gaozong|Gaozong]]

[[Vessel:Gaozu|Gaozu]]

[[Vessel:Gawain|Gawain]]

[[Vessel:Gleaner|Gleaner]]

[[Vessel:Goddard|Goddard]]

[[Vessel:Gondi|Gondi]]

[[Vessel:Gongti|Gongti]]

[[Vessel:GTIO|GTIO]]

[[Vessel:Guangzong|Guangzong]]

[[Vessel:H496|H496]]

[[Vessel:Hagfish|Hagfish]]

[[Vessel:Hammer|Hammer]]

[[Vessel:Han|Han]]

[[Vessel:Hidalgo|Hidalgo]]

[[Vessel:Humility|Humility]]

[[Vessel:Hyena|Hyena]]

[[Vessel:Interceptor Mk. 212|Interceptor Mk. 212]]

[[Vessel:Interceptor Mk. 273|Interceptor Mk. 273]]

[[Vessel:Jackal|Jackal]]

[[Vessel:Janissary|Janissary]]

[[Vessel:Jouppi|Jouppi]]

[[Vessel:Kafka|Kafka]]

[[Vessel:Kahan|Kahan]]

[[Vessel:Kierkegaard|Kierkegaard]]

[[Vessel:Kindred|Kindred]]

[[Vessel:Kiwi|Kiwi]]

[[Vessel:Knight|Knight]]

[[Vessel:Koala|Koala]]

[[Vessel:Lament|Lament]]

[[Vessel:Lancelot|Lancelot]]

[[Vessel:Lander Mk. 159|Lander Mk. 159]]

[[Vessel:Leon|Leon]]

[[Vessel:Leonidas|Leonidas]]

[[Vessel:Llama|Llama]]

[[Vessel:Mach|Mach]]

[[Vessel:MacGyver|MacGyver]]

[[Vessel:Maxwell|Maxwell]]

[[Vessel:MESS|MESS]]

[[Vessel:Midwife|Midwife]]

[[Vessel:Miner Mk. 351|Miner Mk. 351]]

[[Vessel:Monaco|Monaco]]

[[Vessel:Mule|Mule]]

[[Vessel:Nicander|Nicander]]

[[Vessel:Niniane|Niniane]]

[[Vessel:Nietzsche|Nietzsche]]

[[Vessel:Otto-Maddox|Otto-Maddox]]

[[Vessel:Ox|Ox]]

[[Vessel:Pacific|Pacific]]

[[Vessel:Pacifier|Pacifier]]

[[Vessel:Patience|Patience]]

[[Vessel:Patrol Boat Mk. 460|Patrol Boat Mk. 460]]

[[Vessel:Patterson|Patterson]]

[[Vessel:Pausanias|Pausanias]]
|width="100pt"|
|
[[Vessel:Pavlov|Pavlov]]

[[Vessel:Pelleus|Pelleus]]

[[Vessel:Penitence|Penitence]]

[[Vessel:People-Mover Mk. 78|People-Mover Mk. 78]]

[[Vessel:Percival|Percival]]

[[Vessel:Pleistarchus|Pleistarchus]]

[[Vessel:Pleistoanax|Pleistoanax]]

[[Vessel:Plowshare|Plowshare]]

[[Vessel:Polydectes|Polydectes]]

[[Vessel:Polydorus|Polydorus]]

[[Vessel:Procles|Procles]]

[[Vessel:Progenitor|Progenitor]]

[[Vessel:Progeny|Progeny]]

[[Vessel:Prudence|Prudence]]

[[Vessel:Prytanis|Prytanis]]

[[Vessel:PSC-U Mk. 29|PSC-U Mk. 29]]

[[Vessel:Quicksilver|Quicksilver]]

[[Vessel:Raven|Raven]]

[[Vessel:Redeemer|Redeemer]]

[[Vessel:Reeve|Reeve]]

[[Vessel:Regret|Regret]]

[[Vessel:Reindeer|Reindeer]]

[[Vessel:Resupply and Refuel Mk. 451|Resupply and Refuel Mk. 451]]

[[Vessel:Rhincodon|Rhincodon]]

[[Vessel:Robin|Robin]]

[[Vessel:Ruizong|Ruizong]]

[[Vessel:Sartre|Sartre]]

[[Vessel:Scarab|Scarab]]

[[Vessel:Schroedinger|Schroedinger]]

[[Vessel:Shangdi|Shangdi]]

[[Vessel:Shenzong|Shenzong]]

[[Vessel:Shizong|Shizong]]

[[Vessel:Shizu|Shizu]]

[[Vessel:Shundi|Shundi]]

[[Vessel:Sickle|Sickle]]

[[Vessel:Sobriety|Sobriety]]

[[Vessel:Sofono|Sofono]]

[[Vessel:Soos|Soos]]

[[Vessel:Sorrow|Sorrow]]

[[Vessel:Squire|Squire]]

[[Vessel:Taizong|Taizong]]

[[Vessel:Taizu|Taizu]]

[[Vessel:Teleclus|Teleclus]]

[[Vessel:Tesla|Tesla]]

[[Vessel:Thales|Thales]]

[[Vessel:Theopompus|Theopompus]]

[[Vessel:Tridacna|Tridacna]]

[[Vessel:Tsiolkovsky|Tsiolkovsky]]

[[Vessel:Vanderbilt|Vanderbilt]]

[[Vessel:Vendetta|Vendetta]]

[[Vessel:Vigilance|Vigilance]]

[[Vessel:Vulture|Vulture]]

[[Vessel:Watson|Watson]]

[[Vessel:Wendi|Wendi]]

[[Vessel:Wudi|Wudi]]

[[Vessel:Xianzong|Xianzong]]

[[Vessel:Xiaozong|Xiaozong]]

[[Vessel:Xizong|Xizong]]

[[Vessel:Xuande|Xuande]]

[[Vessel:Xuanzong|Xuanzong]]

[[Vessel:Yeoman|Yeoman]]

[[Vessel:Yindi|Yindi]]

[[Vessel:Zeuxidamus|Zeuxidamus]]

[[Vessel:Zhaozong|Zhaozong]]

[[Vessel:Zhezong|Zhezong]]

[[Vessel:Zhuangzong|Zhuangzong]]
|}
==Installations==

Agricultural Habitat
*[[Installation:Confederation Agricultural Station|Confederation]] Strangelet (Some minor problems with importing model. May have since been fixed)

Anti-matter Refinery
*[[Installation:Aeran Anti-matter Refinery|Aera]]
*[[Installation:Confederation Anti-matter Refinery|Confederation]]
*[[Installation:Rlaan Anti-matter Refinery|Rlaan]]

Area Fortifications
*[[Installation:Shmrn Area Fortifications|Shmrn]]

Asteroid Fighter Base
*[[Installation:Aeran Asteroid Fighter-Base|Aera]]
*[[Installation:Confederation Asteroid Fighter-Base|Confederation]]
*[[Installation:Rlaan Asteroid Fighter-Base|Rlaan]]

Bio-Adaptation Station
*[[Installation:Shaper Bio-Adaptation Station|Shaper]]

Bio-mod Research Station
*[[Installation:Rlaan-Briin Bio-Mod Research Station|Rlaan-Briin]]

Civilian Population Defense Redoubt
*[[Installation:Rlaan Civilian Population Defense Redoubt|Rlaan]]

Commerce Center
*[[Installation:Confederation Commerce Center|Confederation]]

----
'''Installation entries above this point have been entered into the [[Development:3D Models|model list]] and have had the 'Model Status' section renamed to 'Visuals' and all non-image data from said section moved elsewhere.'''
----

Defense of Area Missile Battery
*[[Installation:Confederation Defense of Area Missile Battery|Confederation]]

Diplomatic Station
*[[Installation:Uln Diplomatic Station|Uln]] Strangelet?

Distributed Fortification
*[[Installation:Andolian Distributed Fortification|Andolian]]

Factory
*[[Installation:Aeran Factory Station|Area]] needs new model+texture
*[[Installation:Confederation Factory Station|Confederation]] Strangelet
*[[Installation:Rlaan Factory Station|Rlaan]] needs new model+texture

Fighter Barracks (station)
*[[Installation:Aera Fighter Barracks (station)|Aera]] needs new model+texture
*[[Installation:Confederation Fighter Barracks (station)|Confederation]] Strangelet finished new model+texture, committed
*[[Installation:Rlaan Fighter Barracks (station)|Rlaan]] needs new model+texture

Habitat
*[[Installation:Spaceborn Habitat|Spaceborn]]

Jump Point Fortifications
*[[Installation:Aeran Jump Fort|Aera]]
*[[Installation:Confederation Jump Fort|Confederation]]
*[[Installation:Rlaan Jump Fort|Rlaan]]
*[[Installation:Uln Jump Fort|Uln]]

Long Range Weapons Platform
*[[Installation:Aeran Long Range Weapons Platform|Aera]]
*[[Installation:Confederation Long Range Weapons Platform|Confederation]]

Medical Station
*[[Installation:Aeran Medical Station|Aera]] needs new model+texture
*[[Installation:Confederation Medical Station|Confederation]] Strangelet finished new model+texture, committed
*[[Installation:Rlaan Medical Station|Rlaan]] needs new model+texture

Medical Transformation Procedure Station
*[[Installation:Rlaan-Briin Medical Transformation Procedure Station|Rlaan-Briin]]

Mining Base
*[[Installation:Aeran Mining Base|Aera]] Ryder working on new model+texture
*[[Installation:Confederation Mining Base|Confederation]] Strangelet
*[[Installation:Pirate Mining Base|Pirates]] deserves new model+texture
*[[Installation:Rlaan Mining Base|Rlaan]] deserves new model+texture
*[[Installation:Uln Mining Base|Uln]]

Outpost(?) - Strangelet [http://vegastrike.sourceforge.net/albums/wiki_manual/Ship-Profiles/profile_019.jpg]

Orbital Docking Platform
*[[Installation:Aeran Orbital Docking Platform|Aera]]
*[[Installation:Confederation Orbital Docking Platform|Confederation]] PeteyG
*[[Installation:Highborn Class 1 Orbital Docking Platfrom|High Born Class 1]]
*[[Installation:Highborn Class 2 Orbital Docking Platform|High Born Class 2]]
*Rlaan
**[[Installation:Rlaan Methane Breather Orbital Docking Platform|Methane Breather]]
**[[Installation:Rlaan Oxygen Breather Orbital Docking Platform|Oxygen Breather]]
*[[Installation:Uln Orbital Docking Platform|Uln]]

Planetary Defense Station
*[[Installation:Aeran Planetary Defense Station|Aera]]

Prison Station
*[[Installation:Homeland Security Prison Station|Homeland Security]]
*[[Installation:Rlaan Prison Station|Rlaan]]

Refinery Station
*[[Installation:Aeran Refinery Station|Aera]] needs new model+texture
*[[Installation:Confederation Refinery Station|Confederation]]Strangelet - 2 versions
*[[Installation:Pirate Refinery Station|Pirate]]needs new model+texture
*[[Installation:Rlaan Refinery Station|Rlaan]]Rlaan needs new model+texture

Relay Station
*[[Installation:Confederation Relay Station|Confederation]] Strangelet, Pontiac
*[[Installation:Aeran Relay Station|Aera]]
*[[Installation:Rlaan Relay Station|Rlaan]]
*[[Installation:Uln Relay Station|Uln]]

Repair and Salvage Station
*[[Installation:Aera Repair and Salvage Station|Aera]]
*[[Installation:Confederation Repair and Salvage Station|Confederation]]
*[[Installation:Rlaan Repair and Salvage Station|Rlaan]]

Research Station
*[[Installation:Aeran Research Station|Aera]] needs new model+texture
*[[Installation:Confederation Research Station|Confederation]] Strangelet
*[[Installation:Rlaan Research Station|Rlaan]]

Sensor Array
*[[Installation:Aeran Sensor Array|Aera]]
*[[Installation:Unadorned Sensor Array|Unadorned]]

Shipyard Strangelet - unassigned
*Civilian
**[[Installation:Aeran Civilian Shipyard|Aera]]
**[[Installation:High-Born Luxury Shipyard|Luxury Travel Conglomerate]]
**[[Installation:Mechanist Civilian Shipyard|Mechanist]]
**[[Installation:Merchant Civilian Shipyard|Merchant]]
**[[Installation:Rlaan Civilian Shipyard|Rlaan]]
**[[Installation:Andolian Spaceborn Civilian Shipyard|Spaceborn / Andolian]]
*Military
**[[Installation:Aeran Military Shipyard|Aera]]
**[[Installation:Confederation Military Shipyard|Confederation]] Strangelet, finished and committed
**[[Installation:High-Born Shipyard|High Born Command]]
**[[Installation:Mechanist Automated Mega-Shipyard|Mechanist]]
**[[Installation:Rlaan Military Shipyard|Rlaan]]
**[[Installation:Andolian Protectorate Military Shipyard|Spaceborn / Andolian]]

Star Fortress
*[[Installation:Aeran Star Fortress|Aera]] needs new model+texture
*[[Installation:Confederation Star Fortress|Confederation]] needed new model+texture. Artists working on: Strangelet, Etheral, Targon. Preliminary Models received from: Etheral, Targon,Strangelet Last contact June 2004
*[[Installation:Rlaan Star Fortress|Rlaan]] DIRELY in need of new model+texture

Storage Depot
*[[Installation:Aeran Storage Depot|Aera]]
*[[Installation:Confederation Storage Depot|Confederation]]

Weapons Platform
*[[Installation:Aeran Weapons Platform|Aera]]
*[[Installation:Confederation Weapons Platform|Confed]]
*[[Installation:Rlaan Weapons Platform|Rlaan]]

==Containers and Other Non-Crewed Significant Objects==
(Aera Cargo Freight Container) Pontiac
(Confed Cargo Freight Container)
(Rlaan Cargo Freight Container)
(Uln Cargo Freight Container)

==Specific vessels and installations==
* [[Installation:Specific installation:Cherryh station|Cherryh station]]
* [[Installation:Specific installation:Hephaestus|Hephaestus]]
* Forsaken Slowboats:
** {{Fixme}}
* See also {{reference}}[[Terminology:Lo Ad'Fai'led|Lo Ad'Fai'led]]
* [Specific vessel:xxxx]

==Yet to be named or sorted==

(Pirate Converted Old Freight)

==See also==
[[Development:3D Models|model list]]
----
{{NAV_Database |
| previous=[[Factions]]
| up=[[Database]]
| next=[[Upgrades]]
}}

Vessels & Installations

2008-10-11T10:03:07Z

Nachtwolf: Vessels & Installations moved to Vessels and Installations: The & breaks things

#redirect [[Vessels and Installations]]

Talk:Vessels and Installations

2008-10-11T10:03:07Z

Nachtwolf: Talk:Vessels & Installations moved to Talk:Vessels and Installations

=Namespace=
* Wouldn't it be better to have the ships in an extra namespace like this [[Vessel:Acrotatus]] as it is with the [[Terminology]] right now ? [[User:pontiac|pontiac]] 01:22, 2 Mar 2005 (PST)
** Of course it would be quite easy to move the pages to this new locations (there are just alot of them ;) ) [[User:pontiac|pontiac]] 01:38, 2 Mar 2005 (PST)

Sounds like a good idea. I'm sure we can move slowly them as we edit them for content. [[User:jackS|jackS]] 02:20, 2 Mar 2005 (PST)

*[[User:jackS|jackS]] 19:38, 2 Mar 2005 (PST) see [[Vessel:Acrotatus]]

*[[User:jackS|jackS]] 23:11, 2 Mar 2005 (PST) See also [[:Category:Vessels:Civilian]] and the accompanying talk page for a potential issue with renaming everything
:also, see [[Vessel:Admonisher]] for another look at a ship page (this one actually being in-game-- it needs a picture :) )
*[[User:Silverain|Silverain]] 16:11, 4 Apr 2005 (PDT) I linked to the hud.png at sourceforge as a temp measure to see how it looks. Short of getting larger screenshots and storing them in the gallery somewhere, this is all I can think of.

*[[User:jackS|jackS]] 23:30, 3 Mar 2005 (PST)Well, moved all of the pages, but haven't updated this page to reflect that (only works right now because of re-directs). Also, still need to fix all the next and previous fields to not be "FIXME" (of course, I also have to put in entries for all but 3 of the articles, but I try not to depress myself too much :)
** [[User:pontiac|pontiac]] On a sidenote: Do you think that a previous/next link is a good idea with this many vessle/installation-entries? Sure it's possible, but is it maintainable? Maybe we should limit this nav-menu to the manual and the linking between big topics (e.g vessles->installations->weapons->...) and maybe the subsections of them. .. just a though :)
*** [[User:Silverain|Silverain]] 16:11, 4 Apr 2005 (PDT) Maintainable? Difficult but yes, since JackS has put most names in already. I would say have the side links to the next ship, that way people browsing for entertainment can read ship to ship, rather than having to go back to the main page first.
**** [[User:pontiac|Pontiac]] 06:47, 5 Apr 2005 (PDT) I'm not against the previous/next links, but i still think it's too much effort... especially if you see most of the existing prev/next links, which still have the '''Ship:xxx''' prefix and the top links points to '''Ships'''. ''To make it clear'' that needs to be changed to the '''Vessel:''' prefix etc... Further just think about name changes and new Vessels. For each change you need to change two other pages (alphabetical prev + next) to reflect this change/addition. But maybe there will but less changes then i am imagine right now.. in this chase my arguments nullify. Just my 2c ;)
** [[User:pontiac|pontiac]] 23:55, 3 Mar 2005 (PST) Maybe we could just use something like this: [[Template:Parent_link]] to link to the parent (e.g Vessels & Installations) page.
{{Parent_link | parent=[[Vessels & Installations]]}}
<pre>
{{Parent_link | parent=[[Vessels & Installations]]}}
</pre>
*** [[User:pontiac|Pontiac]] 12:28, 30 Jun 2005 (PDT) On a second note i think that the manual prev/top/next nav-bar would be better here.
=Blueprints=
* [[User:TyKeiL|TykeiL]] June 29th 2005 hey, i have added some blueprint style images to some of the pages, hope you like. i really think that on the main page the names of the ships should be accompanied with there HUD image. that way people will get a peek at what they will be looking into.
** [[User:jackS|jackS]] 18:07, 29 Jun 2005 (PDT) @Tykeil - check your PM inbox
***[[User:TyKeiL|TyKeiL]] 19:50, 8 Jul 2005 @jackS - read and replied. Sorry about the delay, im not used to checking on these types of things, im used to mailing lists.
** [[User:pontiac|Pontiac]] 12:28, 30 Jun 2005 (PDT) I like the blueprints, they are pretty cool 8) Using the HUD-images of the ships/stations as a preview is a very good idea, i thni nobody will be against that :D
*** [[User:TyKeiL|TyKeiL]] 03:23, 8 Jul 2005 (PDT) @Pontiac - excellent.
** [[User:TyKeiL|TyKeiL]] 03:23, 8 Jul 2005 (PDT) - These images are half sized the originals which were 1024x768, so i can supply them if needed. I also want to put information on the images like lables for different things, ie engine types, gun specs, speed, cargo capacity, aerodynamic info(for flying in atmosphere) anything that will spruce up the images making them look more professional and nice.
*** [[User:pontiac|Pontiac]] 07:13, 8 Jul 2005 (PDT) I really like the idea, but you have to keep in mind that the infos may change in the future (position, numbers, names, etc...) so providing the graphic source files to the community (ask the devs for upload) is a necessity.
****[[User:TyKeiL|TyKeiL]] 07:57, 9 Jul 2005 (PDT) - that was also one of the things i was going to ask sometime(someplace i can upload the image source) which consists of 1 .blend file 4 .tga files(not completely necessary) and 1 .xcf file, i will also provide instruction along with them to get the exact same look so to keep consistancy, im not exactly sure how the cvs tree's are organised so i will have to wait for someone else to help me with that.

=Layout of a Vessel or Installation page=
* [[User:pontiac|Pontiac]] 12:28, 30 Jun 2005 (PDT) I wonder if we could move the model and texture-info into the development section (i suggest the [[Development:3D Models]] page). and put in a header like "Blueprint" or "Ship Design" or something like that.
** [[User:TyKeiL|TyKeiL]] 03:25, 8 Jul 2005 (PDT) - I agree to move the model and texture info to the dev section, but people still need there pictures so as jackS said to me in the PM before make both link to the same image.
*** [[User:pontiac|Pontiac]] 07:08, 8 Jul 2005 (PDT) I was a bit unclear in my statement above. I meant to move all the development bits (textures, status of the modes, etc..) to the development section, but keep the 'finished' images and such (e.g your blueprints/pictures) on the 'Vessel'-pages. :D
****[[User:TyKeiL|TyKeiL]] 07:57, 9 Jul 2005 (PDT) - dont warry it was clear, i was just stating the obvious. :O)

Talk:Vessels & Installations

2008-10-11T10:03:07Z

Nachtwolf: Talk:Vessels & Installations moved to Talk:Vessels and Installations: The & breaks things

#redirect [[Talk:Vessels and Installations]]

HowTo:VCPP Compiling

2008-06-02T05:48:30Z

Nachtwolf: /* Compiling under Visual C++ */ added preliminary info for vc9

{{NAV_Manual |
| previous=[[HowTo:Checkout SVN|Checkout SVN]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}
----
{{attention}}
=Compiling under Visual C++=
First, [[HowTo:Checkout_SVN|check out the SVN modules]].

When using another module (e.g. <code>vegastrike</code>, <code>vssetup</code>), they should be placed in the directory above <code>vega-proj</code> in the directory tree.

For example, when you want to checkout Vegastrike, you may make a <code>Vegastrike</code> directory and from there, checkout <code>vega-proj</code> (or <code>vega-vc7</code> for "dot-NET" or <code>vega-vc8</code> for Express users), <code>vegastrike</code>, <code>data</code> ALL from this directory.

* <code>vegastrike/</code> - base directory.
* <code>vegastrike/vegastrike/</code> - The stuff from the vegastrike module (the actual code)
* <code>vegastrike/vega-proj/</code> - The project files. (VISUAL C++ 6.x)
* <code>vegastrike/vega-vc7/</code> - The project files. (VISUAL C++ 7.x)
* <code>vegastrike/vega-vc8/</code> - The project files. (VISUAL C++ 8.0)
* <code>vegastrike/win32/</code> - The newer version of data. Binaries will be compiled into the bin directory, so it should be here in the tree if you do not want to edit project settings.

Here is a list of every project included for SVN compilation that is used:
* vegastrike (<code>Vegastrike.exe</code>) - '''VegaStrike binary'''
* vsserver (<code>vegaserver.exe</code>) - VegaStrike server
* vssetup (<code>Setup.exe</code>) - The main Setup program--doesn't change much, so you can use the binary directly from SVN.

==Visual C++ 6.0 (deprecated)==
As of the end of December, 2005, VegaStrike has dropped compatibility for VC 6 because of the new OGRE rendering engine.

VC 6 users can grab a free copy of VC 8 (Visual Studio 2005 Express) off the Microsoft site, and follow the directions below to compile.
===Compiling using VC 6===
Until the OGRE port is finished, VC 6 will still compile, so you can try it if VC8 won't work for you.

First, check out all the modules above.

Then from the MSDEV IDE, open the "vegastrike.dsw" project inside vega-proj, and compile. You will want to use Debug or Release configurations for a standard build. (The Boost 129 builds are permanently broken, and GLUT doesn't work very well as far as I know)

==Visual C++ 9.0 (2008 Express)==
I think this is only for Windosw XP SP3 and Vista (so probably not win2k).

You can get the downloader here:
http://www.microsoft.com/express/download/
Make sure to be *logged on* as admin. Otherwise you will get some weird error 3MB into the download.
Run the installer, uncheck all the boxes on each page if you want a lighter download.

It will do everything on it's own then ask to reboot.
Apparently no Platform SDK is necessary (at least it seemed that way for me, but maybe that's because I already had VC7 installed. Please someone post here if you try it out on a new install.

I was hoping that I could just use the vega-vc8 directory but Python seems to be incompatible so we will need a new version of python... still, it may be possible to provide slightly modified projects in the vc8 directory for vc9 support with a few different .libs.

==Visual C++ 8.0 (2005 Express)==
Warning: VC8 requires a big download off Microsoft's site.

Microsoft claims that they will continue offering their non-expiring version of VC8 forever, so I guess this will be the main build platform.

Keep in mind that VC8 does something weird with .manifest files, and for official builds, I would suggest VC7 as it seems to be faster, and it lacks compatibility issues. There are too many forum threads on this to count.

This will work on Windows 2000 or XP (Not sure about 98,95...).

# You have two download choices:
#* Download the standard install: http://msdn.microsoft.com/vstudio/express/visualc/download/ and register (free but requires an E-mail and filling in a form)
#* Download the "manual install" (from a CD image): http://msdn.microsoft.com/vstudio/express/support/install/ (seems to be an ISO image, but looks like it doesn't require registration...)
# Install the [http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en#filelist| Windows Platform SDK] ([http://msdn.microsoft.com/library/default.asp?url=/library/EN-US/sdkintro/sdkintro/installing_the_platform_sdk_with_visual_studio.asp Instructions] - [http://www.microsoft.com/downloads/info.aspx?na=47&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&u=details.aspx%3ffamilyid%3dD8EECD75-1FC4-49E5-BC66-9DA2B03D9B92%26displaylang%3den FULL ISO version(395MB)]). A [http://www.microsoft.com/downloads/details.aspx?FamilyID=0baf2b35-c656-4969-ace8-e4c0c0716adb&DisplayLang=en more recent SDK] for Windows XP SP2 exists, but it has not been tested with VS (yet.)
# In Visual C++ 8.0 (2005 Express), under Tools...Options...Visual C++ Directories, add an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include and an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include\mfc. If you forget this step, the build will not be able to find windows.h, basetsd.h, and afxres.h and will throw fatal errors.
# You should not need the [http://www.microsoft.com/downloads/details.aspx?FamilyID=EDB98FFA-A59C-4C23-9B92-BA304F188314&displaylang=en DirectX SDK] (337MB) to compile VS, but it may be required to compile OGRE in the future.
# Disable Intellisense: Microsoft provides no GUI for this, but it is recommended unless you want to eat up twice the RAM and wait 10-20 seconds between saving each file.
#* Browse to your VC8 install.
#* Go to the VC/vcpackages folders and rename the "feacp" DLL file to anything else like "feacp_backup.dll". This should not break anything... it will only disable IntelliSense.
# Checkout the Vegastrike project as described earlier.
# Open the "vega-vc8" project using the IDE.
# The compilation should go for the most part smoothly. If you encounter any problems, please tell us in the [http://vegastrike.sourceforge.net/forums/ forum] or specifically on [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=6251 this thread].
#* Note that Debug versions will be very slow (I get 5 frames/second on my Pentium3 1GHz machine using debug VS).

==Visual Studio 7.x==

===Compiling from the command line with Visual Studio===
Here is a batch file that could be used to checkout everything and then compile all projects (copy and paste in <code>makeall.bat</code>), if you were going somewhere for a few hours and wanted to get a working project when you got back:
<pre>
@echo off
mkdir vegastrike
cd vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vega-vc7
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/
cd vega-vc7
echo Building project...
"C:\VC7\Common7\IDE\devenv.exe" vegastrike.sln /BUILD Debug
cd ..
cd ..
</pre>

'''NOTE''': You must replace the "<code>C:\vc7</code>" with the directory where you installed visual c++ 7 and replace the "<code>Debug</code>" on the same line with "<code>Release</code>" if you want a release build.

===Compiling with the Visual Studio GUI===
''(This is written with Visual C++ .NET Standard in mind)''

Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], use Visual Studio to open vegastrike.sln, found in the vega-vc7 directory. When compiling for release, select "Release Boost 131" from the drop-down menu on the toolbar. Right-click on the "vegastrike" project in the "solution explorer" sidebar, and then select "Build".

==Visual C++ Toolkit 2003==
This is a [http://msdn.microsoft.com/visualc/vctoolkit2003/ free download] from Microsoft, and is the same compiler and linker as Visual Studio 2003.

Note, you must have Windows XP or 2000 in order to install the toolkit. (formerly said only Windows XP, but this is not true according to their download page)

===Downloads===
* Install the [http://msdn.microsoft.com/visualc/vctoolkit2003/ Visual C++ Toolkit 2003] from the Microsoft web site.
* Install the [http://www.microsoft.com/msdownload/platformsdk/sdkupdate Windows Platform SDK] from the Microsoft web site. You can take any of the 3 versions available.
* Install the [http://www.codeblocks.org/downloads.shtml Code::Blocks] (alternative download site on [http://prdownloads.sourceforge.net/codeblocks/ Sourceforge]). You can take the full version or the core only, since we will use the VS 2003 TK.

===Configuring Code::Blocks===
* Run CodeBlocks. The first time you install it, you will be listed with a set of compilers. Select Microsoft Visual C++ Toolkit, and click '''Set As Default'''.
* For configuration you have to include the location of the Windows Platform SDK. Go to '''Settings''' -> '''Compiler''' in the menu. Click the '''Directories''' tab. Add the directory "<code>C:\Program Files\Microsoft SDK\bin</code>" to the Resource Compiler tab.

===Compiling with Code::Blocks and Visual C++ Toolkit===
Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], import the vegastrike.sln file, found in the vega-vc7 directory into Code::Blocks using '''Project->Import->MS Visual Studio Solution''' in the menu.

===Note (CVS version as of 14 Nov 2005===
Using the most recent CVS versions (and 2003/Runtime versions from Microsoft) I had to remove /W from the build options '''Project Build Options > Compiler Options > Other Options'''

=See Also=
* [[HowTo:Checkout SVN|Checking out SVN]]
* [http://www.codeblocks.org Code:Blocks IDE]

----
{{NAV_Manual |
| previous=[[HowTo:Checkout SVN|Checkout SVN]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}

[[Category:HowTos|VCpp Compiling]]

Development:Base Backgrounds

2008-05-24T04:49:56Z

Nachtwolf: /* Python Scripts */ info about Z coordinate of ships

{{parent_link|parent=[[Development]]}}
----
=Introduction=

This page summarizes concepts and approaches recommended to add base or planet backgrounds to Vega Strike.

=Development Needs and Tasks=

We could always use more backgrounds. Ideally, each planet and base in Vega Strike would have a unique background.

Please head over here for a list of open tasks: [[Development:2D_Images#Base_Backgrounds]]

=Docking Backgrounds=

==Texture Requirements==

===Generic Image Requirements===

Please read this [[Development:Graphics_Requirements]] page before continuing to the specific requirements.

===Specific Image Requirements===
That leaves few options:
*1024x1024
*2048x2048

Keeping original high resolution image (e.g. 8192x or 4096x) versions in stock helps maintaining quality and scalability as game development progresses or typical screen resolutions rise in the future with better hardware available to the players.

==Creating and Naming==

===Comments by MamiyaOtaru in Forums===

First off, the bases are not full screen due to the config file, not the sprite file. Change that first to have fullscreen bases. So, the explanation:

In the coordinate system, 0,0 is at the center not the top left. The coordinate system is cartesian, left to right is -1 to 1 x, top to bottom is 1 to -1 y.

Width 2 means the width of the screen (two halves, from -1 to 1) and height 2 means the height of the screen.

In your example, the image is meant to take up 3.104/2 screen widths and 2.4832/2 screen heights. This is because the actual used part of the image (320x200) is approx 512*(2/3.2) x 256*(2/2.5). 3.104 and 2.4832 stretch the image beyond fullscreen, so that the part of the image that actually has something in it (which is only 320x200) will take up fullscreen.

The next two numbers are where the image is centered. Often, those two numbers are actually stored elsewhere. In cockpits, they are stored in the .cpt file and only the dimensions are actually in the .spr file. Here, the X and Y coordinates for the center of the image are in /bases/*.py. Your example is in /bases/pleasure_land.py

Your example is therefore actually
3.104 2.4832 width and height
and
0.582 -0.2716 centerX and centerY

The center of the image is thus a little more than half the distance from the center of the screen to the right hand side of the screen. This serves to place the center of the area that has actual content at the center of the screen. The center is a bit more than a quarter of the way from the center to the bottom of the screen for the same reason.

If you use an image that fills up the whole bitmap, without empty space like the priv remake backgrounds, to go fullscreen you would use something like this
2 2 (2 half widths and half heights, from -1, -1 to 1, 1)
0 0 (centered in the center of the screen)

Oh, and pleasure_land.py is also where the animations are linked, if you'd like to remove them for a different background. The animations are the water and the building lights: Jolson_LandingBay_wtr and Jolson_LandingBay_blt respectively. Remove their lines.

===Python Scripts===

You will need to create the appropriate python scripts to be placed in the <code>bases</code> directory.

Each planet has a script labeled according to its texture name (i.e. texturename_day.py, texturename_night.py, texturename_sunset.py, etc.) What this means is that each planet you want specific control over will require its own texture. Not too big a task (as I assume the number of planets for which this control is needed is not major), as you can almost just copy and paste the old python files for the planet type, but you will also need to edit units.csv to add that planet type. This is easy if you know what you're doing, but obviously is not a long term solution to such a problem. (If anyone knows of a better way that we can do this, let me know!)

Each unit type has a script labeled according to its unit and faction name (unitname_factionname.py, or ignoring factions unitname.py). Here the trick will be to create a python file that checks the name of the unit you are docked to to see if it's the campaign one. If it is then do something special, else do the same as every other unit.

Basically, these scripts are simply run when the player docks. We can't force a different script to load at will, only make sure that the script VS looks for contains what we want it to. However, it might be useful in future to change this...

'''Room definition'''

<code><pre>room1 = Base.Room ('Aera Planet')
Base.Texture (room1, 'tex', 'bases/generic/aera_planet.spr', 0, 0)</pre></code>

In the first line, you assign the room object type to your script variable giving the unique argument, the name that will be visible on the in-game interface.
The second line defines the texture image sprite for the base background with the argument list ''roomvariable'', ''linkname'', ''spriteaddress'', ''centerx'', ''centery''.

'''Ship placement'''

<code><pre>Base.Ship (room1, 'ship', (-0.3, -0.3, 6), (0, 0.93, -0.34), (-1, 0, 0))</pre></code>

The above code defines the placement for the ship in room1, assuming room1 is the landing pad room or the repairs and upgrades room, where the player's ship should show. It has the form:
Base.Ship (''roomvariable'', ''linkname'', ''vectorP'', ''vectorR'', ''vectorQ'')

where:
* ''roomvariable'' - the room in which you place the button
* ''linkname'' - arbitrary name to make your code readable
* ''vectorP'' - position of the ship with (''centerx'', ''centery'', ''scale'') -- Note that scale is a Z coordinate in perspective, so you must adjust your X and Y accordingly as it gets farther away.
* ''vectorR'' - ship up orientation with up-vector coordinates (''x'', ''y'', ''z'')
* ''vectorQ'' - ship nose orientation with forward-vector coordinates (''x'', ''y'', ''z'')

'''''Testimonial by chuck_starchaser'''''

''Adjusting these vectors (particularly the up and forward) manually, by trial and error, can be very time consuming and tedious. The sum of the squares of the x, y and z values in the up and forward vectors must add to one. In other words, the vectors should be "normalized", or of "unit-length". Also, the up and forward vectors should be normal (perpendicular) to one another. In arithmetic terms, their dot product should be zero. And what's the dot-product? The result of multiplying up.x times forward.x, adding to that the product of up.y times forward.y, and adding to that the product of up.z times forward.z. That should be zero if the two vectors are perpendicular. Yes; it's Hell; been there and survived. But there's an escape... maybe...''

''If you have a background artwork with a given perspective of the landing pad, say, you may want to load it into Blender as a background image. Set your view to orthogonal, with positive x to the right, and positive y up on the screen. Place a cube. Scale it so it's 2 x 2 x 2 size. Go to perspective, transparent mode (Numpad 5, Z in Blender). Set your view so that the cube extends over the screen, half visible, half beyond the screen borders. Now, load the mesh of a typical ship that you'd have land there. Do NOT change your view; but rotate the ship's mesh to get the perspective of it you want, over the picture. Now you can snap your cursor to the center of the ship (Shift-S, Cursor to selection, in Object mode) and read the cursor's position from the View Properties screen. That's NOT the values you want for the P vector, but save them for now. For the forward vector, in edit mode, select the nose vertex for the ship, snap cursor, write down the xyz. Subtract the xyz for the ship's center. Normalize it (i.e.: divide all three numbers by the square root of the sum of the squares. That's your vectorQ. For the UP vector, find any two vertices on the ship that are vertically aligned, get their coords, subtract, normalize.''

''VectorP will be a bit trickier: You need to measure the position of the center of the ship on-screen, placing a ruler on your monitor, careful not to scratch it. And you need to translate those measurements to VS screen coordinates, where the far left is -1 X, far right is +1 X, top is +1 Y, bottom is -1 Y. The two numbers you obtained are centerx and centery, but what should scale be? Frankly, I (chuck starchaser) don't know how scale works; I just adjusted it for PU by trial and error.''

''Hope this helps. The idea for this Blender method came to me in retrospect, today (May 23, 2008), and I haven't actually tested it. Be sure to edit this document to fix it as necessary, if you do make it work; or if you come up with a better method.''

'''Button definition'''

<code><pre>Base.Comp (room1, 'CargoComputer', 0.289063, -0.283854, 0.146484, 0.179688, 'Cargo Computer', 'Cargo')
Base.Link (room1, 'goto_exterior', 0.3, -0.3, 0.5, 0.3, 'Planet Exterior', room2)</pre></code>

The above code defines the button for the cargo computer and a link button to an exterior background image with the following convention:
Base.''Object'' (''roomvariable'', ''linkname'', ''leftx'', ''bottomy'', ''width'', ''height'', ''displaytext'', ''linkobject'' )

where:
* ''roomvariable'' - the room in which you place the button
* ''linkname'' - arbitrary name to make your code readable
* ''leftx'', ''bottomy'' - button left bottom corner coordinates; ranging from -1 on the left to 1 on the right, -1 on bottom 1 on the top
* ''width'', ''height'' - button size; full screen size is 2, half screen is 1.
* ''displaytext'' - the text that will be shown in game
* ''linkobject'' - the variable name of the object in your python script or a name predefined in the engine

In addition, for Base.Comp, the ''linkobject'' is used to determine the services available at that particular computer:
* Cargo
* Missions
* News
* Info
* Upgrade
* ShipDealer

==Including and Testing==

You'll need to create a sprite file referencing the image. See more information on how to do this in [[HowTo:Edit_HUDs|HowTo:Edit HUDs]]

==Selection and Vetting==

===Some Thoughts===

Once you have chosen a replacement candidate and have one or more proposals...

===The Process===
If you are not sure that your texture meets the basic requirements, then please open a forum topic posting your textures.
Please verify the summary of requirements [[#Including_and_Testing|above]].

If a texture that you have created meets the texture requirements, then:
* Open a poll for a reasonable period of time (e.g. 2 weeks) and describe:
** which texture(s) you'd like to replace
** display your candidates
** briefly describe the method of creation and tools used
** If you'd like to replace more than one texture, describe how you would assign the favorites of the poll to the individual textures

* After a set period of time
** announce the winners
** and call the poll closed

* Then
** Submit the textures to svn (in case you have commit rights attributed), or
** through the forum ask a developer with write access to submit them (e.g. the maintainer of this page, [[User:pyramid|pyramid]]).

==Submission==

AKA: Committing to SVN.

=References=

==Software, Tools==
For a comprehensive list of tools, please see:
*[[Links:Graphic_Applications|Links:Graphic Applications]]
*[[Links:3D_Applications|Links:3D Applications]]

==See Also==
* See the following Forums [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=4636], [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=1679&start=0&postdays=0&postorder=asc]
* [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=2292 How to change the base art in a planet]
* Example Scripts

'''Author: [[User:pyramid|pyramid]]'''

[[Category:Development]]

Moving data4.x to data

2008-05-02T19:04:08Z

Nachtwolf: tested phrase

We recently (on May 1) moved the data4.x repository to "data". This has instructions on how to update your repository without checking out everything again.

'''NOTE:''' Do not follow these steps if you checked out the whole top-level folder. A simple SVN Update "Omit Externals" or "--ignore-externals" (command-line) when you update should do the trick.

'''ANOTHER NOTE:''' If you have a limited amount of bandwidth or a slow internet connection, make a copy of your original "data4.x" before doing this--it may corrupt your whole data directory if it goes wrong

'''Please write on the Discussion page, or post on the forums if this process fails or is confusing in any way!'''

= Updating your existing data4.x repository =
The process is slightly different for each platform, because we now store binaries in a different place.

== Windows Users ==
Here are the steps to modify your working directory on windows (using Tortoise SVN):

I have only tested this on [[http://tortoisesvn.net/downloads Tortoise SVN 1.4.8 / subversion 1.4.6]].

Do not use SVN Switch unless you need to--it may decide to delete your whole directory for no reason if you do this wrong... however if you use SVN Switch, make sure to be all the way up-to-date (At least revision 12226) before completing this process.

Make some empty text files and folders inside your "data" folder--that should go a long way to preventing Subversion from deleting your data folder if something were to go wrong.

# Make an empty folder called "win32" (put this outside of data4.x). Right click on it and select "SVN Checkout..."
# Type the URL https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/win32
# Make sure "Omit Externals" box is checked! Otherwise it will helpfully download your whole data directory again.
# Leave the checkout folder as is.
# You should see it downloading binaries.
# Rename your data4.x folder to be called "data".
# Drag the "data" folder inside of win32.
# Now, run "SVN Update" on the 'win32' folder
# You should only see a few changes (as from a normal SVN download).
# If you get pages and pages of "Deleted" files, you might want to stop it before it's too late. Otherwise, contratulations: The update process is complete.

== Mac OSX users ==

I'm assuming you followed a tutorial similar to [[http://vegastrike.sourceforge.net/wiki/HowTo:Checkout_SVNMac]] and that you already have "svn" or "/usr/local/bin/svn" installed.

For the Mac, this process is not as simple as the windows one.
First, right/control click on your Vega Strike .app that you downloaded, click "Show package contents". Open Contents, and drag "Resources" to the desktop (this is the same folder you put there when you initially checked out your verison).

Now go into a console and run (you can copy and paste this):
svn checkout --ignore-externals https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/mac
mv ~/Desktop/Resources mac/VegaStrike.app/Contents/Resources
svn

If all works according to plan, you should only have to download a few files ("Framework" directories) and binaries in "MacOS".

== Linux and users building from source ==
Go inside of data4.x from a Terminal. Then run:
svn switch https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data

If it gives you an error because you are not using https, the easiest way is to type "svn info" from inside of data4.x, copy the "URL" field, and paste thatwith the "4.x" removed.

Now, type "svn update". If you do not get an error, the update is complete.

Moving data4.x to data

2008-05-02T18:55:53Z

Nachtwolf: another note about making a copy

We recently (on May 1) moved the data4.x repository to "data". This has instructions on how to update your repository without checking out everything again.

'''NOTE:''' Do not follow these steps if you checked out the whole top-level folder. A simple SVN Update "Omit Externals" or "--ignore-externals" (command-line) when you update should do the trick.

'''ANOTHER NOTE:''' If you have a limited amount of bandwidth or a slow internet connection, make a copy of your original "data4.x" before doing this--it may corrupt your whole data directory if it goes wrong

'''Please write on the Discussion page, or post on the forums if this process fails or is confusing in any way!'''

= Updating your existing data4.x repository =
The process is slightly different for each platform, because we now store binaries in a different place.

== Windows Users ==
Here are the steps to modify your working directory on windows (using Tortoise SVN):

Do not use SVN Switch unless you need to--it may decide to delete your whole directory for no reason if you do this wrong... however if you use SVN Switch, make sure to be all the way up-to-date (At least revision 12226) before completing this process.

Make some empty text files and folders inside your "data" folder--that should go a long way to preventing Subversion from deleting your data folder if something were to go wrong.

# Make an empty folder called "win32" (put this outside of data4.x). Right click on it and select "SVN Checkout..."
# Type the URL https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/win32
# Make sure "Omit Externals" box is checked! Otherwise it will helpfully download your whole data directory again.
# Leave the checkout folder as is.
# You should see it downloading binaries.
# Rename your data4.x folder to be called "data".
# Drag the "data" folder inside of win32.
# Now, run "SVN Update" on the 'win32' folder
# You should only see a few changes (as from a normal SVN download).
# If you get pages and pages of "Deleted" files, you might want to stop it before it's too late. Otherwise, contratulations: The update process is complete.

== Mac OSX users ==

I'm assuming you followed a tutorial similar to [[http://vegastrike.sourceforge.net/wiki/HowTo:Checkout_SVNMac]] and that you already have "svn" or "/usr/local/bin/svn" installed.

For the Mac, this process is not as simple as the windows one.
First, right/control click on your Vega Strike .app that you downloaded, click "Show package contents". Open Contents, and drag "Resources" to the desktop (this is the same folder you put there when you initially checked out your verison).

Now go into a console and run (you can copy and paste this):
svn checkout --ignore-externals https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/mac
mv ~/Desktop/Resources mac/VegaStrike.app/Contents/Resources
svn

If all works according to plan, you should only have to download a few files ("Framework" directories) and binaries in "MacOS".

== Linux and users building from source ==
Go inside of data4.x from a Terminal. Then run:
svn switch https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data

If it gives you an error because you are not using https, the easiest way is to type "svn info" from inside of data4.x, copy the "URL" field, and paste thatwith the "4.x" removed.

Now, type "svn update". If you do not get an error, the update is complete.

Moving data4.x to data

2008-05-02T18:49:59Z

Nachtwolf: Note about whole trunk folder

We recently (on May 1) moved the data4.x repository to "data". This has instructions on how to update your repository without checking out everything again.

'''NOTE:''' Do not follow these steps if you checked out the whole top-level folder. A simple SVN Update "Omit Externals" or "--ignore-externals" (command-line) when you update should do the trick.

'''Please write on the Discussion page, or post on the forums if this process fails or is confusing in any way!'''

= Updating your existing data4.x repository =
The process is slightly different for each platform, because we now store binaries in a different place.

== Windows Users ==
Here are the steps to modify your working directory on windows (using Tortoise SVN):

Do not use SVN Switch unless you need to--it may decide to delete your whole directory for no reason if you do this wrong... however if you use SVN Switch, make sure to be all the way up-to-date (At least revision 12226) before completing this process.

Make some empty text files and folders inside your "data" folder--that should go a long way to preventing Subversion from deleting your data folder if something were to go wrong.

# Make an empty folder called "win32" (put this outside of data4.x). Right click on it and select "SVN Checkout..."
# Type the URL https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/win32
# Make sure "Omit Externals" box is checked! Otherwise it will helpfully download your whole data directory again.
# Leave the checkout folder as is.
# You should see it downloading binaries.
# Rename your data4.x folder to be called "data".
# Drag the "data" folder inside of win32.
# Now, run "SVN Update" on the 'win32' folder
# You should only see a few changes (as from a normal SVN download).
# If you get pages and pages of "Deleted" files, you might want to stop it before it's too late. Otherwise, contratulations: The update process is complete.

== Mac OSX users ==

I'm assuming you followed a tutorial similar to [[http://vegastrike.sourceforge.net/wiki/HowTo:Checkout_SVNMac]] and that you already have "svn" or "/usr/local/bin/svn" installed.

For the Mac, this process is not as simple as the windows one.
First, right/control click on your Vega Strike .app that you downloaded, click "Show package contents". Open Contents, and drag "Resources" to the desktop (this is the same folder you put there when you initially checked out your verison).

Now go into a console and run (you can copy and paste this):
svn checkout --ignore-externals https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/mac
mv ~/Desktop/Resources mac/VegaStrike.app/Contents/Resources
svn

If all works according to plan, you should only have to download a few files ("Framework" directories) and binaries in "MacOS".

== Linux and users building from source ==
Go inside of data4.x from a Terminal. Then run:
svn switch https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data

If it gives you an error because you are not using https, the easiest way is to type "svn info" from inside of data4.x, copy the "URL" field, and paste thatwith the "4.x" removed.

Now, type "svn update". If you do not get an error, the update is complete.

Moving data4.x to data

2008-05-02T18:36:55Z

Nachtwolf: /* Windows Users */ added comment

We recently (on May 1) moved the data4.x repository to "data". This has instructions on how to update your repository without checking out everything again.

'''Please write on the Discussion page, or post on the forums if this process fails or is confusing in any way!'''

= Updating your existing data4.x repository =
The process is slightly different for each platform, because we now store binaries in a different place.

== Windows Users ==
Here are the steps to modify your working directory on windows (using Tortoise SVN):

Do not use SVN Switch unless you need to--it may decide to delete your whole directory for no reason if you do this wrong... however if you use SVN Switch, make sure to be all the way up-to-date (At least revision 12226) before completing this process.

Make some empty text files and folders inside your "data" folder--that should go a long way to preventing Subversion from deleting your data folder if something were to go wrong.

# Make an empty folder called "win32" (put this outside of data4.x). Right click on it and select "SVN Checkout..."
# Type the URL https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/win32
# Make sure "Omit Externals" box is checked! Otherwise it will helpfully download your whole data directory again.
# Leave the checkout folder as is.
# You should see it downloading binaries.
# Rename your data4.x folder to be called "data".
# Drag the "data" folder inside of win32.
# Now, run "SVN Update" on the 'win32' folder
# You should only see a few changes (as from a normal SVN download).
# If you get pages and pages of "Deleted" files, you might want to stop it before it's too late. Otherwise, contratulations: The update process is complete.

== Mac OSX users ==

I'm assuming you followed a tutorial similar to [[http://vegastrike.sourceforge.net/wiki/HowTo:Checkout_SVNMac]] and that you already have "svn" or "/usr/local/bin/svn" installed.

For the Mac, this process is not as simple as the windows one.
First, right/control click on your Vega Strike .app that you downloaded, click "Show package contents". Open Contents, and drag "Resources" to the desktop (this is the same folder you put there when you initially checked out your verison).

Now go into a console and run (you can copy and paste this):
svn checkout --ignore-externals https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/mac
mv ~/Desktop/Resources mac/VegaStrike.app/Contents/Resources
svn

If all works according to plan, you should only have to download a few files ("Framework" directories) and binaries in "MacOS".

== Linux and users building from source ==
Go inside of data4.x from a Terminal. Then run:
svn switch https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data

If it gives you an error because you are not using https, the easiest way is to type "svn info" from inside of data4.x, copy the "URL" field, and paste thatwith the "4.x" removed.

Now, type "svn update". If you do not get an error, the update is complete.

Moving data4.x to data

2008-05-02T05:52:42Z

Nachtwolf: Note to write about problems.

We recently (on May 1) moved the data4.x repository to "data". This has instructions on how to update your repository without checking out everything again.

'''Please write on the Discussion page, or post on the forums if this process fails or is confusing in any way!'''

= Updating your existing data4.x repository =
The process is slightly different for each platform, because we now store binaries in a different place.

== Windows Users ==
Here are the steps to modify your working directory on windows (using Tortoise SVN):

Do not use SVN Switch unless you need to--it may decide to delete your whole directory for no reason if you do this wrong... however if you use SVN Switch, make sure to be all the way up-to-date (At least revision 12226) before completing this process.

# Make an empty folder called "win32" (put this outside of data4.x). Right click on it and select "SVN Checkout..."
# Type the URL https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/win32
# Make sure "Omit Externals" box is checked! Otherwise it will helpfully download your whole data directory again.
# Leave the checkout folder as is.
# You should see it downloading binaries.
# Rename your data4.x folder to be called "data".
# Drag the "data" folder inside of win32.
# Now, run "SVN Update" on the 'win32' folder
# You should only see a few changes (as from a normal SVN download).
# If you get pages and pages of "Deleted" files, you might want to stop it before it's too late. Otherwise, contratulations: The update process is complete.

== Mac OSX users ==

I'm assuming you followed a tutorial similar to [[http://vegastrike.sourceforge.net/wiki/HowTo:Checkout_SVNMac]] and that you already have "svn" or "/usr/local/bin/svn" installed.

For the Mac, this process is not as simple as the windows one.
First, right/control click on your Vega Strike .app that you downloaded, click "Show package contents". Open Contents, and drag "Resources" to the desktop (this is the same folder you put there when you initially checked out your verison).

Now go into a console and run (you can copy and paste this):
svn checkout --ignore-externals https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/mac
mv ~/Desktop/Resources mac/VegaStrike.app/Contents/Resources
svn

If all works according to plan, you should only have to download a few files ("Framework" directories) and binaries in "MacOS".

== Linux and users building from source ==
Go inside of data4.x from a Terminal. Then run:
svn switch https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data

If it gives you an error because you are not using https, the easiest way is to type "svn info" from inside of data4.x, copy the "URL" field, and paste thatwith the "4.x" removed.

Now, type "svn update". If you do not get an error, the update is complete.

Moving data4.x to data

2008-05-02T05:39:41Z

Nachtwolf: /* Windows Users */ more minor fixes

We recently (on May 1) moved the data4.x repository to "data". This has instructions on how to update your repository without checking out everything again.

= Updating your existing data4.x repository =
The process is slightly different for each platform, because we now store binaries in a different place.

== Windows Users ==
Here are the steps to modify your working directory on windows (using Tortoise SVN):

Do not use SVN Switch unless you need to--it may decide to delete your whole directory for no reason if you do this wrong... however if you use SVN Switch, make sure to be all the way up-to-date (At least revision 12226) before completing this process.

# Make an empty folder called "win32" (put this outside of data4.x). Right click on it and select "SVN Checkout..."
# Type the URL https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/win32
# Make sure "Omit Externals" box is checked! Otherwise it will helpfully download your whole data directory again.
# Leave the checkout folder as is.
# You should see it downloading binaries.
# Rename your data4.x folder to be called "data".
# Drag the "data" folder inside of win32.
# Now, run "SVN Update" on the 'win32' folder
# You should only see a few changes (as from a normal SVN download).
# If you get pages and pages of "Deleted" files, you might want to stop it before it's too late. Otherwise, contratulations: The update process is complete.

== Mac OSX users ==

I'm assuming you followed a tutorial similar to [[http://vegastrike.sourceforge.net/wiki/HowTo:Checkout_SVNMac]] and that you already have "svn" or "/usr/local/bin/svn" installed.

For the Mac, this process is not as simple as the windows one.
First, right/control click on your Vega Strike .app that you downloaded, click "Show package contents". Open Contents, and drag "Resources" to the desktop (this is the same folder you put there when you initially checked out your verison).

Now go into a console and run (you can copy and paste this):
svn checkout --ignore-externals https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/mac
mv ~/Desktop/Resources mac/VegaStrike.app/Contents/Resources
svn

If all works according to plan, you should only have to download a few files ("Framework" directories) and binaries in "MacOS".

== Linux and users building from source ==
Go inside of data4.x from a Terminal. Then run:
svn switch https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data

If it gives you an error because you are not using https, the easiest way is to type "svn info" from inside of data4.x, copy the "URL" field, and paste thatwith the "4.x" removed.

Now, type "svn update". If you do not get an error, the update is complete.

Moving data4.x to data

2008-05-02T05:33:56Z

Nachtwolf: /* Windows Users */ removed thing about "not empty" dialog

We recently (on May 1) moved the data4.x repository to "data". This has instructions on how to update your repository without checking out everything again.

= Updating your existing data4.x repository =
The process is slightly different for each platform, because we now store binaries in a different place.

== Windows Users ==
Here are the steps to modify your working directory on windows (using Tortoise SVN):

Do not use SVN Switch unless you need to--it may decide to delete your whole directory for no reason if you do this wrong... however if you use SVN Switch, make sure to be all the way up-to-date (At least revision 12226) before completing this process.

# Rename your data4.x folder to be called "data".</li>
# Make an empty folder called "win32" (put this outside of data4.x). Right click on it and select "SVN Checkout..."</li>
# Type the URL https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/win32</li>
# Make sure "Omit Externals" box is checked! Otherwise it will helpfully download your whole data directory again.
# Leave the checkout folder as is.</li>
# You should see it downloading binaries.
# Drag the "data" folder inside of win32.
# Now, run "SVN Update"
# As long as it does not start downloading or deleting data files again, the update process is complete.</li>

== Mac OSX users ==

I'm assuming you followed a tutorial similar to [[http://vegastrike.sourceforge.net/wiki/HowTo:Checkout_SVNMac]] and that you already have "svn" or "/usr/local/bin/svn" installed.

For the Mac, this process is not as simple as the windows one.
First, right/control click on your Vega Strike .app that you downloaded, click "Show package contents". Open Contents, and drag "Resources" to the desktop (this is the same folder you put there when you initially checked out your verison).

Now go into a console and run (you can copy and paste this):
svn checkout --ignore-externals https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/mac
mv ~/Desktop/Resources mac/VegaStrike.app/Contents/Resources
svn

If all works according to plan, you should only have to download a few files ("Framework" directories) and binaries in "MacOS".

== Linux and users building from source ==
Go inside of data4.x from a Terminal. Then run:
svn switch https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data

If it gives you an error because you are not using https, the easiest way is to type "svn info" from inside of data4.x, copy the "URL" field, and paste thatwith the "4.x" removed.

Now, type "svn update". If you do not get an error, the update is complete.

Moving data4.x to data

2008-05-02T05:32:32Z

Nachtwolf: /* Windows Users */ minor change about Omit Externals box

We recently (on May 1) moved the data4.x repository to "data". This has instructions on how to update your repository without checking out everything again.

= Updating your existing data4.x repository =
The process is slightly different for each platform, because we now store binaries in a different place.

== Windows Users ==
Here are the steps to modify your working directory on windows (using Tortoise SVN):

Do not use SVN Switch unless you need to--it may decide to delete your whole directory for no reason if you do this wrong... however if you use SVN Switch, make sure to be all the way up-to-date (At least revision 12226) before completing this process.

# Rename your data4.x folder to be called "data".</li>
# Make an empty folder called "win32" (put this outside of data4.x)</li>
# right click on win32 and select "SVN Checkout..."</li>
# Type the URL https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/win32</li>
# Make sure "Omit Externals" box is checked! Otherwise it will helpfully download your whole data directory again.
# Leave the checkout folder as is. Click OK when it warns you about the "not empty folder".</li>
# You should see it downloading binaries.
# Drag the "data" folder inside of win32.
# Now, run "SVN Update"
# As long as it does not start downloading or deleting data files again, the update process is complete.</li>

== Mac OSX users ==

I'm assuming you followed a tutorial similar to [[http://vegastrike.sourceforge.net/wiki/HowTo:Checkout_SVNMac]] and that you already have "svn" or "/usr/local/bin/svn" installed.

For the Mac, this process is not as simple as the windows one.
First, right/control click on your Vega Strike .app that you downloaded, click "Show package contents". Open Contents, and drag "Resources" to the desktop (this is the same folder you put there when you initially checked out your verison).

Now go into a console and run (you can copy and paste this):
svn checkout --ignore-externals https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/mac
mv ~/Desktop/Resources mac/VegaStrike.app/Contents/Resources
svn

If all works according to plan, you should only have to download a few files ("Framework" directories) and binaries in "MacOS".

== Linux and users building from source ==
Go inside of data4.x from a Terminal. Then run:
svn switch https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data

If it gives you an error because you are not using https, the easiest way is to type "svn info" from inside of data4.x, copy the "URL" field, and paste thatwith the "4.x" removed.

Now, type "svn update". If you do not get an error, the update is complete.

Moving data4.x to data

2008-05-02T05:30:55Z

Nachtwolf: /* Windows Users */ more comments

We recently (on May 1) moved the data4.x repository to "data". This has instructions on how to update your repository without checking out everything again.

= Updating your existing data4.x repository =
The process is slightly different for each platform, because we now store binaries in a different place.

== Windows Users ==
Here are the steps to modify your working directory on windows (using Tortoise SVN):

Do not use SVN Switch unless you need to--it may decide to delete your whole directory for no reason if you do this wrong... however if you use SVN Switch, make sure to be all the way up-to-date (At least revision 12226) before completing this process.

# Rename your data4.x folder to be called "data".</li>
# Make an empty folder called "win32" (put this outside of data4.x)</li>
# right click on win32 and select "SVN Checkout..."</li>
# Type the URL https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/win32</li>
# Uncheck the "Fetch Externals" box.
# Leave the checkout folder as is. Click OK when it warns you about the "not empty folder".</li>
# You should see it downloading binaries.
# Drag the "data" folder inside of win32.
# Now, run "SVN Update"
# As long as it does not start downloading or deleting data files again, the update process is complete.</li>

== Mac OSX users ==

I'm assuming you followed a tutorial similar to [[http://vegastrike.sourceforge.net/wiki/HowTo:Checkout_SVNMac]] and that you already have "svn" or "/usr/local/bin/svn" installed.

For the Mac, this process is not as simple as the windows one.
First, right/control click on your Vega Strike .app that you downloaded, click "Show package contents". Open Contents, and drag "Resources" to the desktop (this is the same folder you put there when you initially checked out your verison).

Now go into a console and run (you can copy and paste this):
svn checkout --ignore-externals https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/mac
mv ~/Desktop/Resources mac/VegaStrike.app/Contents/Resources
svn

If all works according to plan, you should only have to download a few files ("Framework" directories) and binaries in "MacOS".

== Linux and users building from source ==
Go inside of data4.x from a Terminal. Then run:
svn switch https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data

If it gives you an error because you are not using https, the easiest way is to type "svn info" from inside of data4.x, copy the "URL" field, and paste thatwith the "4.x" removed.

Now, type "svn update". If you do not get an error, the update is complete.

Moving data4.x to data

2008-05-02T05:27:57Z

Nachtwolf: /* Windows Users */ added comment

We recently (on May 1) moved the data4.x repository to "data". This has instructions on how to update your repository without checking out everything again.

= Updating your existing data4.x repository =
The process is slightly different for each platform, because we now store binaries in a different place.

== Windows Users ==
Here are the steps to modify your working directory on windows (using Tortoise SVN):

Do not use SVN Switch unless you need to--it may decide to delete your whole directory for no reason if you do this wrong.

# Rename your data4.x folder to be called "data".</li>
# Make an empty folder called "win32" (put this outside of data4.x)</li>
# right click on win32 and select "SVN Checkout..."</li>
# Type the URL https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/win32</li>
# Uncheck the "Fetch Externals" box.
# Leave the checkout folder as is. Click OK when it warns you about the "not empty folder".</li>
# You should see it downloading binaries.
# Drag the "data" folder inside of win32.
# Now, run "SVN Update"
# As long as it does not start downloading or deleting data files again, the update process is complete.</li>

== Mac OSX users ==

I'm assuming you followed a tutorial similar to [[http://vegastrike.sourceforge.net/wiki/HowTo:Checkout_SVNMac]] and that you already have "svn" or "/usr/local/bin/svn" installed.

For the Mac, this process is not as simple as the windows one.
First, right/control click on your Vega Strike .app that you downloaded, click "Show package contents". Open Contents, and drag "Resources" to the desktop (this is the same folder you put there when you initially checked out your verison).

Now go into a console and run (you can copy and paste this):
svn checkout --ignore-externals https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/mac
mv ~/Desktop/Resources mac/VegaStrike.app/Contents/Resources
svn

If all works according to plan, you should only have to download a few files ("Framework" directories) and binaries in "MacOS".

== Linux and users building from source ==
Go inside of data4.x from a Terminal. Then run:
svn switch https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data

If it gives you an error because you are not using https, the easiest way is to type "svn info" from inside of data4.x, copy the "URL" field, and paste thatwith the "4.x" removed.

Now, type "svn update". If you do not get an error, the update is complete.

Moving data4.x to data

2008-05-02T05:25:23Z

Nachtwolf: tried to fix directions

We recently (on May 1) moved the data4.x repository to "data". This has instructions on how to update your repository without checking out everything again.

= Updating your existing data4.x repository =
The process is slightly different for each platform, because we now store binaries in a different place.

== Windows Users ==
Here are the steps to modify your working directory on windows (using Tortoise SVN):

# Rename your data4.x folder to be called "data".</li>
# Make an empty folder called "win32" (put this outside of data4.x)</li>
# right click on win32 and select "SVN Checkout..."</li>
# Type the URL https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/win32</li>
# Uncheck the "Fetch Externals" box.
# Leave the checkout folder as is. Click OK when it warns you about the "not empty folder".</li>
# You should see it downloading binaries.
# Drag the "data" folder inside of win32.
# Now, run "SVN Update"
# As long as it does not start downloading or deleting data files again, the update process is complete.</li>

== Mac OSX users ==

I'm assuming you followed a tutorial similar to [[http://vegastrike.sourceforge.net/wiki/HowTo:Checkout_SVNMac]] and that you already have "svn" or "/usr/local/bin/svn" installed.

For the Mac, this process is not as simple as the windows one.
First, right/control click on your Vega Strike .app that you downloaded, click "Show package contents". Open Contents, and drag "Resources" to the desktop (this is the same folder you put there when you initially checked out your verison).

Now go into a console and run (you can copy and paste this):
svn checkout --ignore-externals https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/mac
mv ~/Desktop/Resources mac/VegaStrike.app/Contents/Resources
svn

If all works according to plan, you should only have to download a few files ("Framework" directories) and binaries in "MacOS".

== Linux and users building from source ==
Go inside of data4.x from a Terminal. Then run:
svn switch https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data

If it gives you an error because you are not using https, the easiest way is to type "svn info" from inside of data4.x, copy the "URL" field, and paste thatwith the "4.x" removed.

Now, type "svn update". If you do not get an error, the update is complete.

Moving data4.x to data

2008-05-02T04:51:50Z

Nachtwolf: Added tutorials on how to rename data4.x

We recently (on May 1) moved the data4.x repository to "data". This has instructions on how to update your repository without checking out everything again.

= Updating your existing data4.x repository =
The process is slightly different for each platform, because we now store binaries in a different place.

== Windows Users ==
Here are the steps to modify your working directory on windows (using Tortoise SVN):
# On Windows, right click on your "data4.x" folder and click TortoiseSVN -> "Switch..."</li>
# Take out the "4.x", and click OK.</li>
# Rename your data4.x folder to be called "data".</li>
# Make an empty folder called "win32" (put this outside of data4.x)</li>
# Drag the "data" folder inside of win32.</li>
# right click on win32 and select "SVN Checkout..."</li>
# Type the URL https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/win32</li>
# Leave the checkout folder as is. Click OK when it warns you about the "not empty folder".</li>
# You should see it downloading additional data. As long as it does not start downloading data files again, the update process is complete.</li>

== Mac OSX users ==

I'm assuming you followed a tutorial similar to [[http://vegastrike.sourceforge.net/wiki/HowTo:Checkout_SVNMac]] and that you already have "svn" or "/usr/local/bin/svn" installed.

For the Mac, this process is not as simple as the windows one.
First, right/control click on your Vega Strike .app that you downloaded, click "Show package contents". Open Contents, and drag "Resources" to the desktop (this is the same folder you put there when you initially checked out your verison).

Now go into a console and run (you can copy and paste this):
mkdir -p mac/VegaStrike.app/Contents
mv ~/Desktop/Resources mac/VegaStrike.app/Contents/Resources
svn checkout https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/mac

If all works according to plan, you should only have to download a few files ("Framework" directories) and binaries in "MacOS".

== Linux and users building from source ==
Go inside of data4.x from a Terminal. Then run:
svn switch https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data

If it gives you an error because you are not using https, the easiest way is to type "svn info" from inside of data4.x, copy the "URL" field, and paste thatwith the "4.x" removed.

Now, type "svn update". If you do not get an error, the update is complete.

HowTos

2008-05-02T04:34:21Z

Nachtwolf: /* Obtain a copy of the development-version files */ added section about moving data4.x

{{Wiki_Nav_Index}}
__FORCETOC__
= Game HowTos =
== Modeling ==
''This series of How-to articles is intended to take you through the full process of creating a model and adding it to Vega Strike.''
* [[HowTo:Add Ships|Adding your ship to Vega Strike]] - An overview of how to create and add ships to the game
** [[HowTo:Create Models]] - A summary on how to create a new model for Vega Strike
*** [[HowTo:Model a Ship|Brad Mick's video tutorial on ship modelling]] - using Lightwave, but the concept is general: ''Rapid Prototyping''
*** [[HowTo:Create Ships in Wings3D|Creating a 3D-model using Wings3D]] - includes general guidance for other modeling programs
*** [[HowTo:Basic Blender Tutorial|A basic Blender3D tutorial]] - not specific to ships, though...
** [[HowTo:Smooth Groups|Understanding "Smooth Groups"]] - a Blender tutorial on splitting smooth groups...
** [[HowTo:Bevel|Getting bevels to look good]] - a Blender tutorial on smooth shading and beveling...
** [[HowTo:Weld|Smoothly Welding complex shapes]] - a Blender tutorial on smooth welding...
** [[HowTo:Unwrap|Unwrapping your model]] - How to UV-map your ship so it can be textured
*** [[HowTo:Unwrap in Blender|Using Blender to unwrap your model]] - A blender UV-mapping tutorial
*** [[HowTo:FullUnwrapBlender|Full ship unwrap tutorial (Blender)]] - Full ship UV unwrap, from A to Z
** [[HowTo:Texture|Creating your own textures]] - A summary on how to make texture maps
*** [[HowTo:Texture in Wings3d|Texturing your model in Wings 3d]]
*** [http://netzwelt.gaming-hut.de/vegatexturing/ WIP VegaStrike texturing page by Major]
*** [http://edice.netfirms.com/tuts/texturetut.htm Texturing tutorial by Duality]
*** [[HowTo:SuperrealisticTexturing|Tips for realistic-looking textures]]
*** [[HowTo:Make Animated Textures|Using animated textures on a model]]
** [[HowTo:Edit BFXM files|Editing BFXM files (format spec)]]
*** [[HowTo:Edit XMESH files|Editing the xmesh file of a ship]]
*** [[HowTo:Add LODs|Adding Levels of Detail]]
*** [[HowTo:Add Engine Glow|Adding an engine glow to your 3D model]]
*** [[HowTo:Add Per Pixel Lighting|Adding per-pixel lighting to your 3D model]]
** [[HowTo:Edit units.csv|Editing units.csv]]
*** [[HowTo:Edit Unit Files|Editing the xunit file of a ship]] - Deprecated, but can be converted easily to .csv format
=== Advanced Topics ===
* [[HowTo:Edit HUDs|Editing HUDs, placing radars, ...]]
* [[HowTo:Create Cockpit in Wings3d|Creating a 3D cockpit for your ship.]]
=== New Stuff (The Shaders Age begins...) ===
* [[HowTo:IntroToShaders|Introduction to shaders, and what they mean for you]] --Bumpmaps, Normalmaps, Shininess maps ...

==Artwork ==
''Artwork related Howtos''
* [[HowTo:Make Splash Screens|Making splash screens that display at startup]]
* [[HowTo:Radiosity baking in Blender|Radiosity baking in Blender]]

More under [[Development#Art-related]]

== MODs ==
* [[HowTo:MOD|You want to create your own mod for VS? Start here.]]
== Miscellaneous ==
* Game related:
** [[HowTo:Make Weapons|Adding new weapons to the game]]
** [[HowTo:Add Upgrades|Adding new upgrades to the game]]
** [[HowTo:Add Cargo|Adding new cargo to the game]]
** [[HowTo:Edit Systems|Creating or editing star systems]]
** [[HowTo:Edit AI|Creating or editing Ship AI's]]
** [[HowTo:Take Screenshots|Taking really awesome screenshots]]
* Information related:
** [[HowTo:Add Descriptions|Putting ship and goods descriptions into the game]]
***[[HowTo:Edit master_part_list.csv|Editing the Master_part_list.csv file]]
** [[HowTo:Add Conversations|Adding more conversation lines to the game]]
** [[HowTo:Edit faction relationships|Edit the relationships between the existing factions]] (the <code>factions.xml</code> file)
* Event related:
** [[Development:Quests & Campaigns|Creating or editing campaigns]] - Portal for all python scripting reference for campaigns, missions, quests, and adventures
** [[HowTo:Edit News|Creating or editing news events]]

=Sourcecode HowTos =
== Obtain a copy of the development-version files ==
* [[HowTo:Checkout SVN|Checkout Vega Strike's Subversion (SVN) modules.]]
* [[HowTo:Checkout SVNMac|Checkout Vega Strike's Subversion (SVN) modules on Mac OSX.]]
* [[HowTo:Checkout CVS|Checkout Vegastrike CVS modules with various programs.]] - '''Deprecated'''
'''NOTE: Vegastrike development has moved to SVN. CVS is still theoretically accessible, but the repository is months out of date and will never be updated again. There is no reason not to use Subversion instead.'''
* [[Moving data4.x to data]] - We recently (on May 1) moved the data4.x repository to "data". This has instructions on how to update your repository without checking out everything again.

== Compile the Vega Strike sourcecode ==
* [[HowTo:VCPP Compiling|Compiling from SVN under Visual C++]]
* [[HowTo:Cygwin Compiling|Compiling from SVN under Cygwin]] (may not work--enter at your own risk)
* [[HowTo:Compile from CVS|Compiling from SVN under your favourite Unixlike OS]]
* [[HowTo:Compile on OSX|Compiling from SVN on Mac OSX]]
* Debug a Vega Strike Compilation
** [[HowTo:Use GDB|Debugging on your Unixlike OS using GDB]]
** [[HowTo:Use Dr Watson|Debugging on Windows using Dr Watson]]

= Miscellaneous HowTos =
*[[HowTo:Contribute|The Vega Strike Contributor's Guide]]
* Wings
** [[HowTo:Compile Wings3d from CVS|Compiling CVS version of Wings 3d (Linux)]]
** [[HowTo:Install Wings3d|Installing Wings 3D and the Xmesh Plugin]]

=See Also=
* [[FAQ:Installing|Installing]]
* [[Development]]
* For related tools see the [[Links]] section.
[[Category:HowTo]]

HowTo:VCPP Compiling

2008-05-02T04:31:10Z

Nachtwolf: /* Compiling under Visual C++ */ data4.x

{{NAV_Manual |
| previous=[[HowTo:Checkout SVN|Checkout SVN]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}
----
{{attention}}
=Compiling under Visual C++=
First, [[HowTo:Checkout_SVN|check out the SVN modules]].

When using another module (e.g. <code>vegastrike</code>, <code>vssetup</code>), they should be placed in the directory above <code>vega-proj</code> in the directory tree.

For example, when you want to checkout Vegastrike, you may make a <code>Vegastrike</code> directory and from there, checkout <code>vega-proj</code> (or <code>vega-vc7</code> for "dot-NET" or <code>vega-vc8</code> for Express users), <code>vegastrike</code>, <code>data</code> ALL from this directory.

* <code>vegastrike/</code> - base directory.
* <code>vegastrike/vegastrike/</code> - The stuff from the vegastrike module (the actual code)
* <code>vegastrike/vega-proj/</code> - The project files. (VISUAL C++ 6.x)
* <code>vegastrike/vega-vc7/</code> - The project files. (VISUAL C++ 7.x)
* <code>vegastrike/vega-vc8/</code> - The project files. (VISUAL C++ 8.0)
* <code>vegastrike/data/</code> - The newer version of data. Binaries will be compiled into the bin directory, so it should be here in the tree if you do not want to edit project settings.

Here is a list of every project included for SVN compilation:

* AsterGet (<code>AsterGen.exe</code>) - Not used
* mission (<code>Mission Launcher.exe</code>) - Not used
* savegame (<code>Launcher.exe</code>) - '''Not required but still used for selecting missions'''
* texturizer (<code>Texturizer.exe</code>) - Not used
** REQUIRES texturizer module
* TriSort (<code>TriSort.exe</code>) - Not used?
* vsacctserver (<code>accountserver.exe</code>) - Soon to be functional in Windows
* vegastrike (<code>Vegastrike.exe</code>) - '''used - VegaStrike binary'''
* vsserver (<code>vegaserver.exe</code>) - Soon to be functional in Windows
* vssetup (<code>Setup.exe</code>) - The main Setup program--doesn't change much, so you can use the binary directly from SVN.

==Visual C++ 6.0 (deprecated)==
As of the end of December, 2005, VegaStrike has dropped compatibility for VC 6 because of the new OGRE rendering engine.

VC 6 users can grab a free copy of VC 8 (Visual Studio 2005 Express) off the Microsoft site, and follow the directions below to compile.
===Compiling using VC 6===
Until the OGRE port is finished, VC 6 will still compile, so you can try it if VC8 won't work for you.

First, check out all the modules above.

Then from the MSDEV IDE, open the "vegastrike.dsw" project inside vega-proj, and compile. You will want to use Debug or Release configurations for a standard build. (The Boost 129 builds are permanently broken, and GLUT doesn't work very well as far as I know)

==Visual C++ 8.0 (2005 Express)==
Warning: VC8 requires a big download off Microsoft's site.

Microsoft claims that they will continue offering their non-expiring version of VC8 forever, so I guess this will be the main build platform.

Keep in mind that VC8 does something weird with .manifest files, and for official builds, I would suggest VC7 as it seems to be faster, and it lacks compatibility issues. There are too many forum threads on this to count.

This will work on Windows 2000 or XP (Not sure about 98,95...).

# You have two download choices:
#* Download the standard install: http://msdn.microsoft.com/vstudio/express/visualc/download/ and register (free but requires an E-mail and filling in a form)
#* Download the "manual install" (from a CD image): http://msdn.microsoft.com/vstudio/express/support/install/ (seems to be an ISO image, but looks like it doesn't require registration...)
# Install the [http://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&displaylang=en#filelist| Windows Platform SDK] ([http://msdn.microsoft.com/library/default.asp?url=/library/EN-US/sdkintro/sdkintro/installing_the_platform_sdk_with_visual_studio.asp Instructions] - [http://www.microsoft.com/downloads/info.aspx?na=47&p=3&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=A55B6B43-E24F-4EA3-A93E-40C0EC4F68E5&u=details.aspx%3ffamilyid%3dD8EECD75-1FC4-49E5-BC66-9DA2B03D9B92%26displaylang%3den FULL ISO version(395MB)]). A [http://www.microsoft.com/downloads/details.aspx?FamilyID=0baf2b35-c656-4969-ace8-e4c0c0716adb&DisplayLang=en more recent SDK] for Windows XP SP2 exists, but it has not been tested with VS (yet.)
# In Visual C++ 8.0 (2005 Express), under Tools...Options...Visual C++ Directories, add an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include and an Include directory for C:\Program Files\Microsoft Platform SDK for Windows Server 2003 R2\Include\mfc. If you forget this step, the build will not be able to find windows.h, basetsd.h, and afxres.h and will throw fatal errors.
# You should not need the [http://www.microsoft.com/downloads/details.aspx?FamilyID=EDB98FFA-A59C-4C23-9B92-BA304F188314&displaylang=en DirectX SDK] (337MB) to compile VS, but it may be required to compile OGRE in the future.
# Disable Intellisense: Microsoft provides no GUI for this, but it is recommended unless you want to eat up twice the RAM and wait 10-20 seconds between saving each file.
#* Browse to your VC8 install.
#* Go to the VC/vcpackages folders and rename the "feacp" DLL file to anything else like "feacp_backup.dll". This should not break anything... it will only disable IntelliSense.
# Checkout the Vegastrike project as described earlier.
# Open the "vega-vc8" project using the IDE.
# The compilation should go for the most part smoothly. If you encounter any problems, please tell us in the [http://vegastrike.sourceforge.net/forums/ forum] or specifically on [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=6251 this thread].
#* Note that Debug versions will be very slow (I get 5 frames/second on my Pentium3 1GHz machine using debug VS).

==Visual Studio 7.x==

===Compiling from the command line with Visual Studio===
Here is a batch file that could be used to checkout everything and then compile all projects (copy and paste in <code>makeall.bat</code>), if you were going somewhere for a few hours and wanted to get a working project when you got back:
<pre>
@echo off
mkdir vegastrike
cd vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vega-vc7
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/
cd vega-vc7
echo Building project...
"C:\VC7\Common7\IDE\devenv.exe" vegastrike.sln /BUILD Debug
cd ..
cd ..
</pre>

'''NOTE''': You must replace the "<code>C:\vc7</code>" with the directory where you installed visual c++ 7 and replace the "<code>Debug</code>" on the same line with "<code>Release</code>" if you want a release build.

===Compiling with the Visual Studio GUI===
''(This is written with Visual C++ .NET Standard in mind)''

Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], use Visual Studio to open vegastrike.sln, found in the vega-vc7 directory. When compiling for release, select "Release Boost 131" from the drop-down menu on the toolbar. Right-click on the "vegastrike" project in the "solution explorer" sidebar, and then select "Build".

==Visual C++ Toolkit 2003==
This is a [http://msdn.microsoft.com/visualc/vctoolkit2003/ free download] from Microsoft, and is the same compiler and linker as Visual Studio 2003.

Note, you must have Windows XP or 2000 in order to install the toolkit. (formerly said only Windows XP, but this is not true according to their download page)

===Downloads===
* Install the [http://msdn.microsoft.com/visualc/vctoolkit2003/ Visual C++ Toolkit 2003] from the Microsoft web site.
* Install the [http://www.microsoft.com/msdownload/platformsdk/sdkupdate Windows Platform SDK] from the Microsoft web site. You can take any of the 3 versions available.
* Install the [http://www.codeblocks.org/downloads.shtml Code::Blocks] (alternative download site on [http://prdownloads.sourceforge.net/codeblocks/ Sourceforge]). You can take the full version or the core only, since we will use the VS 2003 TK.

===Configuring Code::Blocks===
* Run CodeBlocks. The first time you install it, you will be listed with a set of compilers. Select Microsoft Visual C++ Toolkit, and click '''Set As Default'''.
* For configuration you have to include the location of the Windows Platform SDK. Go to '''Settings''' -> '''Compiler''' in the menu. Click the '''Directories''' tab. Add the directory "<code>C:\Program Files\Microsoft SDK\bin</code>" to the Resource Compiler tab.

===Compiling with Code::Blocks and Visual C++ Toolkit===
Once you have checked out the vegastrike and vega-vc7 modules from [[HowTo:Checkout CVS|CVS]], import the vegastrike.sln file, found in the vega-vc7 directory into Code::Blocks using '''Project->Import->MS Visual Studio Solution''' in the menu.

===Note (CVS version as of 14 Nov 2005===
Using the most recent CVS versions (and 2003/Runtime versions from Microsoft) I had to remove /W from the build options '''Project Build Options > Compiler Options > Other Options'''

=See Also=
* [[HowTo:Checkout SVN|Checking out SVN]]
* [http://www.codeblocks.org Code:Blocks IDE]

----
{{NAV_Manual |
| previous=[[HowTo:Checkout SVN|Checkout SVN]]
| up=[[HowTos]]
| next=[[HowTo:Cygwin Compiling|Cygwin Compiling]]
}}

[[Category:HowTos|VCpp Compiling]]

HowTo:Compile on OSX

2008-05-02T04:29:37Z

Nachtwolf: /* Getting the SVN-files */ data4.x

{{NAV_Manual |
| previous=[[HowTo:Compile_from_CVS|Compiling from SVN under your favourite Unixlike OS ]]
| up=[[HowTos]]
| next=[[HowTo:Use GDB|Using GDB]]
}}
----
How to compile from SVN under OSX.

==Getting the SVN-files==

* Checkout the following modules ...
** data package: <code>data</code>
** code package: <code>vegastrike</code>
* Visit [[HowTo:Checkout SVN]] to see how you check these modules out.

==Requirements==
In order to compile Vega Strike there are a few things to check:
* Ensure you have installed XCode Tools from your OS installation disc.
** Various gcc versions included in XCode Tools releases may have bugs preventing the compilation of Vega Strike. Vega Strike is known to work, on OSX, with gcc version ''powerpc-apple-darwin8-gcc-4.0.0 (GCC) 4.0.0 20041026''
** You should also install the Mac OSX 10.3.9 SDK from the same disk.
* Using [http://fink.sourceforge.net/ Fink], make sure you install the following libraries:
** <code>libpng</code> + <code>libpng-devel</code> <-- libpng 3 is recommended.
** <code>python</code> and <code>python-dev</code> <-- 2.2.1
** <code>expat</code>
** <code>(lib)jpeg</code> + <code>libjpeg-devel</code>
* Download the [http://www.libsdl.org/index.php SDL] source tarball, version 1.2.10 or later, compile, and install.
* Download and install the [http://developer.creative.com/articles/article.asp?cat=1&sbcat=31&top=38&aid=97 OpenAL] framework. (Footnote: This is a PPC only framework. Intel core machines may require to compile OpenAL from source.)

==Compiling==
The compile procedure should look like the following listing. Remember the configure part depends on above requirements.
<pre>
cd ./vegastrike
./bootstrap-sh
./configure
make vegastrike
make soundserver
</pre>
Note: You will require various options on configure, to specify the paths to the various libraries you have installed.
Note: If you intend to build a binary to replace the that packaged in a release (ie in a .app), then you must use the configure command --enable-macosx-bundle

==Compiling under MacIntel==
In the vegastrike directory there is a script called intel-mac-conf.sh, edit this file in vi and point it to your dependencies directories (i.e for fink /sw/bin /sw/inc etc. or for Darwin Ports /opt/local/bin /opt/local/inc etc.)

*Note: the python from Darwin Ports did not seem to play with the configure script and I had to install python from fink to get the configure script to work.

Ok, Now run the script.
*Note: For some reason the configure script forces itself against the 10.3.9.sdk, that is no good for us as when you try to build the process has a fit as we have an intel processor and it needs a powerpc to compile, so navigate in finder to your source directory and open configure.ac, do a find and replace and replace all the MacOSX10.3.9.sdk with MacOSX10.4u.sdk, save the file and we should be set to go.

Do a make vegastrike, the shell script as been designed to create us a bundle app, once the build is finished just copy this into your existing bundle.

=See also=
* [[HowTo:Compile_from_CVS|Compiling from SVN under your favourite Unixlike OS ]]
* [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=4185 "make clean/distclean" thread in the forum] - A quite helpful thread about the make process.
* [http://thewillofomega.googlepages.com/vegastrikedev Dandandaman's website about VS on Mac] including SVN builds.

----
{{NAV_Manual |
| previous=[[HowTo:Compile_from_CVS|Compiling from SVN under your favourite Unixlike OS ]]
| up=[[HowTos]]
| next=[[HowTo:Use GDB|Using GDB]]
}}
[[Category:HowTos|Compile from CVS]]

HowTo:Compile from SVN on Linux

2008-05-02T04:21:45Z

Nachtwolf: Updated howtos

{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
----
How to compile from SVN under Linux.

''See also: [[HowTo:Cygwin Compiling]], [[HowTo:VCPP Compiling]]''

==Getting the SVN-files==

* Checkout the following modules ...
** data package: '''data''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data)
** code package: '''vegastrike''' (repository link: https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike)
* Visit [[HowTo:Checkout SVN]] to see how you check these modules out.

==Requirements==
In order to compile Vegastrike there are a few things to check:
* Make sure you have these packages installed ...
** '''make'''
** '''gcc'''
** '''automake''' at least version 1.5
** '''autoconf''' at least version 2.53
** '''X11'''...
** '''libpng''' + '''libpng-devel''' <-- libpng 3 is recommended.
** '''python''' and '''python-dev''' <-- 2.2.1
** '''expat''' + '''expat-devel'''
** '''(lib)jpeg''' + '''libjpeg-devel'''
** '''opengl''' (see below) (you probably already have it)
** '''glut''' + '''glut-devel'''
** '''openal''' + '''openal-devel'''
** '''libgtk2.0''' + '''libgtk2.0-devel''' or '''libgtk1.2''' + '''libgtk1.2-devel'''
** '''inetutils'''

This probably should do the trick in debian/ubuntu:

<pre>
sudo apt-get install libpng12-0 libpng12-dev python2.5-dev libexpat1-dev libjpeg62-dev glutg3-dev libopenal-dev libgtk2.0-dev inetutils-inetd build-essential libgl1-mesa-dev automake1.9 autoconf2.13
</pre>

==Compiling==
The compile procedure should look like the following listing. Remember the configure part depends on above requirements. Though autoconf may not work, if so just skip it.
<pre>
cd ./vegastrike
./bootstrap-sh
./configure --enable-debug
make
make install # [AS ROOT]
</pre>

* To be sure '''set the data dir''' to your vs-data dir:
<pre>
./configure --with-data-dir=<DIR> ........
</pre>
* When using '''libpng 1.2''',
<pre>
--with-png-inc=<DIR>
</pre>
is needed. An example is
<pre>
--with-png-inc=/usr/include/libpng12/
</pre>
* If you don't want to compile with '''GTK''' just turn it off, however you will not get a setup program if you do this:
<pre>
./configure --disable-gtk ...........
</pre>
* If you only want the server, and want to disable all GUI components--This removes the dependency on X11, OpenGL, SDL, GLUT, OpenAL.
<pre>
./configure --disable-client ...........
</pre>
* See [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=1147 this] thread about boost versions. Set this option to 1.28, 1.29, 1.33, or "system" if the default does not compile.
<pre>
./configure --with-boost=<VER> ...........
</pre>

You will likely receive some error messages during any of these stages, especially during the configure part. If they tell you that your system is missing some development libraries, install them. How this is done depends strongly on your Linux distribution, but we will assist you in the [http://vegastrike.sourceforge.net/forums/viewforum.php?f=5 Compiling Problems forums]. You will be left with a file called "config.log" please attach that instead of copy-and-pasting thousands of lines of error messages. It's all in this file.

After you installed the missing libraries repeat the last (failed) step and continue.

'''Note:''' The configure script currently has a bug that can cause it to incorrectly report on the absence of GLUT. If you are sure you have installed glut-devel and are still seeing this error, check near the end of config.log to see if another library (such as libxmu or libxi) is the true culprit. [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=7562]

===Make===
Th final step for compiling is the make command. The Makefile should be able to compile most of the included utilities.

To compile mesher, for example, type:
<pre>make mesher</pre>
* Running
<pre>make all-am</pre>
reduces memory usage while compiling because there's only one instance of make instead of two. From [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=9510 this forum thread].
* The step
<pre>
make install
</pre>
is optional as the program is quite happy running in userland.

=See also=
* [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=4185 "make clean/distclean" thread in the forum] - A quite helpful thread about the make process.

----
{{NAV_Manual |
| previous=[[HowTo:Cygwin Compiling|Compiling with Cygwin]]
| up=[[HowTos]]
| next=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
}}
[[Category:HowTos|Compile from CVS]]

Development:SVN Tree

2008-05-02T04:17:19Z

Nachtwolf: updated name of datadir

{{parent_link|
|parent=[[Development]]}}

Note, if you are interested in how to check out a SVN repository, see [[HowTo:Checkout_SVN]]

Also, see [[HowTo:Compile_from_SVN]] for information on compiling an executable.

==trunk/data==
Game data for 0.5.0 and subsequent.

==trunk/history==

==trunk/masters==
Source images/data used to create textures in data

==trunk/modtools==

==trunk/translations==

==trunk/vega-proj==
Vega Strike project files for Microsoft Visual C++ 6.

'''Note: Visual C++ 6 is no longer supported, see [[HowTo:VCPP Compiling#Visual C.2B.2B 6.0 .28deprecated.29|HowTo:VCPP Compiling]].'''

==trunk/vega-vc7==
Vega Strike project files for Microsoft Visual C++ 7 (Visual Studio 2003 and above.)

==trunk/vega-vc8==
Vega Strike project files for Microsoft Visual C++ 8

==trunk/vegastrike==
This is the source code for the vegastrike game engine.

* Must add branch and tag info too.

[[Category:Development|SVN Tree]]
[[Category:SVN|SVN Tree]]

HowTo:Checkout SVN

2008-05-02T04:15:23Z

Nachtwolf: Updated Checkout page

{{NAV_Manual |
| previous=[[HowTo:Edit News|Edit News]]
| up=[[HowTos]]
| next=[[HowTo:VCPP Compiling|Compiling with VCPP]]
}}
----
If you're interested in an experimental version of Vega Strike, then SVN is what you'll be looking at.

'''Executive summary'''

Subversion, or SVN, is a mechanism by which developers can keep track of changes to their code and distribute these changes to the public in real time. This allows people to take advantage of software as it is being developed, between official releases.

[[HowTo:Checkout_SVN#Windows_Clients|Windows users]] can use an [[HowTo:Checkout_SVN#Tortoise_SVN|SVN client]] to check out the "win32" module, which contains game data and windows binaries.

[[HowTo:Checkout_SVN#Linux_Clients|Linux]] and [[HowTo:Checkout_SVN#Mac_OS_X_Clients|Mac OS X]] users must use an SVN client to check out the vegastrike module as well, which contains source code for them to compile. (Note that compiling Vega Strike on Mac OS X is considered very difficult.)

=What is SVN?=
SVN stands for '''S'''ub'''v'''ersio'''n''', a system similar to CVS. It allows developers to simultaneously work on a centralised project - in this case, that's Vega Strike.

Downloading ("checking out") and compiling the SVN-version often gives you access to features not included in the latest stable release of the program. SVN-based versions can be unstable and may not even work at all, but may hold advantages compared to stable versions.

==Structure==
Unlike a CVS repository, the top level of an SVN repository contains more than just the trunk. Vega Strike's SVN repository follows the standard layout, so the SVN root looks like this:
* '''branches''' - Independent copies of some or all of the trunk code. A developer making major changes, such as the ogre branch or major code cleanup will usually make a branch so they can keep track of their progress without breaking the trunk code for everyone else. These changes eventually are merged back into the trunk.
* '''tags''' - Revisions which have been marked. For instance, a tag might be made for a stable release so that svn users can update to it via the ''svn sw'' command. The VS developers like to use tags to mark milestones in the code, such as before or after a major change, so you'll see a lot of tags.
* '''trunk''' - The main trunk code, as would be seen in the root of a CVS repository. This contains a number of modules filled with code and data.

==Modules==
Vega Strike's SVN repository holds several subdirectories, which can either be checked out separately or altogether. The most notable ones are included below.

* '''data''' - data files of the game. This consists mainly of models, textures and backgrounds. Required to play the game.
* '''win32''' - Windows Binaries as well as includes an "external" to the data directory.
* '''mac''' - Macintosh Package, as well as an "external" to the data directory.
* '''masters''' - The original master files that created the game data (original meshes and uncompressed textures).
* '''history''' - Old descriptions of factions and species.
* '''modtools''' - Tools to aid creation and modification of game files (campaigns and units)
* '''translations''' - Translations of Vega Strike data files into other languages.
* '''vega-proj''' - Deprecated Visual C++ 6 projects. (See [[HowTo:VCPP_Compiling#Visual_C.2B.2B_6.0_.28deprecated.29 here]])
* '''vega-vc7''' - Visual Studio 7 projects. (See [[HowTo:VCPP_Compiling#Visual_Studio_7.x here]]
* '''vega-vc8''' - Visual Studio Express 2005 projects. (See [[HowTo:VCPP_Compiling#Visual_C.2B.2B_8.0_.282005_Express.29 here]])
* '''vegastrike''' - the game base code.
* '''data6.x''' - Data for the [[Development:Ogre|Ogre port]]. You may download the OGRE branch using this URL: http://vegastrike.svn.sourceforge.net/svnroot/vegastrike/branches/ogre_branch/

The Subversion tree can be browsed via a web interface: http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/

'''→''' ''See also: [[Development:CVS Tree]]''

=Linux Clients=

==Command-line svn==

===Website===
http://subversion.tigris.org/

===Description===
The linux-command `svn' is the most basic Subversion client.

===Using svn for downloading vs-devel===
Checking out (downloading) the Vega Strike svn-modules is easy. The general syntax is
<pre>
svn co [repo]/trunk/[module] [target-directory]
</pre>

<pre>
svn co --ignore-externals https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk vegastrike
</pre>
...will download the entire tree (all modules) into directory `vegastrike'. But '''don't do this'''! Such a command would download data for both the normal and ogre branches, plus Visual Studio projects for ALL supported versions and goodness knows what else.

You should really only download individual modules, and a similar syntax can be used. For example, to download the data module,
<pre>
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data data
</pre>
...will suffice. (Leaving off the target directory will make svn try check out into the ''working directory''.)
In order to get all the files required to compile the game, checkout the following modules:
* data
* vegastrike

==Tutorial to download, setup and run the development version==
In order to run the development version of Vega Strike, the executables expect to find the data to be in certain places relative to them. This short tutorial deals with these specifics on Linux operating systems. (more experienced MacOSX users can this, or they can read [[HowTo:Checkout_SVNMac]]

So, let's start.
* Create a directory where you would like your copy of the Vega Strike development version to live in. For example purposes we will create a directory called ''VegaStrike'' in our user's home-directory.
<pre>~> mkdir VegaStrike</pre>
* Change into this newly created directory. In our case:
<pre>~> cd VegaStrike</pre>

===Initial downloading (check-out)===
Now we can start downloading the packages from the SVN repository. If you download them directly into your Vega Strike directory they will be just in the right place.

To save on download bandwidth, you can download a snapshot of the SVN tree, and then just update that to the current revision. One big compressed file will download much faster than having SVN get each file individually. Snapshots available here: http://vegastrike.sourceforge.net/forums/viewtopic.php?t=6749. Also here (not sure if this second one includes the .svn directories needed to update it with svn):
http://sourceforge.net/project/showfiles.php?group_id=181552&package_id=211092&release_id=463105.
If you run into any problems, it will work fine to follow the instruction below, using svn to do the whole checkout.

* Download (check-out) the source code package ''vegastrike'', and the content package ''data'' package.
<pre>~/VegaStrike> svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
~/VegaStrike> svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data</pre>
This leaves you with three new directories inside your Vega Strike directory called as the packages are.

''Note:'' If you are having problems with SVN due to connecting via a proxy, try to solve them using the method described here: http://subversion.tigris.org/faq.html#proxy

===Building===
{{FIXME}} This should merged with the [[HowTo:Compile_from_SVN]] page. (Partially done)

The [[HowTo:Compile_from_SVN]] page has a list of some options that you can pass to ./configure

===Setup===
This step is not necessary--the binaries will figure out where they are with respect to the data directory.

To run Vega Strike, the built executables need all the configuration and data files to be in the right place relative to them. Currently, the executables (''vegstrike'' and ''vssetup'') reside in the source code directory. But they can be run out of the ''data'' directory. Therefore, we will create a link.
* Change in to the ''data'' directory. (We are still in the source code directory ''vegastrike''.)
<pre>~/VegaStrike/vegastrike> cd ../data</pre>
* Create symbolic links to the executables in the source code directory.
<pre>~/VegaStrike/data> ln -s ../vegastrike/vegastrike
~/VegaStrike/data> ln -s ../vegastrike/vssetup</pre>
* After that, you must run "'''./vssetup'''" inside the '''data''' folder, or any folder which has the correct '''setup.config''' and '''vegastrike.config'''.
If we had made copies or moved the files instead of symbolic linking, we would have to do the procedure of copying or moving every time we build the executables from source.

===Running and configuring===
* To run Vega Strike you have to start it from the ''data'' directory.
<pre>~/VegaStrike/data> ./vegastrike</pre>
* Optionally you can create a short cut to this application onto your desktop or in your start menu. Simply point it to the ''vegastrike'' executable.
* If you need to adjust screen resolutions, input devices and key-mappings, do so by editing the configuration file ''vegastrike.config''. The default configuration file resides in the ''data'' directory. You can change that or you can make your own user specific version by first copying it into your ''.vegastrike'' (hidden directory) directory in your user's home directory.

===Staying updated with the development version===
As development progresses the repository changes. In order to update your working copy you need to do the following.
* Change into the package's directory you want to update. In our example all the packages were stored in a directory called ''VegaStrike''. Let's assume we want to update the ''data'' package.
<pre>~> cd VegaStrike
~/VegaStrike> cd data</pre>
* Update from the SVN repository.
<pre>~/VegaStrike/data> svn update</pre>
* Do this for every package you want to update. Exchange ''data'' with ''vegastrike''.
* If something changed in the ''data'' package, you don't need to recompile.
* If something changed in the source code package ''vegastrike''. You only need to repeat the building part of this tutorial and in case you did not create symbolic links the copying or moving procedure for the executables in the setup part of this tutorial. You should not need to type "make clean", however if you experience errors like "unresolved external symbol" it may remedy that error.

=Windows Clients=

Note: For windows, only the '''win32''' module is necessary to play the game. It will download the "data" directory You will find the executable program inside the "bin" folder.

If you are interested in compiling the code, you will need the '''vegastrike''' module, as well as the appropriate vega-project module for your Visual C++ version. See [[HowTo:VCPP_Compiling]] for compiling info.

Some people have problems with the latest executable relating to Visual C++ 8. If you want an older version of the executable compiled with VC7, you can browse the repository here:
http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/win32/bin/vegastrike.exe?view=log

==Tortoise SVN==

===Website===
http://tortoisesvn.tigris.org/

===Description===
Just like TortoiseCVS, Tortoise SVN lets you work with files under SVN version control directly from Windows Explorer. It's freely available under the GPL.

With TortoiseSVN you can directly check out modules, update, commit and see differences by right clicking on files and folders within Explorer. You can see the state of a file with overlays on top of the normal icons within Explorer. It even works from within the file open dialog.

===Usage===
* Download and Install Tortoise SVN from http://tortoisesvn.tigris.org
* Create a new folder in Windows Manager where you will download your modules (called Sandbox, SVN or similar working location name);
* Within that folder, create another folder (VegaStrike);
* Right click on the folder created and select SVN Checkout. This brings up the checkout configuration screen;
* Input the URL of the repository into the dialog box:
<pre>
https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/win32
</pre>
**You may also use the built-in repository browser to select the module you wish to check out.
* Click OK to begin checkout of the module.
[Edit - Turbo: The download is 600+ MB and will take some time. I did not have to install the program -- after downloading, run the Setup program in the BIN folder, then you can run VEGASTRIKE.EXE to play.]

=Mac OS X Clients=

NOTE: Leopard (10.5) comes with a SVN client.

==Command Line Client==

===Website===
http://metissian.com/projects/macosx/subversion/

(or http://pdb.finkproject.org/pdb/search.php?summary=svn for Fink packages.)

Footnote:
metissian.com does not maintain current binaries. A better source would be (ordered from most current to most convenient):

(a) http://subversion.tigris.org/ for current source code.

(b) use Fink or MacPorts to get (usually) current source code.

(c) http://www.codingmonkeys.de/mbo/ for a (usually) current install package.

(d) XCode3 includes svn as part of the default installation (But not XCode2).

==SCPlugin==

===Website===
http://scplugin.tigris.org/

===Description===
"The goal of the SCPlugin project is to integrate Subversion into the Mac OS X Finder. The inspiration for this project came from the TortoiseSVN project."

====Usage====
Must have command line client installed.

{{Fixme}}-WRITEME

*[http://www.joshbuhler.com/2005/07/05/setting-up-the-subversion-client-on-mac-os-x/ A good tutorial on setting up SVN for OSX]

==Other==
*[http://www.lachoseinteractive.net/en/community/subversion/svnx/features/ svnX]

==Building==

Note, if you are not interested in compiling your own version, see [[HowTo:Checkout_SVNMac]] to get the whole package.

'''→''' ''See [[HowTo:Compile on OSX]]''

----
{{NAV_Manual |
| previous=[[HowTo:Edit News|Edit News]]
| up=[[HowTos]]
| next=[[HowTo:Checkout CVS|Checkout CVS]]
}}

[[Category:HowTos|Checkout SVN]]

HowTo:Checkout SVNMac

2008-05-02T04:04:17Z

Nachtwolf: Updated mac SVN documentation

July 26th, 2007
This is a step by step instruction for how to download the latest version of Vega Strike on a Macintosh, with no requirements of programming skill.
Note that this has only been tested on one computer, and if it doesn't work for you, or if VS crashes, post a message at the forums and tell us how far you made it.

'''Step 1: Download an SVN client'''

''Leopard'' (10.5) now comes with SVN, so you do not need to worry about this. In Leopard, you just say "svn co".

This one worked for us: [[http://metissian.com/projects/macosx/subversion/]]
Make sure that you have the version that works on your system.
Install the client - open the .pkg-file and follow the instructions.
Now, remember this command: "/usr/local/bin/svn co". You will use it a couple of times, co means Checkout.

'''Step 2: Download the VS Resource package'''

Go to Applications/Utilities and open the program Terminal.
What you have to do is write:

svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/mac

You can copy-paste it if you like (if you installed Subversion, use "/usr/local/bin/svn" instead of "svn". Then wait a couple of seconds, and some text will show up. You will be asked if you want to allow the site to download files to your computer. This is important: CHOOSE PERMANENTLY by pressing p and enter.

After a couple of seconds, a long list of files will show up, downloading one file at a time. Let this finish. The terminal will say that the checkout is finished after a while (took me hours with my slow connection). Note that if your connection terminates while downloading, all you have to do is write the same command again and it will pick up where it left off.

'''Step 3: Still some things to do'''

If you start VS now, you will probably not see what you expected. The Campaign button does not do what it is supposed to do, so we will have to do a tiny work-around.
Go to Resources and find the file New_Game. Copy this file and rename it to something like Cool or whatever you like. Move the file Cool to your home directory. Open the terminal and write the code: mv Cool ~/.vegastrike/save/
mv moves files between directories, ignoring whatever restriction you will find. You might need to enter your password.

'''Step 4: Play'''

Now, forget everything you did and pretend this never happened. Open the folder VS and double click on the application. The game will go through a loading screen and you will end up in a menu. Choose Load Save and load the file "Cool". There you go, the latest version of Vega Strike.

Development

2008-05-02T03:41:10Z

Nachtwolf: /* Code-related */ We now use svn

{{Wiki_Nav_Index}}

=Development pages=
==Status/task list pages==
* [[Development:Compatability]] -Making sure the game works on all hardware
* [[Development:Roadmap|Roadmap]] - The Vega Strike development roadmap.
* [[Development:Rebalance]] - Information and task list for the Rebalance.
* [[Development:Ogre]] - Information on the OGRE port.
* [[Development:3D_Models|3D Models]] - Organisation and contribution information.
* [[Development:2D_Images|2D Images]] - Organisation and contribution information.
* [[Development:Audio|Sound & Music]]
* [[Development:Performance]] - Goals to achieve required performance
* [[Development:AI Navigation]] - Overhauling the ships' navigation routines
* [[Development:Misc Engine Work]] - Various engine and backend work information.

==Developer information pages==
*[[HowTo:Contribute|The Vega Strike Contributor's Guide]]

===Code-related===
* [[Development:Dependencies|Dependencies]] - A guide to system dependencies, broken down by subsystem.
* [[Development:SVN Tree|SVN Tree]] - A guide to the layout of the Subversion tree.
* [[Development:Code style|Code style]] - A guide/manual to write code for Vegastrike that fits in and is readable.
* [[Development:Network|Network]] - Everything network related goes in here.
** [[Development:Network:Packet format|Packet format]] - A description of the packet format that had been implemented a few years ago.
** [[Development:Network:Todo|Todo]] - What still needs to be done.
** [[Development:Network:Testing|Testing]] - Testing the network code.
* [[Development:Keyboard layout|Keyboard layout]] - Discuss and display new keyboard layouts here.
* [[Development:Scripts & Tools|Scripts & Tools]] - to make your life easier
** [[Development:Script:obj2obj converter|obj2obj converter]] (Perl, commandline) - Converts obj files to cockpit files. or extracts tag-data from the models. (''At least that's what is planned, Testing under Win32/Linux. [[User:pontiac|Pontiac]]'')

===Data-related===
* [[Cargo]] - Detailed descriptions of cargo items, listed by category.
* [[Development:Quests_&_Campaigns|Quests & Campaigns]] Reference portal for creation of campaigns, missions, quests & adventures.
** [[Development:Quests|Quests]] Creating quests and adventures
** [[Development:Missions|Developing Missions]] Creation of missions
** [[Development:Campaigns]] Making campaigns
* [[Development:Balancing|Faction Balancing]] - General guidelines to keep in mind when play balancing the Vega Strike factions.

===Art-related===
Please read this '''[[Development:Graphics_Requirements]]''' page first before continuing to the specific requirements.
See also: [[Links:Graphic_Applications]] and [[Links:3D_Applications]] for applications listings.

* [[Development:Cargo (graphics)|Creating Cargo Graphics]] - Images to be displayed in the trading interface for cargo items.
* [[Development:Orbital Planet Surfaces|Orbital Planet Surfaces]] - General guidance for development of planet surfaces visible from orbit.
* [[Development:System_Backgrounds|Generating star system backgrounds]]
* [[Development:Base_Backgrounds|Creating and adding backgrounds for bases, planets, or capital ships]]
* [[Development:Logos & Signage|Logos & Signage]]
* [[Development:HUD (graphics)|HUD (graphics)]]
* Ship and Installations models
** [[Development:Model Guidelines|Guidelines for creating models]] - General guidance for development of models for Vega Strike.
** [[Development:Texture Guidelines|Guidelines for creating ship materials]] - General guidance for development of materials for Vega Strike models.
** [[Development:3D_Models|3D models list and status]]

===Configuration ===
* [[Manual:Config:Advanced:Variables|Configuration Variables]]
* [[CONFVAR|CONFVAR - Complete Variable Listing]]

===Internationalization/Localisation-related===
* [[Development:Translations|Translation projects]]

=== Common topics ===
* [[Development:Realism vs Believability|Realism vs Believability]]
* [[Development:Behaviour of the SPEC drive and insystem flight in general|Behaviour of the SPEC drive and insystem flight in general]]
* [[Development:Economy|Economy]] - How ingame economy should work.
* [[Development:Political system|Political system]]
* [[Development:Ingame library|Ingame library]] - How can/should it be done? .. if at all.

=See also=
* [[HowTos]]
* [[FAQ:Feature_Requests|Feature Requests]]

[[Category:Development]]

{{warning_text |
| text=Most of the content located under [http://vegastrike.sourceforge.net/phpwiki/index.php/VsModsVegastrike VsModsVegastrike] should be moved to this page or better it's namespace '''Development:xxx'''. Please classify all pages with <code><nowiki>[[Category:Development]]</nowiki></code>
}}

HowTo:Checkout SVN

2008-04-26T22:01:39Z

Nachtwolf: /* Modules */ Updated info about masters and ogre port

{{NAV_Manual |
| previous=[[HowTo:Edit News|Edit News]]
| up=[[HowTos]]
| next=[[HowTo:VCPP Compiling|Compiling with VCPP]]
}}
----
If you're interested in an experimental version of Vega Strike, then SVN is what you'll be looking at.

'''Executive summary'''

Subversion, or SVN, is a mechanism by which developers can keep track of changes to their code and distribute these changes to the public in real time. This allows people to take advantage of software as it is being developed, between official releases.

[[HowTo:Checkout_SVN#Windows_Clients|Windows users]] can use an [[HowTo:Checkout_SVN#Tortoise_SVN|SVN client]] to check out the data4.x module, which contains game data and windows binaries.

[[HowTo:Checkout_SVN#Linux_Clients|Linux]] and [[HowTo:Checkout_SVN#Mac_OS_X_Clients|Mac OS X]] users must use an SVN client to check out the vegastrike module as well, which contains source code for them to compile. (Note that compiling Vega Strike on Mac OS X is considered very difficult.)

=What is SVN?=
SVN stands for '''S'''ub'''v'''ersio'''n''', a system similar to CVS. It allows developers to simultaneously work on a centralised project - in this case, that's Vega Strike.

Downloading ("checking out") and compiling the SVN-version often gives you access to features not included in the latest stable release of the program. SVN-based versions can be unstable and may not even work at all, but may hold advantages compared to stable versions.

==Structure==
Unlike a CVS repository, the top level of an SVN repository contains more than just the trunk. Vega Strike's SVN repository follows the standard layout, so the SVN root looks like this:
* '''branches''' - Independent copies of some or all of the trunk code. A developer making major changes, such as the ogre branch or major code cleanup will usually make a branch so they can keep track of their progress without breaking the trunk code for everyone else. These changes eventually are merged back into the trunk.
* '''tags''' - Revisions which have been marked. For instance, a tag might be made for a stable release so that svn users can update to it via the ''svn sw'' command. The VS developers like to use tags to mark milestones in the code, such as before or after a major change, so you'll see a lot of tags.
* '''trunk''' - The main trunk code, as would be seen in the root of a CVS repository. This contains a number of modules filled with code and data.

==Modules==
Vega Strike's SVN repository holds several subdirectories, which can either be checked out separately or altogether. The most notable ones are included below.

* '''data4.x''' - data files of the game. This consists mainly of models, textures and backgrounds. Required to play the game.
* '''masters''' - The original master files that created the game data (original meshes and uncompressed textures).
* '''history''' - Old descriptions of factions and species.
* '''modtools''' - Tools to aid creation and modification of game files (campaigns and units)
* '''translations''' - Translations of Vega Strike data files into other languages.
* '''vega-proj''' - Deprecated Visual C++ 6 projects. (See [[HowTo:VCPP_Compiling#Visual_C.2B.2B_6.0_.28deprecated.29 here]])
* '''vega-vc7''' - Visual Studio 7 projects. (See [[HowTo:VCPP_Compiling#Visual_Studio_7.x here]]
* '''vega-vc8''' - Visual Studio Express 2005 projects. (See [[HowTo:VCPP_Compiling#Visual_C.2B.2B_8.0_.282005_Express.29 here]])
* '''vegastrike''' - the game base code.
* '''data6.x''' - Data for the [[Development:Ogre|Ogre port]]. You may download the OGRE branch using this URL: http://vegastrike.svn.sourceforge.net/svnroot/vegastrike/branches/ogre_branch/

The following modules are deprecated, have been removed from current revisions, and are listed for historical purposes only:
* '''data''' - deprecated 3.x and lower data files.
* '''charserver'''
* '''vega-new-proj''' - even older VC6 project - don't use.
* '''evilwm''', '''ethereal''', '''virtuanet''' - other projects with temporary repositories
* '''mission_select''' - Functionality also in Launcher, and also not used often.
* '''texturizer''' - If you can get it to compile, I believe it may still work.
* '''syseditor''' - If you like typing in coordinates of every planet by hand in an ugly console interface, go ahead.

The Subversion tree can be browsed via a web interface: http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/

'''→''' ''See also: [[Development:CVS Tree]]''

=Linux Clients=

==Command-line svn==

===Website===
http://subversion.tigris.org/

===Description===
The linux-command `svn' is the most basic Subversion client.

===Using svn for downloading vs-devel===
Checking out (downloading) the Vega Strike svn-modules is easy. The general syntax is
<pre>
svn co [repo]/trunk/[module] [target-directory]
</pre>

<pre>
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk vegastrike
</pre>
...will download the entire tree (all modules) into directory `vegastrike'. But '''don't do this'''! Such a command would download data for both the normal and ogre branches, plus Visual Studio projects for ALL supported versions and goodness knows what else.

You should really only download individual modules, and a similar syntax can be used. For example, to download the data4.x module,
<pre>
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data4.x data4.x
</pre>
...will suffice. (Leaving off the target directory will make svn try check out into the ''working directory''.)
In order to get all the files required to compile the game, checkout the following modules:
* data4.x
* vegastrike

==Tutorial to download, setup and run the development version==
In order to run the development version of Vega Strike, the executables expect to find the data to be in certain places relative to them. This short tutorial deals with these specifics on Linux operating systems. (It also applies for Mac OS X users.)

So, let's start.
* Create a directory where you would like your copy of the Vega Strike development version to live in. For example purposes we will create a directory called ''VegaStrike'' in our user's home-directory.
<pre>~> mkdir VegaStrike</pre>
* Change into this newly created directory. In our case:
<pre>~> cd VegaStrike</pre>

===Initial downloading (check-out)===
Now we can start downloading the packages from the SVN repository. If you download them directly into your Vega Strike directory they will be just in the right place.

To save on download bandwidth, you can download a snapshot of the SVN tree, and then just update that to the current revision. One big compressed file will download much faster than having SVN get each file individually. Snapshots available here: http://vegastrike.sourceforge.net/forums/viewtopic.php?t=6749. Also here (not sure if this second one includes the .svn directories needed to update it with svn):
http://sourceforge.net/project/showfiles.php?group_id=181552&package_id=211092&release_id=463105.
If you run into any problems, it will work fine to follow the instruction below, using svn to do the whole checkout.

* Download (check-out) the source code package ''vegastrike'', and the content package ''data4.x'' package.
<pre>~/VegaStrike> svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
~/VegaStrike> svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data4.x</pre>
This leaves you with three new directories inside your Vega Strike directory called as the packages are.

''Note:'' If you are having problems with SVN due to connecting via a proxy, try to solve them using the method described here: http://subversion.tigris.org/faq.html#proxy

===Building===
{{FIXME}} This should merged with the [[HowTo:Compile_from_SVN]] page. (Partially done)

The [[HowTo:Compile_from_SVN]] page has a list of some options that you can pass to ./configure

===Setup===
To run Vega Strike, the built executables need all the configuration and data files to be in the right place relative to them. Currently, the executables (''vegstrike'' and ''soundserver'') reside in the source code directory. But they have to be run out of the ''data4.x'' directory. Therefore, we will create a link.
* Change in to the ''data4.x'' directory. (We are still in the source code directory ''vegastrike''.)
<pre>~/VegaStrike/vegastrike> cd ../data4.x</pre>
* Create symbolic links to the executables in the source code directory.
<pre>~/VegaStrike/data4.x> ln -s ../vegastrike/vegastrike
~/VegaStrike/data4.x> ln -s ../vegastrike/soundserver
~/VegaStrike/data4.x> ln -s ../vegastrike/vssetup</pre>
* After that, you must run "'''./vssetup'''" inside the '''data4.x''' folder, or any folder which has the correct '''setup.config''' and '''vegastrike.config'''.
If we had made copies or moved the files instead of symbolic linking, we would have to do the procedure of copying or moving every time we build the executables from source.

===Running and configuring===
* To run Vega Strike you have to start it from the ''data4.x'' directory.
<pre>~/VegaStrike/data4.x> ./vegastrike</pre>
* Optionally you can create a short cut to this application onto your desktop or in your start menu. Simply point it to the ''vegastrike'' executable in the ''data4.x'' directory.
* If you need to adjust screen resolutions, input devices and key-mappings, do so by editing the configuration file ''vegastrike.config''. The default configuration file resides in the ''data4.x'' directory. You can change that or you can make your own user specific version by first copying it into your ''.vegastrike'' (hidden directory) directory in your user's home directory.

===Known bugs and work-arounds===
This issue has been fixed in the latest SVN versions.

In case you are using an older version (i.e. pre-10700 or so) and Vegastrike does not run (gives a "Cannot open display :0.0" error), if are willing to sacrifice some security on multi-user systems, you may have to use this command to run vegastrike:
<pre>xhost +local:</pre>If you do not want to compromise security, update to the latest revision.

===Staying updated with the development version===
As development progresses the repository changes. In order to update your working copy you need to do the following.
* Change into the package's directory you want to update. In our example all the packages were stored in a directory called ''VegaStrike''. Let's assume we want to update the ''data4.x'' package.
<pre>~> cd VegaStrike
~/VegaStrike> cd data4.x</pre>
* Update from the SVN repository.
<pre>~/VegaStrike/data4.x> svn update</pre>
* Do this for every package you want to update. Exchange ''data4.x'' with ''vegastrike''.
* If something changed in the ''data4.x'' package, you don't need to recompile.
* If something changed in the source code package ''vegastrike''. You only need to repeat the building part of this tutorial and in case you did not create symbolic links the copying or moving procedure for the executables in the setup part of this tutorial. You should not need to type "make clean", however if you experience errors like "unresolved external symbol" it may remedy that error.

=Windows Clients=

Note: For windows, only the '''data4.x''' module is necessary to play the game. You will find the executable program inside the "bin" folder.

If you are interested in compiling the code, you will need the '''vegastrike''' module, as well as the appropriate vega-project module for your Visual C++ version. See [[HowTo:VCPP_Compiling]] for compiling info.

Some people have problems with the latest executable relating to Visual C++ 8. If you want an older version of the executable compiled with VC7, you can browse the repository here:
http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/data4.x/bin/vegastrike.exe?view=log

==Tortoise SVN==

===Website===
http://tortoisesvn.tigris.org/

===Description===
Just like TortoiseCVS, Tortoise SVN lets you work with files under SVN version control directly from Windows Explorer. It's freely available under the GPL.

With TortoiseSVN you can directly check out modules, update, commit and see differences by right clicking on files and folders within Explorer. You can see the state of a file with overlays on top of the normal icons within Explorer. It even works from within the file open dialog.

===Usage===
* Download and Install Tortoise SVN from http://tortoisesvn.tigris.org
* Create a new folder in Windows Manager where you will download your modules (called Sandbox, SVN or similar working location name);
* Within that folder, create another folder being the name of module you wish to checkout e.g. data4.x, vegastrike etc;
* Right click on the folder created and select SVN Checkout. This brings up the checkout configuration screen;
* Input the URL of the repository into the dialog box, for example data4.x will be;
<pre>
https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data4.x
</pre>
**You may also use the built-in repository browser to select the module you wish to check out.
* Click OK to begin checkout of the module.
[Edit - Turbo: The download is 600+ MB and will take some time. I did not have to install the program -- after downloading, run the Setup program in the BIN folder, then you can run VEGASTRIKE.EXE to play.]

=Mac OS X Clients=

==Command Line Client==

===Website===
http://metissian.com/projects/macosx/subversion/

(or http://pdb.finkproject.org/pdb/search.php?summary=svn for Fink packages.)

Footnote:
metissian.com does not maintain current binaries. A better source would be (ordered from most current to most convenient):

(a) http://subversion.tigris.org/ for current source code.

(b) use Fink or MacPorts to get (usually) current source code.

(c) http://www.codingmonkeys.de/mbo/ for a (usually) current install package.

(d) XCode3 includes svn as part of the default installation (But not XCode2).

==SCPlugin==

===Website===
http://scplugin.tigris.org/

===Description===
"The goal of the SCPlugin project is to integrate Subversion into the Mac OS X Finder. The inspiration for this project came from the TortoiseSVN project."

====Usage====
Must have command line client installed.

{{Fixme}}-WRITEME

*[http://www.joshbuhler.com/2005/07/05/setting-up-the-subversion-client-on-mac-os-x/ A good tutorial on setting up SVN for OSX]

==Other==
*[http://www.lachoseinteractive.net/en/community/subversion/svnx/features/ svnX]

==Building==
'''→''' ''See [[HowTo:Compile on OSX]]''

----
{{NAV_Manual |
| previous=[[HowTo:Edit News|Edit News]]
| up=[[HowTos]]
| next=[[HowTo:Checkout CVS|Checkout CVS]]
}}

[[Category:HowTos|Checkout SVN]]

Template:Oldversion

2008-04-07T07:18:29Z

Nachtwolf: Added an oldversion template

<div class="boilerplate metadata" id="attention" style="margin: 0 2.5%; text-align: justify; background: #ffAA33; color: black; padding: 0 10px; border: 1px solid #ff7777">
'''This page is for old versions of Vega Strike. Please disregard this information if you are using a new version. '''
</div>

Manual:Save and load

2008-04-07T07:13:58Z

Nachtwolf: Added oldversion tag to this page

{{oldversion}}

{{Languages|En|Manual:Save and load}}
{{NAV_Manual |
| previous=[[Manual:Running Vegastrike|Running Vegastrike]]
| up=[[Manual]]
| next=[[Manual:Config|Configure Vegastrike]]
}}
----
<table width=35% style="float:left;"><tr><td>__TOC__</td></tr></table>
= Commandline/Direct-Start (all users) =

All the Vega Strike savegames are in your home directory under <code>.vegastrike</code> (or in the vegastrike directory under <code>.vegastrike</code> under windows). Change the save game by editing the file <code>save.txt</code>. The file is called <code>save.4.x.txt</code> in Vegastrike4.x.

= Mac users =
...should do the following (because <code>.vegastrike</code> is a hidden directory):
{|
|
# In the finder choose '''Go To Folder''' from the '''Go''' menu.
# Type <code>~/.vegastrike</code> to open the vegastrike folder in a Finder window
# Drag the folder from the title bar of the Finder window while holding down the {{Key:EN:Alt}} and (command) {{Key:Apple}} keys to make an alias of this folder on your Desktop.
|}
= Launcher (windows/linux/unix) =

<table style="float: right;"><tr><td>http://vegastrike.sourceforge.net/albums/wiki_manual/launcher.jpg</td></tr></table>

There should be a program named "Launcher" in the vegastrike directory or Start Menu. This program provides a list of game choices:

== Start New Pilot ==
To start a new pilot (game) in the Vega Strike universe, select this button. If no scenario has been selected beforehand (below), this button loads the default Exploring the Universe scenario.

You start with a dinged up old Llama and head from your starting sector with the hope of finding profit and adventure on the frontier.

== Play Saved Pilot ==
This button loads the selected saved pilot to load into Vega Strike.

== Continue Last Game ==
This button loads your last saved pilot automatically into Vega Strike. If you do not choose a mission, you will start in the standard trading/bounty hunting mission. Differs from Play Saved Pilot in that you do not choose which saved game to load.

== Game Settings ==
This button accesses Vega Strike’s game settings for configuration. Refer to [[Manual:Config|Config]] for information on configuration selections.

== Recover from Autosave==
This button allows a player to recover their most recently played game into the selected save game upon next run. If the player quits or the player docks, and then dies, it will restore to the last saved position.

== Change Scenario ==
This allows you to select which Vega Strike scenario to play. To select, highlight the requested scenario and click “OK�?. Once selected, you start the scenario by selecting Start New Pilot Most scenarios do not involve save games and will ignore those options. Note that the default scenario will utilize the save game you specify. If you ignore this option you default to the standard Exploring the Universe scenario.

== Help ==
Pop up help window with this information.

== Exit Launcher ==
Exits the launcher.

= See also =
* [[Manual:Computer:Game menu]]
----
{{NAV_Manual |
| previous=[[Manual:Running Vegastrike|Running Vegastrike]]
| up=[[Manual]]
| next=[[Manual:Config|Configure Vegastrike]]
}}
[[Category:Manual|Save and load]]

Manual

2008-04-07T06:54:24Z

Nachtwolf: /* Installation */ Removed reference to launcher

{{Languages|En|Manual}}
{{Wiki_Nav_Index}}
{|width="100%"
|valign="top"|__TOC__
|valign="top" align="right"|http://vegastrike.sourceforge.net/albums/wiki_manual/cleaned3_shot_016_02_A5.png
|}

=Dedication=
This Player’s Guide is dedicated to Daniel ‘Hellcatv’ Horn and the Vega Strike development team for bringing us the Vega Strike game; to the coders, artists, designers and play-testers willing to devote their own time and effort to the creation of a great game; and of course to the players of Vega Strike, without whom this whole thing would be a pointless exercise.

=Introduction=

<big>'''''WELCOME''''' to ''Vega Strike'', a 3d OpenGL spaceflight simulator being developed for multi-platform play.</big>

Vega Strike allows players to explore a vastly dynamic universe where frontiers collide and you're just a pilot trying to make ends meet. How? That's your decision. Vega Strike is designed as a non-linear gaming experience, where you choose what action you want to take.

Vega Strike features a dynamic trading economy, allowing your character to operate as a merchant. Discover what trade routes bring in the most profit, what commodities make you the most money given your ship's cargo space limitations, accept cargo [[Manual:Computer:Missions_screen|missions]] and learn to avoid areas of danger (repairs eat into your profits!).

If you tire of making money on milk runs, or want to try something different, then there are other paths to success. Vega Strike features a mission generator, providing multiple missions to the experienced (and not so experienced) pilots. Engage in bounty hunts, patrols, battles and escort missions. Feel like travelling? Explore the dynamic universe and see the farthest reaches of known space. Want a walk on the wild side? You could always turn pirate! Just be prepared for the consequences.

Your ship just not doing the job you want it to? Vega Strike gives you the ability to purchase from a wide variety of ships capable of doing different jobs. Want to haul cargo? Fight battles? There's a ship for you. Your ship is fully customizable, so if you've got the [[Terminology:Credits|credit]], outfit your craft with the right tools for the job at hand.

Have a chat with the [[Manual:Location:Bar|bartender]] or view the [[Manual:Computer:News_screen|news broadcasts ]]to find out what's going on in the universe. While you're there, talk to the fixers, they may have a job that only you can do. But be warned, you never know where it may lead ...

* [[Vegastrike:License|License]] The license Vega Strike is released under (please do not edit)
* [[Vegastrike:Mission|Mission]] The Vega Strike Mission Statement (what it's all about)
* [[Vegastrike:Features|Features]] Why Vega Strike is the best game ever made
* [[Vegastrike:Credits|Credits]] The people who are making it happen

Winner of the Jeux (games) category of the Trophees Du Libre 2003. [http://vegastrike.sourceforge.net/index.php?prevnext=10 Link]

=Installation=
{|
|valign=top|Your guides on how to install, configure and start playing Vega Strike.
If you're new to Vegastrike you can also follow the [[Manual:New users|New users]] guide.

* [[Manual:Install|Installation of Vegastrike]]
* [[Manual:Running Vegastrike|Running Vegastrike]]
* [[Manual:Save and load|Saving and loading]]
* [[Manual:Config|Configure Vegastrike (Setup)]]
** [[Manual:Config:Advanced|Advanced configuration (edit the config file)]]
*** [[Manual:Config:Advanced:Bindings|Bindings]]
**** [[Manual:Config:Advanced:Bindings:Keyboard|Keyboard bindings]]
**** [[Manual:Config:Advanced:Bindings:Mouse|Mouse bindings]]
**** [[Manual:Config:Advanced:Bindings:Joystick|Joystick bindings]]
*** [[Manual:Config:Advanced:Variables|Variables]]

|valign=top|
{||
|<center>http://vegastrike.sourceforge.net/gallery/main.php?g2_view=core.DownloadItem&g2_itemId=5814&g2_serialNumber=2&ext=.png</center>
|<center>http://vegastrike.sourceforge.net/gallery/main.php?g2_view=core.DownloadItem&g2_itemId=5881&g2_serialNumber=2&ext=.png</center>
|-
|
|<center>http://vegastrike.sourceforge.net/albums/wiki_manual/config_code.png</center>
|}
|}

=Tutorial=
* [[Manual:New users|New users]] - Tips and tricks for new users.
* [[Manual:Tutorial|Tutorial]] - Starting a new game - making a few credits.
* [[Manual:Gameplay Tactics|Gameplay Tactics]] - Advanced game tactics.

=Play=
How to Interact with Vega Strike.
{|
|valign=top width=33%| 
==Interface==
http://vegastrike.sourceforge.net/gallery2/main.php?g2_view=core.DownloadItem&g2_itemId=6619&g2_serialNumber=2&ext=.png

*Directory
** [[Manual:Location|Locations]]
** [[Manual:Computer|Computers]]
* [[Manual:Location:Hangar|Hangar]] - Yes, that's your ship.
* [[Manual:Location:Concourse|Concourse]] - Access All Areas.
** [[Manual:Computer:Mission computer|Mission Computer]] - Your location access point.
*** [[Manual:Computer:Missions screen|Missions Screen]] - Have we got the mission for you!
*** [[Manual:Computer:News screen|News Screen]] - what's up?
*** [[Manual:Computer:Info screen|Pilot Information Screen]] - its all about you isn't it?
*** [[Manual:Computer:Game menu|Game Menu]] - Game file interaction.
* [[Manual:Location:Bar|The Bar]] - Come on in, have a drink!
* [[Manual:Location:Transit| Transit System]] - Going somewhere?
* [[Manual:Location:Cargobay|The Cargobay]] - where to go to buy or sell.
** [[Manual:Computer:Cargo computer|Cargo Computer]] - And how to do so.
* [[Manual:Location:Shipyards|Shipyards]] - Your one stop killer ship shop.
** [[Manual:Computer:Upgrades screen|Upgrades Screen]] - How do I obtain new upgrades?
** [[Manual:Computer:Ships screen|Ships Screen]] - How do I obtain new ships?
|valign=top|

==Inflight==
{|
|valign=top|
===Flying & Navigation===
http://vegastrike.sourceforge.net/gallery2/main.php?g2_view=core.DownloadItem&g2_itemId=5444&g2_serialNumber=2&ext=.png
* [[Manual:Basic flight|Basic flight]] techniques.
* [[Manual:Advanced flight|Advanced flight]] techniques.
** [[Manual:Match velocity|Match velocity]] with a [[Manual:Targeting|target]].
** [[Manual:Docking|Docking]] to a planet or a [[Vessels & Installations|capship]].
** [[Manual:Insystem travel|Insystem travel]]
** [[Manual:Interstellar travel|Interstellar travel]] (Jump drive).
* [[Manual:Targeting|Targeting]] - How to use targeting.
* [[Manual:Views|Views]] - Cockpit and camera views - what are they and how do they work.
* [[Manual:HUD|HUD]] - Explanation of the HUD layout.
* [[Manual:Map|Map]] - How the ingame map system works.
** [[Manual:Statistical Mode|Statistical Mode]] - What do all these numbers mean?
** [[Manual:Map Mode|Map Mode]] - Exploring the Universe.
** [[Manual:Navigation Computer|Navigation Computer]] - Using the Navigation computer.

===Communication===
http://vegastrike.sourceforge.net/gallery2/main.php?g2_view=core.DownloadItem&g2_itemId=6617&g2_serialNumber=2&ext=.png
* [[Manual:Communication|Communication]] - How to communicate with other [[Vessels & Installations|ships/stations]].
* [[Manual:Wingmen|Wingmen]] - Communicating / using Wingmen
|valign=top|

===Combat===
http://vegastrike.sourceforge.net/gallery2/main.php?g2_view=core.DownloadItem&g2_itemId=5079&g2_serialNumber=2&ext=.png
* [[Manual:Combat|Combat]] - How to fight your enemies.
** [[Manual:Combat:Guns|Guns]] - What are they and how do they work.
** [[Manual:Combat:Missiles|Missiles]] - When you need that extra firepower.
** [[Manual:Combat:Target tracking|Target tracking]] - What is ITTS and how is it used.
** [[Manual:Combat:Counter measures|Counter measures]] - ECM stops those missiles - dead!
** [[Manual:Combat:Cloaking|Cloaking]] - What is the device, and how to use it.
** [[Manual:Combat:Turrets|Turrets]] - Pilot turrets.
** [[Manual:Combat:Death|Death]] is not forever!
** [[Manual:Combat:Wingmen|Ordering wingmen]] - In space you are not alone!
** [[Manual:Combat:Tractor beam|Tractor beam]] - Grabbing the booty!

===and more===
* [[Manual:Tractor beam|Tractor beam]] - What is it and how to use it.
* [[Manual:Gameplay functions|Gameplay functions]] - Miscellaneous gameplay commands.
* [[Manual:Dynamic Universe|Dynamic Universe]] - How the universe works.
|}
|}

=Appendix=
* [[Manual:Keyboard layout|Keyboard Layout]] - The default keyboard layout reference for Vega Strike.
* [[Manual:Music|Using Your Own Music]] - How to use your own music files in Vegastrike.
* [[FAQ]] - Vegastrike FAQs
* [[Manual:Cheats|Cheats]] - Cheating the game - Note: contains spoilers.

==Database==
For information about species/factions/ships/terms please refer to the online [[Database]]
{{Database_Overview}}

==Printable version of the manual==

There is a v 0.4.3 PDF version of the information on this site (with some additional info too) available for download by clicking on the link below (current size 1.3 MB): 
CVS (depricated) [http://cvs.sourceforge.net/viewcvs.py/*checkout*/vegastrike/data4.x/documentation/Vega_Strike_Players_Guide.pdf Vega Strike Player's Guide (PDF)]

SVN [http://svn.sourceforge.net/viewcvs.cgi/*checkout*/vegastrike/trunk/data4.x/documentation/Vega_Strike_Players_Guide.pdf Vega Strike Player's Guide (PDF)]

==Links==
* The [http://vegastrike.sourceforge.net/manual/00_fullmanual/index.html original (but outdated) manual] (pure HTML)
* The [http://vegastrike.sourceforge.net/phpwiki/index.php/VegastrikeManual manual in the old wiki] (phpWiki)
* If you read this manual ''offline'', you can find the most recent version ''online'' at [http://vegastrike.sourceforge.net/wiki/Manual http://vegastrike.sourceforge.net/wiki/Manual]
* See also the [[Links]] page of the Vegastrike Wiki.

=Manual notes=
As you read through this manual, you will note references to various keys. These key references appear as: {{Key:EN:W}} refering to the w key; {{Key:EN:Shift left}} + {{Key:EN:W}} refering to the capitalized letter W. {{Key:EN:Ctrl}} + {{Key:EN:W}} refers to pressing both the Control and w key simultaneously.

References to '''[KP]''' refer to using the buttons on the '''KeyPad'''. Buttons appearing onscreen are noted in a similar fashion.

If there are no key graphics available (yet ;) ) the keys will be represented by something like this: '''[Shift]'''+'''[W]'''

----

{{NAV_Manual | previous=[[Vegastrike]]
| up=[[Vegastrike]]
| next=[[Vegastrike:License|License]]
}}

[[Category:Manual]]

Development:Network:Deathmatch/2006 Archive

2008-02-13T04:20:56Z

Nachtwolf: Development:Network:Deathmatch moved to Development:Network:Deathmatch/2006 Archive

Please write down any issues here... try to add to previously reported bugs rather than listing the same bug twice. Use four tilde (~) characters in a row to sign your name after your bug report

==Current Bugs:==
* lag when another player joins [[User:hellcatv|hellcatv]] 19:25, 22 August 2006 (PDT)
** also when someone respawns
* Spec is always allowed [[User:hellcatv|hellcatv]] 19:26, 22 August 2006 (PDT)
** Doesn't drain energy
* in mission files, client is allowed to spawn stuff, which is then "braindead" [[User:spiritplumber|spiritplumber]] 18:29, 30 August 2006 (PDT)
**Especially when server.py is present and client executes a server.server() because it's considered one of player[0]'s active missions
* Accidental disconnect(cable yank) leaves a ghost -- add a heartbeat/deadman switch? [[User:spiritplumber|spiritplumber]] 18:29, 30 August 2006 (PDT)
**should be fixed--needs testing--default 3 min timeout [[User:hellcatv|hellcatv]] 03:52, 2 September 2006 (PDT)
*Login problem with the main acount server with the curent svn releas [[User:www2|www2]] 16:03 PM Seprember 11 2006 (UCT)

==Old Bugs:==
* no way to specify server config file
**Now there is... and also a way to specify a port with -p
* Server completely ignores python blocks in missions [[User:spiritplumber|spiritplumber]] 18:29, 30 August 2006 (PDT)
**Fixed server now loads server.server()
* ship-firing weapons end up not being fired
** must be a type of weapon that fires with enter, like mountsize="heavy-capship-missile" instead of "capship-heavy" [[User:hellcatv|hellcatv]] 02:07, 2 September 2006 (PDT)
* Extra shots fired --[[User:eddit|eddit]] 06:36, 25 August 2006 (PDT)
** When you fire once, sometimes get extra shots fired
***We should ignore server instructions to START firing if the weapon was preemptively fired (as a lag reduction measure)... [[User:hellcatv|hellcatv]] 15:57, 31 August 2006 (PDT)
** Happens with missiles as well
*** Only bolt style missiles
** Currently I'm using a pacifier
* Missile remaining counts incorrect --[[User:eddit|eddit]] 06:43, 25 August 2006 (PDT)
** When you launch missiles, the number of missiles remaining sometimes jump up after a shot!
***server thinks you fired a different number---being updated for the fast missiles is going to have to be a solution (either that or laggy shots) [[User:hellcatv|hellcatv]] 15:57, 31 August 2006 (PDT)
****Fixed [[User:hellcatv|hellcatv]] 01:32, 2 September 2006 (PDT)
** Currently I'm using a pacifier
* no damage from ship-ship collisions [[User:dandandaman|dandandaman]] 04:16, 24 August 2006 (PDT)
** rebound happens, but no damage (hull, shield or armour) results
** This is because rebound happens on the client before the server gets wind of the collision---have some ideas but they'll have to wait--- collision damage is lame anyway in multiplayer [[User:hellcatv|hellcatv]] 01:16, 2 September 2006 (PDT)
*Missiles don't always fire, and sometimes launcher with 0 is selected
**cycling through missile types seems to resolve it---clearly something to do with active mounts
**I think it's fixed [[User:hellcatv|hellcatv]] 00:20, 24 August 2006 (PDT)
**Still seems to be a problem --[[User:eddit|eddit]] 06:48, 25 August 2006 (PDT)
**Ugh...not sure why :-( the cycle fix should have done it...Can you desccribe an easy way to repro it now ...I sometimes get it too... [[User:hellcatv|hellcatv]] 15:59, 31 August 2006 (PDT)
***Can't reproduce the problem... which ship and loadout---and what were the missile counts when it fails--and are you sure the server is actually keeping the lock? i.e. was the target stationary... maybe on server side the target fell out of your cone
****Ok I got it for sure this time :-) Turns out that firing guns toggled the missile lock time--I never found this while testing missiles alone except when I printed out the locktimes over and over [[User:hellcatv|hellcatv]] 01:16, 2 September 2006 (PDT)
* Problems withe the chat system --[[User:www2|www2]] 11:36, 27 August 2006 (UTC)
** When your press the chat key than disable all filght controll.
***not gonna change (at least until new keyboard interface system)
*hundreds of CMD_TARGET(0) requests presumably from dead or nontargetting players
**Fixed [[User:hellcatv|hellcatv]] 22:45, 23 August 2006 (PDT)
*when respawning can be locked into talk mode
**Fixed [[User:hellcatv|hellcatv]] 01:19, 24 August 2006 (PDT)
*esc should quit talk mode
**Fixed [[User:hellcatv|hellcatv]] 01:19, 24 August 2006 (PDT)
*should zoom in when respawned
**Fixed [[User:hellcatv|hellcatv]] 01:19, 24 August 2006 (PDT)
*Torps shouldn't last as long
**fixed...if they have lost their target they expire in 30 seconds (config var) [[User:hellcatv|hellcatv]] 00:58, 24 August 2006 (PDT)
*Ejects are irksome...they should either...expire... or ... never be created
**Fixed (physics, eject_live_time in config) so that eject seats expire after a while [[User:hellcatv|hellcatv]] 00:32, 24 August 2006 (PDT)

Development:Network:Deathmatch

2008-02-13T04:20:56Z

Nachtwolf: Development:Network:Deathmatch moved to Development:Network:Deathmatch/2006 Archive: All of these are old bugs that are now fixed.

#redirect [[Development:Network:Deathmatch/2006 Archive]]

FAQ:Installing

2007-12-01T02:52:09Z

Nachtwolf: added info about vc8

{{Languages|En|FAQ:Installing}}
{{NAV_Manual |
| previous=[[FAQ:Playing]]
| up=[[FAQ]]
| next=[[FAQ:Bugs]]
}}
----
Installing and Compiling Vegastrike. See also [[HowTos#Installing]]

== What are the minimum system requirements for Vegastrike? ==

A:Your computer needs to have OpenGL support (which most do nowadays).
* Minimum Requirement
** Processor: Pentium I 200Mhz or Apple G3 400Mhz
** Video card: 3d card with 16Mb of memory (although it will work without a 3d card too)
** Screen color depth: 16bit
** RAM: 512 Mb ''(I use 256 Mb in WinXP without any troubles - smbarbour / same to me in Linux Ubuntu - federoy)''
** Swap space: ???
** HD: ???
* Recommended Requirement
** Processor: ???
** Video card: ???
** Screen color depth: ???
** RAM: ???
** Swap space: ???
** HD: ???

If your graphics card is poor, put it on low/retro detail and low resolution/16bit color, fullscreen. 
More info about video cards is here: [[#Which_video_cards_are_known_to_work_.28or_not_to.29_with_Vegastrike.3F|Q7]]

== I get a message "The application failed to run because of an incorrect configuration, reinstalling may fix this problem" ==
http://vegastrike.sourceforge.net/forums/download.php?id=1546&ext=.gif

This means you have not installed the VC8 re-distributable package.

Look for an executable called "vcredist_x86.exe" in the bin folder and install it as Administrator.

If you do not have that program, download and install it from Microsoft [http://www.microsoft.com/downloads/details.aspx?familyid=32bc1bee-a3f9-4c13-9c99-220b62a191ee&displaylang=en here].

== Does the source code work with VC++ 6.0 or 7.0? ==

A: Most certainly.
VC++ 6.0/7.0 is unfortunately the only way I know how to compile it in windows. 
''Not completly true, it works with cygwin too. See [[HowTo:Cygwin Compiling]].''

Download '''vega-proj''' (vc++ 6) or '''vega-vc7''' (vc++ 7), '''''not''''' the outdated ''vega-new-proj'' and have at it (from CVS).

See [[HowTo:VCPP Compiling]] for more information.

Note for people with an old project (such as ''vega-new-proj''):

It's a bit of a trick to get all the .lib files into the project because a lot of the people who are in charge of maintaining the project somehow got rid if the library include directories from the project since I committed it. However, it's pretty easy to add those paths.

You have to add a few simple .cpp files to the project so give it a shot if you will.

The simplest way is to checkout '''vega-proj''' as it says in [[HowTo:Checkout CVS]].

== How do I turn fullscreen on or off in Vegastrike? ==
A: Edit vegastrike.config or <code>/.vegastrike/vegastrike.config</code>
and change fullscreen to false/true wherever it occurs.

A: Run Launcher.exe program, select OPTIONS, and adjust color.

Section of the vegastrike.config file that sets the screen mode: 
<code>#cat Color full_32 full_16 win_32 win_16</code>

To set windowed mode use: 
<code>#set Color win_32</code> 
or 
<code>#set Color win_16</code>

To set fullscreen mode use: 
<code>#set Color full_32</code> 
or 
<code>#set Color full_16</code>

== While compiling VS from CVS i got lots of error like seen in [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=848 this] thread in the forum. (e.g ''pasting "operator" and "+" does not give a valid preprocessing token'') and they are all in somewhere like the <code>../src/boost129/</code> directory. What should i do? ==
A: Try to run <code>./configure</code> with the <code>--enable-boost-128</code> parameter. 
See also:
* [[HowTo:Compile From CVS]]
* [[HowTo:Cygwin Compiling]].

== When compiling VS I get a <code>glXGetProcAddress</code> or <code>glXGetProcAddressARB</code> error. ==

A:
* Preferred way: Inserting the following lines into the file <code>gl_init.cpp</code> (Forum [http://vegastrike.sourceforge.net/forums/viewtopic.php?p=14032#14032 Link])
<pre>
#define GLX_GLXEXT_PROTOTYPES
#include <GL/glx.h>
</pre>
* A second way is to replace <code>glXGetProcAddress</code> with <code>glXGetProcAddressARB</code> or the other way around.
* If none of the other ways worked, include the line
<pre>
#define glXGetProcAddress glXGetProcAddressARB
</pre>
or
<pre>
#define glXGetProcAddressARB glXGetProcAddress
</pre>
at the top of the file <code>gl_init.cpp</code> (the very first line)

* See also the forum entries below:
** http://vegastrike.sourceforge.net/forums/viewtopic.php?t=966
** http://vegastrike.sourceforge.net/forums/viewtopic.php?t=1085
** http://vegastrike.sourceforge.net/forums/viewtopic.php?t=1153
** http://vegastrike.sourceforge.net/forums/viewtopic.php?p=14032#14032

== When compiling VS I get a <code>./depcomp: No such file or directory</code> error. ==

A: You need to start <code>automake</code> with the parameter <code>--add-missing</code> like this:
<pre>
automake --add-missing
</pre>

== Which video cards are known to work (or not to) with Vegastrike? ==
A: Any ATI Radeon or NVidia GeForce GPU should be fine. Other cards with OpenGL drivers and at least 16MB VRAM may also work. If your card is old, slow, or low on VRAM you will probably need to turn down the level of detail, resolution, and color depth.

This question is also discussed in the following thread in the forum: http://vegastrike.sourceforge.net/forums/viewtopic.php?t=1399

=== Working ===
{|
|'''Vendor'''
|'''Card Info'''
|'''Operation System'''
|'''Additional Info'''
|-
|ATI
|Rage 128 Pro
|
|not 8MB version
|-
|ATI
|Radeon 7000 Mobility
|OSX
|(iBook G3)
|-
|ATI
|Radeon 7200
|Linux
|
|-
|ATI
|Radeon 7500
|Linux
|[http://vegastrike.sourceforge.net/forums/viewtopic.php?p=28072#28072 Forum-Link]
|-
|ATI
|Radeon 7500
|WinXP
|[http://vegastrike.sourceforge.net/forums/viewtopic.php?p=28072#28072 Forum-Link]
|-
|ATI
|Radeon 8500
|Linux
|
|-
|ATI
|Radeon 9000 Pro
|Win98SE
|[http://vegastrike.sourceforge.net/forums/viewtopic.php?p=16354#16354 Forum-Link]
|-
|ATI
|Radeon 9200
|Linux DRI XF4.3
|Use the 16bit depth, not 24!!
|-
|ATI
|Radeon 9200
|Linux Kubutu "Breezy Badger"
|XOrg driver, 1024x768 24bit, run "xhost +local:" before launching VS from console
|-
|ATI
|Radeon 9500 Pro
|Linux
|
|-
|ATI
|Radeon 9600 Mobility
|OSX
|(PowerBook G4)
|-
|ATI
|Radeon 9600 Pro
|Win2k
|
|-
|ATI
|Radeon 9700 Pro
|Linux/Win2k
|
|-
|ATI
|Radeon 9800 Pro
|OSX
|(G4 867Mhz OSX 10.2.8)
|-
|ATI
|Radeon IGP 345M
|WinXP
|
|-
|ATI
|Radeon X1600 Mobility
|OS X
|(MacBook Pro)
|-
|NVidia
|GeForce 2 GTS 32MB
|Linux/Windows
|[http://vegastrike.sourceforge.net/forums/viewtopic.php?p=16374#16374 Forum-Link]
|-
|NVidia
|GeForce 2 MX
|Linux/Windows
|
|-
|NVidia
|GeForce 2 MX
|OSX
|(PowerMac G4 800)
|-
|NVidia
|GeForce 3 (standard)
|Linux/Windows
|
|-
|NVidia
|GeForce 3 Ti200 128MB
|WinXP
|
|-
|NVidia
|GeForce 3 Ti500 64MB
|
|
|-
|NVidia
|GeForce 4 MX440 64MB
|WinME
|
|-
|NVidia
|GeForce 4 MX460 64MB
|Win2k/WinXP
|
|-
|NVidia
|GeForce 4 MX (integrated)
|WinXP
|[http://vegastrike.sourceforge.net/forums/viewtopic.php?p=28907#28907 Forum-Link]
|-
|NVidia
|GeForce 4 Ti series
|
|
|-
|NVidia
|GeForce 4 Ti 4600 128MB
|Linux
|[http://vegastrike.sourceforge.net/forums/viewtopic.php?p=29718#29718 Forum-Link]
|-
|NVidia
|GeForce FX 5600
|
|
|-
|NVidia
|GeForce FX 5900
|
|
|-
|NVidia
|TNT2 M64 32MB
|
|
|-
|3DFX
|Voodoo3 16MB
|Linux/Win2k
|
|-
|3DFX
|Voodoo5000 64MB
|Linux
|
|-
|3DLabs
|Permedia 2 FireGL 1000 Pro
|
|
|-
|Elsa
|Erazor III Pro
|Linux(Debian)/Win2k
|
|-
|Matrox
|Millenium G400
|Win2k
|[http://vegastrike.sourceforge.net/forums/viewtopic.php?p=15059#15059 Forum-Link]
|-
|Matrox
|G440 DualHead MAX 32MB
|Linux Mandrake 10.1 Community
|[http://vegastrike.sourceforge.net/forums/viewtopic.php?p=29041#29041 Forum-Link]
|-
|Matrox
|Millenium G550
|Linux(Debian)
|[http://vegastrike.sourceforge.net/forums/viewtopic.php?p=59892#59892 Forum-Link]
|-
|S3
|Savage/IX-MV
|Linux (Gentoo)
|[http://vegastrike.sourceforge.net/forums/viewtopic.php?p=33531#33531 Forum-Link]
|-
|SiS
|630 16MB shared memory
|WinXP
|(But no cursor at the bases and some minor graphical issues)
|-
|}

=== Not Working ===

{|
|'''Vendor'''
|'''Card Info'''
|'''Operation System'''
|'''Additional Info'''
|-
|ATI
|Rage 128 8MB
|OSX
|(iMac G3 et al)
|-
|3DFX
|Voodoo 4500
|Win98SE
|
|-
|Hercules
|Kyro II 64MB
|
|
|-
|Matrox
|G400
|Win98
|[http://vegastrike.sourceforge.net/forums/viewtopic.php?p=13183#13183 Forum-Link]
|-
|Matrox
|G450 32MB
|Linux
|
|-
|}

== I'm getting similar errors as shown below when trying to compile today's cvs version, What about that? ==

<pre>
if g++ -DHAVE_CONFIG_H -I. -I. -I../.. -DHAVE_SDL=1 -DSDL_WINDOWING=1 -DHAVE_AL=1 -DUSE_STENCIL_BUFFER=1
-DDATA_DIR=\"/usr/share/games/vegastrike/data\" -I/usr/include/python2.3 -DHAVE_PYTHON=1 -DUSE_BOOST_128=1
-I../../src/boost -I../../src -pipe -falign-loops=2 -falign-jumps=2 -falign-functions=2 -I/usr/include/SDL
-D_REENTRANT -pthread -pipe -MT gl_globals.o -MD -MP -MF ".deps/gl_globals.Tpo" -c -o gl_globals.o gl_globals.cpp; \
then mv -f ".deps/gl_globals.Tpo" ".deps/gl_globals.Po"; else rm -f ".deps/gl_globals.Tpo"; exit 1; fi
In file included from gl_globals.cpp:22:
gl_globals.h:123: error: syntax error before `;' token
gl_globals.h:124: error: syntax error before `;' token
gl_globals.h:125: error: syntax error before `;' token
gl_globals.h:126: error: syntax error before `;' token
gl_globals.h:127: error: syntax error before `;' token
gl_globals.h:128: error: syntax error before `;' token
make[4]: *** [gl_globals.o] Error 1
make[4]: Leaving directory `/usr/src/vegastrike-20040724/vegastrike/src/gldrv'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/usr/src/vegastrike-20040724/vegastrike/src'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/usr/src/vegastrike-20040724/vegastrike'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/usr/src/vegastrike-20040724/vegastrike'
</pre>
A:
* You need the latest version of glext.h to fix the error.
* Get it at http://oss.sgi.com/projects/ogl-sample/ABI/glext.h
* Then you probably need to save it in <code>/usr/include/GL/glext.h</code> as root (Make a backup first).
* If there is no <code>glext.h</code> in <code>/usr/include/GL</code> then do a search for it...
<pre>
find /usr -name glext.h
</pre>
* After that, gcc will probably have to rebuild most of the vega strike files again because that file changed.
* See also [http://vegastrike.sourceforge.net/forums/viewtopic.php?p=22473#22473 this] post in the forum.

== After installing with the Linux Binary installer, I get an error about libstdc++-libc6.2-2.so.3 ==
A: This library is a 'compatibility' library used by many precompiled applications, including Vegastrike. It is available, for Fedora Core 3, from the package compat-libstdc++. Other distributions may be similar.

Debian: See if you have /usr/lib/libstdc++.so.6. If not, install package called "libstdc++6" which should give you that lib. Then you need to do a symlink for it to work:
"ln -s /usr/lib/libstdc++.so.6 /usr/lib/libstdc++-libc6.2-2.so.3".

Once this is installed, both Vegastrike and the setup application should work.
----
{{NAV_Manual |
| previous=[[FAQ:Playing]]
| up=[[FAQ]]
| next=[[FAQ:Bugs]]
}}
[[Category:FAQ]]

Talk:Vegastrike

2007-10-15T00:25:47Z

Nachtwolf: /* Skin usage */ fixed

= Talk =
* [[User:pontiac|pontiac]] 07:46, 12 Mar 2005 (PST) another thing that isn't really a big issue:
** When i turn off the diplay of images (firefox here) i do no tget the article/discussion/edit+ watch/etc... links on the top of the page. But they are texts, so the ''should'' show up, no?
** I think this is since the wiki has been integrated/embedded into the vegastrike design, but i'm not sure.
** With turned off images i also get wrong links in the main menu on the left (because the 'nonexisting image' overlaps the other links)

=Wiki logo discussion=
* [[User:pontiac|pontiac]] 07:46, 12 Mar 2005 (PST) Just two small suggestions for the Wiki main page (if possible):
** The community portal link should also be changed to something else.
*** Maybe like this: [http://vegastrike.sourceforge.net/forums/ Community Forum]
**** in the code below this link is removed completly ;)
*** If that isnt' possible at least point ot the place [[VsWiki:Community Portal]] or so.
** Is it possible to change the "Main Page" to point to [[Vegastrike]] (but leave the "Main Page" caption)?
** Remove the wikipedia log (Flower with brackets) ... IMHO it isn't really needed, is it?
*** [[User:Silverain|Silverain]] 15:25, 11 May 2005 (PDT) Pontiac, did you ever figure out how to do this? It is so irritating and unnecessary.
**** [[User:pontiac|Pontiac]] 02:17, 12 May 2005 (PDT) Just found this: [http://meta.wikimedia.org/wiki/Customization#How_do_I_customize_the_logo_in_the_top_left_corner.3F Wikimedia -> Customization#How do I customize the logo in the top left_corner?] The rest of the [http://meta.wikimedia.org/wiki/Customization Customization page] is pretty informative as well.

[[User:pontiac|Pontiac]] 04:49, 12 May 2005 (PDT) Here are the changes i did to the wiki files:
<pre>
###############################################################################
# edit ./LocalSettings.php

$wgLogo = "{$wgUploadPath}/wiki.png";

$wgNavigationLinks = array (
array( 'text'=>'mainpage', 'href'=>'mainpage2' ),
array( 'text'=>'recentchanges', 'href'=>'recentchanges-url' ),
array( 'text'=>'randompage', 'href'=>'randompage-url' ),
array( 'text'=>'help', 'href'=>'helppage' ),
array( 'text'=>'sitesupport', 'href'=>'sitesupport-url' ),
);

###############################################################################
# edit ./languages/Language.php

'mainpage' => 'Main Page',
'mainpage2' => 'Vegastrike',

###############################################################################
# edit ./skins/monobook/main.css

/*#column-one { padding-top: 160px; }*/
/*edited by ponitac 2005 05 12*/
#column-one { padding-top: 10px; }

/* edited by by pontiac 2005 05 12 */
/*
#p-logo {
z-index: 10;
position:absolute;
top: 0px;
left: 0px;
height: 0px;
width: 0em;
overflow: visible;
}

#p-logo h5 { display: none; }
#p-logo a,
#p-logo a:hover {
display: block;
height: 1px;
width: 1em;
background-repeat: no-repeat;
background-position: 35% 50% !important;
text-decoration: none;
}
*/

</pre>

= Login discussion =
* Pontiac, what was resolved about logins to edit the wiki? I know its connected to the forum logins, but we can still edit the wiki without logging in (and we show up as an IP address). Can we bloke non-logged in editing somehow? It makes it difficult to tell who's done what if someone forgets to login. [[User:Silverain|Silverain]] 15:57, 12 Apr 2005 (PDT)
** [[User:jackS|jackS]] 23:18, 12 Apr 2005 (PDT) Agreed. if we can do anything to force logins, that would be a very good thing.
** [[User:pontiac|Pontiac]] 11:50, 17 Apr 2005 (PDT) Actually i don't know what's the current setting for wiki login since i'm not really involved with the configuration. I'm normally not for a restricted access to wikis. But as you two already mentioned, the 'keeping track of things' is not really possible with IPs everywhere, so i triple this idea... especially since there is still the possibility for everyone to edit the wiki.
** Odd, I had thought you had set up the configuration... so should mention it to [[User:ace123|ace123]] instead? Calling [[User:ace123|ace123]]... [[User:Silverain|Silverain]] 15:45, 17 Apr 2005 (PDT)
*** OK, I badgered and annoyed [[User:ace123|ace123]] and you may have noticed that if you try to edit without being logged on, it comes up with a reminder and takes you to the login screen - Big thanks [[User:ace123|ace123]]. [[User:Silverain|Silverain]] 22:48, 17 Apr 2005 (PDT)
* With SourceForge's move to MySQL 4, we decided to upgrade the Media Wiki to 1.5.0, which was released not long ago. The login system should work hopefully.. [[User:Ace123|Ace123]] 17:25, 14 Oct 2005 (PDT)

= Vegastrike (name) discussion =
* [[User:pontiac|pontiac]] 10:39, 15 Mar 2005 (PST) Another thing that needs to be discussed and straightend out is the title of the game itself.
** Should it be:
*** "Vegastrike" (Sourceforge/Mission)
*** "VegaStrike" (Logo?)
*** "Vega Strike" (Logo)
*** [[User:Silverain|Silverain]] 15:26, 22 Mar 2005 (PST) I have been using Vega Strike taken from the current logo, forum title etc. Maybe we should poll this in the forums?
**** [[User:pontiac|Pontiac]] 10:54, 8 May 2005 (PDT) That's a good idea, but at first a statement from the devs would be good to see how it was intended in the beginning.

* Finding the pages containing the different names
** [http://vegastrike.sourceforge.net/wiki/Special:Search?search=Vega+Strike&fulltext=Search Search for "Vega Strike" in the wiki]
** [http://vegastrike.sourceforge.net/wiki/Special:Search?search=Vegastrike&fulltext=Search Search for "Vegastrike" in the wiki]

'''After discussing this issue the conclusion should be added to the [[VsWiki:Manual of Style|Manual of Style]]'''

== Navigation-Mainpage target ==

Hi, the "Main Page" of the navigation (left hand of the wiki) directes to '''Main Page''' which is a simple redirect to [[Vegastrike]]. Is it possible to change the link to '''Vega Strike''' directly? Any redirect at the navigation looks ''strange''. The '''Community portal''' looks quite empty. Is '''Help''' intended to be some general help about the wiki or about the game? It is also empty. Greetings: [[User:Makarius|Makarius]] 06:35, 7 November 2006 (PST)

== Skin usage ==

Hi, I've some problems reading the links within the articles, because they are dark blue and the background is black. What skins are you using? I tried all existing skins, but monobook is the only one where the normal font is not black. I'm using the Mozilla browser. Greetings: [[User:makarius|makarius]] 02:42, 10 October 2007 (PDT)
* It was just the main page which sets the background but not the font color... Should be fixed now. [[User:ace123|Patrick]] 17:25, 14 October 2007 (PDT)

Vegastrike

2007-10-15T00:22:57Z

Nachtwolf: fixed font color

{{Languages|En|Vegastrike}}
{{Wiki_Nav_Index}}

{| cellspacing="3" class="mainpagetable" align="center" style="background:#2A2A2A;color: rgb(216,216,255); border-style:solid;border-width:1px;padding:5px;width:100%;"
|- valign="top"
|colspan="2"|
<center>Welcome to the Vega Strike Wiki</center>

Welcome to the '''Vega Strike''' [[wikipedia:Wiki|Wiki]], a user-edited manual and development guide for users and developers of the [http://www.opensource.org/ open source] '''Vega Strike''' game. Feel free to edit or add any pages you feel are necessary, but please read the [[VsWiki:Manual of Style|Manual of Style]] first, and please only add data to the [[Database]] that originates from an authoritative source.
|- valign="top"
|style="background:#ffdead;" width="50%"|<center>'''[[Manual|User Manual]]'''</center>
|style="background:#dfefef;" width="50%"|<center>'''[[Development|Development]]'''</center>
|-
|valign="top" style="border-style:solid;border-width:1px;padding:5px;"|<center>Everything you wanted to know about Vega Strike (playing/story/etc)</center>
{|class="mainpagetable" style="background:#2A2A2A;"
|http://vegastrike.sourceforge.net/gallery/main.php?g2_view=core.DownloadItem&g2_itemId=5842&g2_serialNumber=2&ext=.png
|
* [[Manual]] - The complete game manual.
* [[Manual:New users|New users guide]]
* [[Story Elements]]
* [[FAQ]]s - Frequently asked questions
* [[OOG Tools|Out of Game Tools]] - map viewers, route finders, etc.
* [[Database]] - Info on the Vega Strike Universe
* [[MODs|Full list of MODs]] for Vega Strike
* MODs using this Wiki:
** [[MOD:WCU|Wing Commander Universe]]
** [[MOD:Elite Strike|Elite Strike]]
|}
|valign="top" style="border-style:solid;border-width:1px;padding:5px;"|<center>Feel free to help with the development of Vega Strike. The links below are a good starting point to do so.
</center>
* [[HowTo:Contribute|The Vega Strike Contributor's Guide]]
* [[Development]] - Development main page
* [[FAQ:Feature_Requests|Feature Requests]]
* [[FAQ]]s - Frequently asked questions
* [[Artstyle_guides|Model Art Style Guides]] - Style Information for VS model artists
* [[Development:Roadmap|Roadmap]] - Vega Strike development plan
* [[HowTos]] - Various Howtos (Installing/Playing/etc).
* [[HowTos#Sourcecode HowTos|Sourcecode HowTos]] - Getting and installing the latest unstable version.
* [http://vegastrike.sourceforge.net/forums/ Vega Strike Forums] - Especially the "Development" and modding forums.
* [[MODs]] - Help the people making their MODs
* [http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/ Browse the SVN repository]
* [http://sourceforge.net/tracker/?group_id=19507&atid=119507 Bug tracker]

|}

{| cellspacing="3" class="mainpagetable" align="center" style="background:#2A2A2A;border-style:solid;border-width:1px;padding:5px;width:100%;"
|- valign="top"
|colspan="2"|<center>'''The Vega Strike Community'''
If you want to help out with the wiki, or get help that this wiki cannot provide, check out the links below.
</center>
|-
|style="background:#2d7f2d;" width="50%"|<center>'''Helping with the Wiki'''</center>
|style="background:#3e3e4f;" width="50%"|<center>'''Getting Help'''</center>
|-
|valign="top" style="border-style:solid;border-width:1px;padding:5px;"|
* [[VsWiki:Manual of Style|Manual of Style]] - Please read it before editing, and please make any testing of the wiki system in the [[SandBox|Sandbox]].
*[[VsWiki:Village Pump|Village Pump]] - Make any discussions you wish about better organizing the wiki, or adding major new additions to the wiki.
* [[VsWiki:Requested Articles|Article Requests]] - Needed/wanted pages
* [[Wikipedia:How to edit a page|How to edit a wiki page]]
* [[:Category:Pages_needing_attention|Pages that need attention]]
* [[Special:Listusers|User list]] | [[Special:Popularpages|Most popular pages]]

* More special pages are here [[Special:Specialpages]]
|valign="top" style="border-style:solid;border-width:1px;padding:5px;"|<center>Do you need help? Then try the forums, the main source for development or help! Or you can leave the site by any one of a number of other links...
</center>
* [http://vegastrike.sourceforge.net/forums/ Vega Strike Forums]
* [[Links]]
* irc.freenode.net #vegastrike (Main chanel)
** irc://irc.freenode.net/#vegastrike
** irc://irc.freenode.net/vegastrike (link for mIRC user)
* irc.stealth.net #vegastrike (Backup chanel)
** irc://irc.stealth.net/#vegastrike
** irc://irc.stealth.net/vegastrike (link for mIRC user)
|}

{| cellspacing="3" class="mainpagetable" align="center" style="background:#2A2A2A;border-style:solid;border-width:1px;padding:5px;width:100%;"
|valign="top" |<center>'''Creating a wiki account'''
If you want to create an account in the wiki, you need to '''go to the [http://vegastrike.sourceforge.net/forums/ forum] and create an account there'''. This is because the logins are linked and creation is only possible there. Sorry if that causes any troubles ;)
</center>
|}

{{Moving_from_phpwiki}}

----
Please see [http://meta.wikipedia.org/wiki/MediaWiki_i18n documentation on customizing the interface]
and the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide] for usage and configuration help.

HowTo:MOD

2007-10-08T01:19:49Z

Nachtwolf: Updated mod information to be more current and to avoid confusion.

{{NAV_Manual |
| previous=[[HowTo:Add Warp Trails|Add Warp Trails]]
| up=[[HowTos]]
| next=[[HowTo:Make Weapons|Make Weapons]]
}}
----
''For a list of available mods, see [[MODs]]. For more general information on creating content for use with the Vega Strike engine, see [[HowTos]].''
----
=MOD support=
VegaStrike has automatic support for MODs.
You still have to specify
<tt>
./vegastrike -Mmodname.
</tt> (note that there is no space between -M and modname.

Mod support currently only works in Linux, however the source code has a Windows fix as of October 7 if someone compiles a EXE.

Workaround for Windows 0.5 Beta: Make an *empty directory* modname in the "mods" directory, and put still your modded content in ".vegastrike/mods" (which exists in the vegastrike data directory for Windows).

For windows, the easiest way to start it is to make a shortcut to the vegastrike.exe and add the "-Mmodname" into the Command Line in the shortcut properties.

The MOD must have a directory structure just like <tt>data4.x</tt> containing only files that were modified or added compared to VS data files, with a few exceptions:
* You want to put your own copy of vegastrike.config in the mod directory.
* To add your own units, you must modify the "UnitCSV" config option to contain "modunits.csv units.csv" or the other way around, depending on the loading priority.
** You must therefore call your "units.csv" instead "modunits.csv" (but still in the "units" folder).
* you just have to put the MOD directory structure in your LINUX: (~ = home) <tt>~/.vegastrike/mods/modname</tt> or in <tt>datadir/mods/modname</tt>.

No files must exist in the mod directory, but it is usually a good idea to have a vegastrike.config (and corresponding setup.config and Version.txt).

If you add Files existing Files of VS to the Modstructure, Vegastrike loads your modded files instead of the original Vegastrike Files.

VS <strike>will</strike>used to use all the found MOD files in a standard game (no -M option) but will start using the standard config file and weapon_list file.
When specifying <tt>-Mmodname</tt> on the command line, VS will start and load the MOD config file and <tt>weapon_list.xml</tt> file automatically. '''Doing things this way makes it hard to both enable and disable mods (think about the files it saves in the home directory which will keep getting loaded and possibly interfere with the real game or other mods), so I have disabled this to avoid confusion with two different mod systems.''' [[User:ace123|Patrick]] 18:19, 7 October 2007 (PDT)

NOTE: sectors should be in a sectors subdir ([[VegaTrek|Mods:Vega Trek]] has sectors in <tt>Sector01</tt>, but the right place is in <tt>sectors/Sector01</tt>).

==Sources==
[http://vegastrike.sourceforge.net/forums/viewtopic.php?p=11838#11838 Link]

[http://vegastrike.sourceforge.net/forums/viewtopic.php?p=88877#88877 Questions on mod filesystem layout]

=placing Starting Location=

The startlocation is saved as three floating points, and credits as another in a default savegame called "New_Game" in the <tt>datadir</tt> Folder (I recommend not in "save" [[User:ace123|Patrick]] 18:19, 7 October 2007 (PDT)).
Easist way to change the Starting location is to save a game and copy it into the name "New_Game"
== Sources ==
[http://vegastrike.sourceforge.net/forums/viewtopic.php?p=88864#88864 starting location of the game]
----
{{NAV_Manual |
| previous=[[HowTo:Add Warp Trails|Add Warp Trails]]
| up=[[HowTos]]
| next=[[HowTo:Make Weapons|Make Weapons]]
}}

[[Category:HowTos|MOD]]

HowTo:Checkout SVN

2007-10-06T04:06:46Z

Nachtwolf: removed references to the "music" module.

{{NAV_Manual |
| previous=[[HowTo:Edit News|Edit News]]
| up=[[HowTos]]
| next=[[HowTo:VCPP Compiling|Compiling with VCPP]]
}}
----
If you're interested in an experimental version of Vega Strike, then SVN is what you'll be looking at.

'''Executive summary'''

Subversion, or SVN, is a mechanism by which developers can keep track of changes to their code and distribute these changes to the public in real time. This allows people to take advantage of software as it is being developed, between official releases.

[[HowTo:Checkout_SVN#Windows_Clients|Windows users]] can use an [[HowTo:Checkout_SVN#Tortoise_SVN|SVN client]] to check out the data4.x module, which contains game data and windows binaries.

[[HowTo:Checkout_SVN#Linux_Clients|Linux]] and [[HowTo:Checkout_SVN#Mac_OS_X_Clients|Mac OS X]] users must use an SVN client to check out the vegastrike module as well, which contains source code for them to compile. (Note that compiling Vega Strike on Mac OS X is considered very difficult.)

=What is SVN?=
SVN stands for '''S'''ub'''v'''ersio'''n''', a system similar to CVS. It allows developers to simultaneously work on a centralised project - in this case, that's Vega Strike.

Downloading ("checking out") and compiling the SVN-version often gives you access to features not included in the latest stable release of the program. SVN-based versions can be unstable and may not even work at all, but may hold advantages compared to stable versions.

==Structure==
Unlike a CVS repository, the top level of an SVN repository contains more than just the trunk. Vega Strike's SVN repository follows the standard layout, so the SVN root looks like this:
* '''branches''' - Independent copies of some or all of the trunk code. A developer making major changes, such as the ogre branch or major code cleanup will usually make a branch so they can keep track of their progress without breaking the trunk code for everyone else. These changes eventually are merged back into the trunk.
* '''tags''' - Revisions which have been marked. For instance, a tag might be made for a stable release so that svn users can update to it via the ''svn sw'' command. The VS developers like to use tags to mark milestones in the code, such as before or after a major change, so you'll see a lot of tags.
* '''trunk''' - The main trunk code, as would be seen in the root of a CVS repository. This contains a number of modules filled with code and data.

==Modules==
Vega Strike's SVN repository holds several subdirectories, which can either be checked out separately or altogether. The most notable ones are included below.

* '''data4.x''' - data files of the game. This consists mainly of models, textures and backgrounds. Required to play the game.
* '''data5.x''' - Data for the [[Development:Ogre|Ogre port]]. Stick with data4.x unless you want to run the experimental Ogre branch.
* '''history''' - Old descriptions of factions and species.
* '''modtools''' - Tools to aid creation and modification of game files (campaigns and units)
* '''translations''' - Translations of Vega Strike data files into other languages.
* '''vega-proj''' - Deprecated Visual C++ 6 projects. (See [[HowTo:VCPP_Compiling#Visual_C.2B.2B_6.0_.28deprecated.29 here]])
* '''vega-vc7''' - Visual Studio 7 projects. (See [[HowTo:VCPP_Compiling#Visual_Studio_7.x here]]
* '''vega-vc8''' - Visual Studio Express 2005 projects. (See [[HowTo:VCPP_Compiling#Visual_C.2B.2B_8.0_.282005_Express.29 here]])
* '''vegastrike''' - the game base code.

The following modules are deprecated, have been removed from current revisions, and are listed for historical purposes only:
* '''data''' - deprecated 3.x and lower data files.
* '''charserver'''
* '''vega-new-proj''' - even older VC6 project - don't use.
* '''evilwm''', '''ethereal''', '''virtuanet''' - other projects with temporary repositories
* '''mission_select''' - Functionality also in Launcher, and also not used often.
* '''texturizer''' - If you can get it to compile, I believe it may still work.
* '''syseditor''' - If you like typing in coordinates of every planet by hand in an ugly console interface, go ahead.

The Subversion tree can be browsed via a web interface: http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/

'''→''' ''See also: [[Development:CVS Tree]]''

=Linux Clients=

==Command-line svn==

===Website===
http://subversion.tigris.org/

===Description===
The linux-command `svn' is the most basic Subversion client.

===Using svn for downloading vs-devel===
Checking out (downloading) the Vega Strike svn-modules is easy. The general syntax is
<pre>
svn co [repo]/trunk/[module] [target-directory]
</pre>

<pre>
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk vegastrike
</pre>
...will download the entire tree (all modules) into directory `vegastrike'. But '''don't do this'''! Such a command would download data for both the normal and ogre branches, plus Visual Studio projects for ALL supported versions and goodness knows what else.

You should really only download individual modules, and a similar syntax can be used. For example, to download the data4.x module,
<pre>
svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data4.x data4.x
</pre>
...will suffice. (Leaving off the target directory will make svn try check out into the ''working directory''.)
In order to get all the files required to compile the game, checkout the following modules:
* data4.x
* vegastrike

==Tutorial to download, setup and run the development version==
In order to run the development version of Vega Strike, the executables expect to find the data to be in certain places relative to them. This short tutorial deals with these specifics on Linux operating systems. (It also applies for Mac OS X users.)

So, let's start.
* Create a directory where you would like your copy of the Vega Strike development version to live in. For example purposes we will create a directory called ''VegaStrike'' in our user's home-directory.
<pre>~> mkdir VegaStrike</pre>
* Change into this newly created directory. In our case:
<pre>~> cd VegaStrike</pre>

===Initial downloading (check-out)===
Now we can start downloading the packages from the SVN repository. If you download them directly into your Vega Strike directory they will be just in the right place.

To save on download bandwidth, you can download a snapshot of the SVN tree, and then just update that to the current revision. One big compressed file will download much faster than having SVN get each file individually. Snapshots available here: http://vegastrike.sourceforge.net/forums/viewtopic.php?t=6749. Also here (not sure if this second one includes the .svn directories needed to update it with svn):
http://sourceforge.net/project/showfiles.php?group_id=181552&package_id=211092&release_id=463105.
If you run into any problems, it will work fine to follow the instruction below, using svn to do the whole checkout.

* Download (check-out) the source code package ''vegastrike'', and the content package ''data4.x'' package.
<pre>~/VegaStrike> svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
~/VegaStrike> svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data4.x</pre>
This leaves you with three new directories inside your Vega Strike directory called as the packages are.

''Note:'' If you are having problems with SVN due to connecting via a proxy, try to solve them using the method described here: http://subversion.tigris.org/faq.html#proxy

===Building===
{{FIXME}} This should merged with the [[HowTo:Compile_from_SVN]] page?

The [[HowTo:Compile_from_SVN]] page has a list of some options that you can pass to ./configure

*To build the engine, change into the source code directory ''vegastrike''.
<pre>~/VegaStrike> cd vegastrike</pre>
*Now start with setting up and configuring the build and finally building the engine.
<pre>~/VegaStrike/vegastrike> ./bootstrap-sh
~/VegaStrike/vegastrike> ./configure
~/VegaStrike/vegastrike> make vegastrike
~/VegaStrike/vegastrike> make soundserver</pre>
You will likely receive some error messages during any of these stages, especially during the configure part. If they tell you that your system is missing some development libraries, install them. How this is done depends strongly on your Linux distribution, but we will assist you in the [http://vegastrike.sourceforge.net/forums/viewforum.php?f=5 Compiling Problems forums]. You will be left with a file called "config.log" please attach that instead of copy-and-pasting thousands of lines of error messages. It's all in this file.

After you installed the missing libraries repeat the last (failed) step and continue.
Finally, there will be two executables called ''vegastrike'' and ''soundserver''.

'''Note:''' The configure script currently has a bug that can cause it to incorrectly report on the absence of GLUT. If you are sure you have installed glut-devel and are still seeing this error, check near the end of config.log to see if another library (such as libxmu or libxi) is the true culprit. [http://vegastrike.sourceforge.net/forums/viewtopic.php?t=7562]

===Building the Setup program===
* You will need a GTK-1.2 development package installed on your system. GTK-2.0 will ''not'' work. Usually, it will be called something like libgtk1.2-dev, gtk1.2-devel, or some similar name. Make sure you have both the main package and the devel package installed.
* Vssetup will be built along with vegastrike and all the tools, but only if you have the GTK-1.2 development package installed before running ./configure. If not, you must re-run ./configure and then '''make vssetup'''
* If compilation works, you will have a '''vssetup''' binary in the vegastrike directory (note that it will ''not'' be named '''setup''' as the directory tree may suggest.

===Setup===
To run Vega Strike, the built executables need all the configuration and data files to be in the right place relative to them. Currently, the executables (''vegstrike'' and ''soundserver'') reside in the source code directory. But they have to be run out of the ''data4.x'' directory. Therefore, we will create a link.
* Change in to the ''data4.x'' directory. (We are still in the source code directory ''vegastrike''.)
<pre>~/VegaStrike/vegastrike> cd ../data4.x</pre>
* Create symbolic links to the executables in the source code directory.
<pre>~/VegaStrike/data4.x> ln -s ../vegastrike/vegastrike
~/VegaStrike/data4.x> ln -s ../vegastrike/soundserver
~/VegaStrike/data4.x> ln -s ../vegastrike/vssetup</pre>
* After that, you must run "'''./vssetup'''" inside the '''data4.x''' folder, or any folder which has the correct '''setup.config''' and '''vegastrike.config'''.
If we had made copies or moved the files instead of symbolic linking, we would have to do the procedure of copying or moving every time we build the executables from source.

===Running and configuring===
* To run Vega Strike you have to start it from the ''data4.x'' directory.
<pre>~/VegaStrike/data4.x> ./vegastrike</pre>
* Optionally you can create a short cut to this application onto your desktop or in your start menu. Simply point it to the ''vegastrike'' executable in the ''data4.x'' directory.
* If you need to adjust screen resolutions, input devices and key-mappings, do so by editing the configuration file ''vegastrike.config''. The default configuration file resides in the ''data4.x'' directory. You can change that or you can make your own user specific version by first copying it into your ''.vegastrike'' (hidden directory) directory in your user's home directory.

===Known bugs and work-arounds===
This issue has been fixed in the latest SVN versions.

In case you are using an older version (i.e. pre-10700 or so) and Vegastrike does not run (gives a "Cannot open display :0.0" error), if are willing to sacrifice some security on multi-user systems, you may have to use this command to run vegastrike:
<pre>xhost +local:</pre>If you do not want to compromise security, update to the latest revision.

===Staying updated with the development version===
As development progresses the repository changes. In order to update your working copy you need to do the following.
* Change into the package's directory you want to update. In our example all the packages were stored in a directory called ''VegaStrike''. Let's assume we want to update the ''data4.x'' package.
<pre>~> cd VegaStrike
~/VegaStrike> cd data4.x</pre>
* Update from the SVN repository.
<pre>~/VegaStrike/data4.x> svn update</pre>
* Do this for every package you want to update. Exchange ''data4.x'' with ''vegastrike''.
* If something changed in the ''data4.x'' package, you don't need to recompile.
* If something changed in the source code package ''vegastrike''. You only need to repeat the building part of this tutorial and in case you did not create symbolic links the copying or moving procedure for the executables in the setup part of this tutorial. You should not need to type "make clean", however if you experience errors like "unresolved external symbol" it may remedy that error.

=Windows Clients=

Note: For windows, only the '''data4.x''' module is necessary to play the game. You will find the executable program inside the "bin" folder.

If you are interested in compiling the code, you will need the '''vegastrike''' module, as well as the appropriate vega-project module for your Visual C++ version. See [[HowTo:VCPP_Compiling]] for compiling info.

Some people have problems with the latest executable relating to Visual C++ 8. If you want an older version of the executable compiled with VC7, you can browse the repository here:
http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/trunk/data4.x/bin/vegastrike.exe?view=log

==Tortoise SVN==

===Website===
http://tortoisesvn.tigris.org/

===Description===
Just like TortoiseCVS, Tortoise SVN lets you work with files under SVN version control directly from Windows Explorer. It's freely available under the GPL.

With TortoiseSVN you can directly check out modules, update, commit and see differences by right clicking on files and folders within Explorer. You can see the state of a file with overlays on top of the normal icons within Explorer. It even works from within the file open dialog.

===Usage===
* Download and Install Tortoise SVN from http://tortoisesvn.tigris.org
* Create a new folder in Windows Manager where you will download your modules (called Sandbox, SVN or similar working location name);
* Within that folder, create another folder being the name of module you wish to checkout e.g. data4.x, vegastrike etc;
* Right click on the folder created and select SVN Checkout. This brings up the checkout configuration screen;
* Input the URL of the repository into the dialog box, for example data4.x will be;
<pre>
https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data4.x
</pre>
**You may also use the built-in repository browser to select the module you wish to check out.
* Click OK to begin checkout of the module.
[Edit - Turbo: The download is 600+ MB and will take some time. I did not have to install the program -- after downloading, run the Setup program in the BIN folder, then you can run VEGASTRIKE.EXE to play.]

=Mac OS X Clients=

==Command Line Client==

===Website===
http://metissian.com/projects/macosx/subversion/

(or http://pdb.finkproject.org/pdb/search.php?summary=svn for Fink packages.)

Footnote:
metissian.com does not maintain current binaries. A better source would be (ordered from most current to most convenient):

(a) http://subversion.tigris.org/ for current source code.

(b) use Fink or MacPorts to get (usually) current source code.

(c) http://www.codingmonkeys.de/mbo/ for a (usually) current install package.

(d) XCode3 includes svn as part of the default installation (But not XCode2).

==SCPlugin==

===Website===
http://scplugin.tigris.org/

===Description===
"The goal of the SCPlugin project is to integrate Subversion into the Mac OS X Finder. The inspiration for this project came from the TortoiseSVN project."

====Usage====
Must have command line client installed.

{{Fixme}}-WRITEME

*[http://www.joshbuhler.com/2005/07/05/setting-up-the-subversion-client-on-mac-os-x/ A good tutorial on setting up SVN for OSX]

==Other==
*[http://www.lachoseinteractive.net/en/community/subversion/svnx/features/ svnX]

==Building==
'''→''' ''See [[HowTo:Compile on OSX]]''

----
{{NAV_Manual |
| previous=[[HowTo:Edit News|Edit News]]
| up=[[HowTos]]
| next=[[HowTo:Checkout CVS|Checkout CVS]]
}}

[[Category:HowTos|Checkout SVN]]

Development:Video Card Compatibility

2007-09-13T06:06:21Z

Nachtwolf: /* Video Card List */ fixed my 8600

This is for the current Vega Strike svn version >= 11520.

Make sure to at least look at your ship in F6 mode and compare with

http://vegastrike.sourceforge.net/devblog/?p=22

Then fly in spec to serenity mining base...and take a mission there...

=== Video Card List ===
{|
|'''Vendor'''
|'''Card'''
|'''OS+processor'''
|'''Ram+swap'''
|'''Functional'''
|'''Shaders Supported'''
|'''Driver'''
|'''Username+caveats'''
|-
|nVidia
|GeForce 6800 GT 128MB
|Ubuntu 2.6.22.1+x86_64
|2G+2G
|Yes
|Bump Mapping + Fallback
|100.14.11
|hellcatv
|-
|nVidia
|GeForce 6600 GT 128MB
|SuSE 10.1 (2.6.16.27-0.9-smp-x86, P4-3G)
|2G+512M
|Yes
|Bump Mapping + Fallback
|1.0-9746
|klauss
|-
|ATI
|Radeon 9800 256MB
|Windows 2000 (P3-1G)
|256M+2G
|Yes
|Bump Mapping + Fallback
|Catalyst 7.3
|klauss (memory shortage needs disabled music)
|-
|NVidia
|GeForce 6600 pcie-x16 (256MB)
|Debian Unstable amd64 (2.6.23-rc3 smp preempt)
|2G+0byte
|Yes
|Bump Mapping
|100.14.11
|safemode
|-
|NVidia
|GeForce 8600 GTS pcie-x16 (256MB)
|Ubuntu 2.6.22.1+x86_64
|4G+1G
|Yes
|Bumpmapping (All?)
|100.14.11
|ace123
|}

Development:Video Card Compatibility

2007-09-13T06:05:23Z

Nachtwolf: /* Video Card List */ Add 8600

This is for the current Vega Strike svn version >= 11520.

Make sure to at least look at your ship in F6 mode and compare with

http://vegastrike.sourceforge.net/devblog/?p=22

Then fly in spec to serenity mining base...and take a mission there...

=== Video Card List ===
{|
|'''Vendor'''
|'''Card'''
|'''OS+processor'''
|'''Ram+swap'''
|'''Functional'''
|'''Shaders Supported'''
|'''Driver'''
|'''Username+caveats'''
|-
|nVidia
|GeForce 6800 GT 128MB
|Ubuntu 2.6.22.1+x86_64
|2G+2G
|Yes
|Bump Mapping + Fallback
|100.14.11
|hellcatv
|-
|nVidia
|GeForce 6600 GT 128MB
|SuSE 10.1 (2.6.16.27-0.9-smp-x86, P4-3G)
|2G+512M
|Yes
|Bump Mapping + Fallback
|1.0-9746
|klauss
|-
|ATI
|Radeon 9800 256MB
|Windows 2000 (P3-1G)
|256M+2G
|Yes
|Bump Mapping + Fallback
|Catalyst 7.3
|klauss (memory shortage needs disabled music)
|-
|NVidia
|GeForce 6600 pcie-x16 (256MB)
|Debian Unstable amd64 (2.6.23-rc3 smp preempt)
|2G+0byte
|Yes
|Bump Mapping
|100.14.11
|safemode
|-
|NVidia
|GeForce 8600 GTS pcie-x16 (256MB)
|Ubuntu amd64 (2.6.23.1 smp)
|4G+1G
|Yes
|Bumpmapping (All?)
|100.14.11
|ace123
|}

User:Ace123/Bugs

2007-09-03T00:42:09Z

Nachtwolf: /* TODO Items */ removing useless items

Development:Network:Todo

2007-09-02T23:40:33Z

Nachtwolf: cleaning up list

= Bugs for deathmatch =
* With renamed units (renamed aeon in both test2 savegame files, Player 2 seems to load fine, but cannot fire guns.
** Yes. This is a feature, not a bug. The way it sends saved games is by starting with the original entry in units.csv. If that does not exist, it sends a blank CSV file to the clients. [[User:ace123|Patrick]] 02:28, 29 July 2007 (PDT)
* Asteroids not always networked... Space junk doesn't display the cargo type because of the way it was created....

= Network TODO =

List of stuff to be done (that is... the to do in "TODO")

== CMD_CARGOUPGRADE and other Docking-related stuff ==
* Client basecomputer notifications are bad:
** Whenever anyone docked at (Fixme: any????) base buys or sells cargo/upgrade, the menu for all other players resets to the top level...
** Needs to keep menu open but still keep cargo in sync.
* To do much much later: Buying ships, missions, saving/loading from COMPY interface.
* Cargo salvage boxes - tractor beams?

== More bugs ==
* There are two different functions to send damage, and I have seen three distinct error messages in a few cases (?!?!?!)
** zonemgr.cpp:614, broadcastDamage AS WELL AS zonemgr.cpp:538, addPosition CALLS zonemgr.cpp:688, addDamage
** netserver_devices.cpp:136, sendDamages CALLED FROM Unit::ApplyLocalDamage

== Other synchronization bugs ==
* Saving games: WriteSavedGame() being used to send ADDCLIENT messages to other players, but original saved game used for player himself.

== Some other bug I wrote down, probably doesn't belong here: ==
* Gas Giant ice rings appear in front of the planet - z buffer.

== General list ==

* Clean up server-client-authserver communication
** I would really like if the messages sent and received could be done in a more uniform way.
** Clean up some unused messages.
* Login:
** Encrypted authentication, possibly using a random server token.
*** This means that login data cannot be the first packet sent -- it must first negotiate a key.
** Would SSL be a good idea here. I think we currently link with a Crypto++ library... but I'm not sure how it is currently used or how to use it.
** Make sure authserver-server-client time synchronization works correctly. Maybe every few minutes (or even hours) A,S,C should sync in case a clock gets off somehow.
* Damage:
** Theoretically implented, but I have yet to see collisions and weapons actually do damage client-side.
*** The problem is: Clients are responsible for position, so they often bounce before the server has a chance to give damage. Other times you die because the client doesn't respond fast enough! [[User:ace123|Patrick]] 20:04, 24 February 2007 (PST)
** Not sure what CMD_SCAN is to be used for... it's used in one place -- that is in NetClient::scanRequest.
** I don't know yet how a MMORPG would implement dying...
*** It would be bad to have to start from scratch every time you crash into something.
*** Have the respawn key re-join?
*** Right now you save only if you disconnect without dying. I guess that works.
*** How do we implement saving? Respawn doesn't work without a way to save... or should you keep everything the same as when you died, and then start from a random "spawn point".
**** I believe most FPS games make you lose all upgrades, but this is not an option in Vega Strike, or things will get boring quickly.
**** How do games like Ultima or WoW behave when you die? Do you lose everything (obviously you can't lose all your experience)?
***** Diablo II: A dead body is left at the place where you died. With it are all your equipment, upgrades and the gold (credits) you carried. Your team members can recover all that for you or you can hurry there yourself. Some of the gold is alsways lost however. In more difficult settings (hell and nightmare) also some of your experience is lost. ([[User:Zeog|Zeog]] 01:24, 4 July 2006 (PDT))
***** WoW: Your equipment takes some damage. With high-end gear, this costs enough that death is worth avoiding. (top-level characters don't have to worry about the XP loss). There's also the time it takes to run your ghost to your corpse. If you just log off without recovering your corpse, I think your gear takes more damage. In Vega Strike, you could lose some of your cargo, and take some damage to your upgrades.

[[Category:Development]]

User:Ace123/Bugs

2007-08-27T06:28:18Z

Nachtwolf: added some bugs.

=TODO Items=
==Bugs temp Aug 26==
* orbiting bases shouldn't be jumping.
* Fix cargo generation (I get NaN orientation for cargo). Tractoring cargo.
* Fix names of units not being sent and/or received.
===Stretching units bug===
inline Matrix WarpMatrix ( const Matrix& ctm) const{
static float cutoff =XMLSupport::parse_float (vs_config->getVariable( "graphics","warp_stretch_cutoff","500000"))*XMLSupport::parse_float(vs_config->getVariable("physics","game_speed","1"));
static float cutoffcutoff= cutoff*cutoff;
(11:26:07 PM) Patrick: inline?
(11:26:09 PM) Danny: it just checks if the speed is greater than some ammt
(11:26:12 PM) Danny: ya stupid, eh? :-)
(11:26:28 PM) Danny: it can be moved to a cpp file--but remember everyting includes unit.cpp too
(11:26:31 PM) Danny: so it doesn't matter
(11:26:52 PM) Danny: it's easy enough to make a config option that never stretches if graphicOptions.InWarp==0
(11:27:05 PM) Danny: (it needs to be a config cus some star trek mods have afterburner do warp effect)
==SOUND==
* IMPORTANT: <strike>SoundServer</strike>Music class eats up all RAM if sound device isdisabled. (I had my 64-bit Linux machine entirely lock up with 4GB of ram!)
* Only use 1 soundserver for now. Two at obce is too buggy.

==SPEC==
* (jacks, easy) Spec way too fast right now...
* NET: Client: Multiply velocity in POSUPDATE when in SPEC mode...

==CARGO==
* NET: Make sure CMD_CARGOUPGRADE always actually works serverside... no removing of cargo on server and not telling the client about it!
* NET: Cargo salvage boxes when client dies?
* Why does generic_cargo import a whole bunch of cargo????
** This causes server to spam CMD_CARGOUPGRADE's to everyone 100's of times every time generic cargo is made.
** Also, fix naming of said cargo.

==SAVEDGAMES==
* Credits bug?
* NET: Do not save games automatically (?) Add save option in net menu?

==RELEASE==
* Default System
* Give new players jump drives?
* NET: Easy way to start server
** NET: Batch script
** NET: vegaserver "--lan" option
** NET: Allow disabling of Account Server (do not check password)
** NET: Choose ship ( password = shipname? )
* NET: Version byte upon connecting

User:Ace123/Bugs

2007-08-23T08:52:12Z

Nachtwolf: /* CARGO */ Added generic_cargo bug.

=TODO Items=
==SOUND==
* IMPORTANT: <strike>SoundServer</strike>Music class eats up all RAM if sound device isdisabled. (I had my 64-bit Linux machine entirely lock up with 4GB of ram!)
* Only use 1 soundserver for now. Two at obce is too buggy.

==SPEC==
* (jacks, easy) Spec way too fast right now...
* NET: Client: Multiply velocity in POSUPDATE when in SPEC mode...

==CARGO==
* NET: Make sure CMD_CARGOUPGRADE always actually works serverside... no removing of cargo on server and not telling the client about it!
* NET: Cargo salvage boxes when client dies?
* Why does generic_cargo import a whole bunch of cargo????
** This causes server to spam CMD_CARGOUPGRADE's to everyone 100's of times every time generic cargo is made.
** Also, fix naming of said cargo.

==SAVEDGAMES==
* Credits bug?
* NET: Do not save games automatically (?) Add save option in net menu?

==RELEASE==
* Default System
* Give new players jump drives?
* NET: Easy way to start server
** NET: Batch script
** NET: vegaserver "--lan" option
** NET: Allow disabling of Account Server (do not check password)
** NET: Choose ship ( password = shipname? )
* NET: Version byte upon connecting

Development:Network:LAN Game

2007-08-19T08:48:23Z

Nachtwolf: Added LAN Game tutorial.

=Running a LAN game=
(This was written by [[ace123]]).
==Starting up server and joining it==
===Windows===
* First of all, to start a server, run "vegaserver".
* When it starts up, it will give you an IP address and port number. If you don't already have it memorized, make sure you know what it is.
** If you have a firewall enabled, you will see an image like the one here. Be ready to deal with it for vegastrike as well.
* Start Vega Strike (double-click vegastrike.exe)
===Linux===
* Run ./vegaserver in one terminal window
** You will need to run "/sbin/ifconfig" to determine your IP address if it does not tell you.
* Run ./vegastrike in another terminal window and enjoy.
==Joining a running server==
* On each computer, select "Multiplayer" and then "Independent Server".
** Type in the proper IP address, and put in a Callsign. Each player needs a different callsign.
** The password only matters if you set up a server password in vegaserver.config.
* You can run a copy of vegastrike on the computer with a server too (in fact, you should.).
** If you do that, it works fine to leave the default of "localhost".
* Click Join Game
** If all goes well, you will be brought to a ship selection dialog. It contains every ship available for purchase. I recommend a light/medium fighter of the ".stock" classification. There are a few that come with (really good) weapons equipped. Most will be empty. Really, I don't understand why some have weapons, but most including the milspec don't.
** NOTE: You may see "No ships available" or something of the like. That could be a result of having a duplicate callsign or a lot of things. Check the vegaserver console window for details.
* Once you are in the game, hit "d" to dock to the planet (named "Market").
==Buying upgrades==
** Go to the weapons room to buy upgrades since your ship will start out with nothing. The 13500 starting credits will not cover much, but some armor, shields and basic weapons is a good idea.
*** NOTE: There is a bug where whenever someone buys something everyone's screen will close off the categories again.
*** NOTE: If you find something that fails to upgrade or that leaves you with 0 credits, this is a bug. Report your starting ship, the number of credits, and approximately other upgrade types you have also gotten before. If you have anything else, sell it if you can, and your credits should be refunded.
** As to changing starting credits, this involves editing the mission file. More about this later.
* Launch from the planet. Don't attack people while they are docked at a planet, since it's mean and makes the other person have to rejoin.
==Bugs==
* Keep in mind that there are a lot of bugs if you engage in some of the weirder situations (ejecting, accepting missions or buying other ships). Such actions might end up in the client getting dropped from the game.
* Turrets usually will not work. I have some ideas on how to fix these, but this is not high priority. This also means don't get a capship that only has turrets and no gun mounts.
* You may end up at a main menu-ish screen with a message "Connection closed". TThis either means that the server was closed or else is due to a bug. It's generally easier to hit "Exit Game" and restart if you see that.

Development:Network

2007-08-19T08:15:33Z

Nachtwolf: Added LAN Game link

* [[Development:Network:LAN Game|LAN Game]] - How to start up a simple server and battle each other.
** If your computer is directly attached to the network or you have a router/firewall, you can set it up to allow others to connect to your server.

Networking documentation goes here:
* [[Development:Network:Packet format|Packet format]] - What we have implemented so far.
* [[Development:Network:Todo|Todo]] - What still needs to be done.
* [[Development:Network:Implentation status|Implentation status]].
* [[Development:Network:Testing|Testing]] - Testing the network code.
* [[Development:Network:Deathmatch|Reporting Deathmatch Problems]] - Bugs with our current deathmatch server

There's still a lot to do.

User:Ace123/Bugs

2007-08-11T09:01:22Z

Nachtwolf: {{FIXME}} Always use preview button before posting in Brain::Internet::Wikipage::AddContent(std::string &text)

=TODO Items=
==SOUND==
* IMPORTANT: <strike>SoundServer</strike>Music class eats up all RAM if sound device isdisabled. (I had my 64-bit Linux machine entirely lock up with 4GB of ram!)
* Only use 1 soundserver for now. Two at obce is too buggy.

==SPEC==
* (jacks, easy) Spec way too fast right now...
* NET: Client: Multiply velocity in POSUPDATE when in SPEC mode...

==CARGO==
* NET: Make sure CMD_CARGOUPGRADE always actually works serverside... no removing of cargo on server and not telling the client about it!
* NET: Cargo salvage boxes when client dies?

==SAVEDGAMES==
* Credits bug?
* NET: Do not save games automatically (?) Add save option in net menu?

==RELEASE==
* Default System
* Give new players jump drives?
* NET: Easy way to start server
** NET: Batch script
** NET: vegaserver "--lan" option
** NET: Allow disabling of Account Server (do not check password)
** NET: Choose ship ( password = shipname? )
* NET: Version byte upon connecting

User:Ace123/Bugs

2007-08-11T08:58:54Z

Nachtwolf: Added current revision of 0.4/0.5 TODO list.

=TODO Items=
==SOUND==
* IMPORTANT: <strike>SoundServer</strike>Music class eats up all RAM if sound device isdisabled. (I had my 64-bit Linux machine entirely lock up with 4GB of ram!)
* Only use 1 soundserver for now. Two at obce is too buggy.

==SPEC==
* (jacks, easy) Spec way too fast right now...
* NET: Client: Multiply velocity in POSUPDATE when in SPEC mode...

==CARGO==
* NET: Make sure CMD_CARGOUPGRADE always actually works serverside... no removing of cargo on server and not telling the client about it!
* NET: Cargo salvage boxes when client dies?

==SAVEDGAMES==
* Credits bug?
* NET: Do not save games automatically (?) Add save option in net menu?

==RELEASE==
* Default System
* Give new players jump drives?
* NET: Easy way to start server
** NET: Batch script
** NET: vegaserver "--lan" option
** NET: Allow disabling of Account Server (do not check password)
** NET: Choose ship ( password = shipname? )
* NET: Version byte upon connecting