VsWiki - User contributions [en]

HowTos

2009-12-20T14:52:13Z

Rubikcube: /* Compile the Vega Strike sourcecode */ changed wording

{{Languages|En|HowTos}}
{{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:Radiosity baking in Blender|Radiosity baking in Blender]]

== MODs ==
* [[HowTo:MOD|You want to create your own mod for VS? Start here.]]

=Sourcecode HowTos =
== Obtain a copy of the development-version files ==
* [[HowTo:Checkout SVN|Checkout Vega Strike's Subversion (SVN) modules.]]
* [[HowTo:Checkout SVN (Ubuntu Linux)|Checkout Vega Strike's Subversion (SVN) modules in Ubuntu.]]
* [[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, 2008) 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]]
* [[HowTo:Compile_from_released_source|Compiling from the released source]]
* 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]]
* [[HowTo:Install Wings3d|Installing Wings 3D and the Xmesh Plugin]] (deprecated)

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

HowTos

2009-12-20T14:51:52Z

Rubikcube: /* Compile the Vega Strike sourcecode */ Link to new tarball compiling

{{Languages|En|HowTos}}
{{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:Radiosity baking in Blender|Radiosity baking in Blender]]

== MODs ==
* [[HowTo:MOD|You want to create your own mod for VS? Start here.]]

=Sourcecode HowTos =
== Obtain a copy of the development-version files ==
* [[HowTo:Checkout SVN|Checkout Vega Strike's Subversion (SVN) modules.]]
* [[HowTo:Checkout SVN (Ubuntu Linux)|Checkout Vega Strike's Subversion (SVN) modules in Ubuntu.]]
* [[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, 2008) 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]]
* [[HowTo:Compile_from_released_source|Compile from the released source]]
* 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]]
* [[HowTo:Install Wings3d|Installing Wings 3D and the Xmesh Plugin]] (deprecated)

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

HowTo:Compile on OSX

2009-12-20T14:51:12Z

Rubikcube: Fixed Navigation elements

{{NAV_Manual |
| previous=[[HowTo:Compile_from_CVS|Compiling from SVN under your favourite Unixlike OS ]]
| up=[[HowTos]]
| next=[[HowTo:Compile_from_released_source|Compile from the released source]]
}}
----
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:Compile_from_released_source|Compile from the released source]]
}}
[[Category:HowTos|Compile from CVS]]

HowTo:Use GDB

2009-12-20T14:51:02Z

Rubikcube: Fixed Navigation elements

{{NAV_Manual |
| previous=[[HowTo:Compile_from_released_source|Compile from the released source]]
| up=[[HowTos]]
| next=[[HowTo:Use Dr Watson|Use Dr Watson]]
}}
----
=Using GDB with Vegastrike=
This page provides information on how to use GDB to help debug Vegastrike.

==Debugging process==
===Game compilation===
* First you have to configure Vegastrike with the <code>--enable-debug</code> option in addition to your others:<BR/><pre>./configure <your other parameters> --enable-debug</pre>

* Then <code>make</code> your Vegastrike binary:<BR/><pre>make</pre>

Please make sure you have enough disk space available before doing this. Compiling Vegastrike with <code>--enable-debug</code> eats up a huge amount of disk space.

===Run GDB===
* Start <code>gdb</code> (GNU Debugger):<BR/><pre>gdb /path/to/vegastrike</pre>

* Start the game by typing this into the gdb-console:<BR/><pre>run</pre>

* When the error occurs or it dies type
<pre>
print *this
backtrace full
up
print *this
up
print *this
</pre>

==See also==

The content of this site is mostly take from [http://vegastrike.sourceforge.net/forums/viewtopic.php?p=4688#4688 this] post in the forum.

----
{{NAV_Manual |
| previous=[[HowTo:Compile_from_released_source|Compile from the released source]]
| up=[[HowTos]]
| next=[[HowTo:Use Dr Watson|Use Dr Watson]]
}}

[[Category:HowTos|Using GDB]]

HowTo:Compile from released source

2009-12-20T14:46:39Z

Rubikcube: Created source compilation HowTo

{{NAV_Manual |
| previous=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
| up=[[HowTos]]
| next=[[HowTo:Use GDB|Debug Using GDB]]
}}
----
How to compile from a released source tarball under Linux (and most other Unix-like systems as well, probably).

This HowTo assumes that this is not the first program you compile yourself and that you know your basic tools like your shell, tar, etc.

''See also: [[HowTo:Compile from SVN]], [[HowTo:Checkout SVN (Ubuntu Linux)]]''

==Requirements==
The requirements are roughly the same as for the [[HowTo:Compile_from_CVS#Requirements|SVN version]], except that the autotools shouldn't be necessary.

==Getting the needed files==

* Get the following files, put them to a convenient location and unpack them there
** data package: Inside '''linux''' (http://sourceforge.net/projects/vegastrike/files/vegastrike/0.5.0/vegastrike-linux-0.5.0.tar.bz2/download)
** source code package: '''src''' (http://sourceforge.net/projects/vegastrike/files/vegastrike/0.5.0/vegastrike-src-0.5.0.tar.bz2/download)
* We assume that the former creates a directory called ''vegastrike-0.5.0'' and the latter one called ''vegastrike-source-0.5.0''

==Compiling==
''vegastrike-source-0.5.0'' contains all the sources we need, while ''vegastrike-0.5.0'' consists of non-code game data like models, textures, etc. It also still has precompiled binaries which cause only confusion and thus could be deleted, if you wish to:
<pre>
rm -r vegastrike-0.5.0/bin
</pre>

The configure process is pretty straighforward, as usual <code>./configure --help</code> shows all relevant options. Apart from <code>--prefix</code> to tell configure where Vega Strike shall be installed, <code>--with-data-dir</code> is quite important. A sample configure process follows:
<pre>
cd vegastrike-source-0.5.0
# This will install Vega Strike to /opt/local/games/, so the binary "vegastrike"
# can then be called as "/opt/local/games/bin/vegastrike"
# Also the data is (and should always be) located at "/home/myuser/Download/vegastrike-0.5.0"
./configure --prefix=/opt/local/games/ --with-data-dir=/home/myuser/Download/vegastrike-0.5.0/
</pre>

If <code>configure</code> finishes without errors, it's time to compile and install Vega Strike. Depending on what you set as <code>PREFIX</code>, you will have to do the install step as root:
<pre>
make && make install
# (try the -j<n> make option if you run a multicore/multiprocessor machine)
</pre>

Of course having the data in your personal home directory is not "the proper way"™ to do it, you might want to move the ''vegastrike-0.5.0'' directory to ''/opt/local/games/share/vegastrike'' first, for example. Don't forget to adapt the configure options accordingly!

----
{{NAV_Manual |
| previous=[[HowTo:Compile_on_OSX|Compiling from SVN on Mac OSX]]
| up=[[HowTos]]
| next=[[HowTo:Use GDB|Debug Using GDB]]
}}
[[Category:HowTos|Compile from released source]]