VsWiki - User contributions [en]

Development:Roadmap

2012-12-02T05:36:38Z

Pheonixstorm: More forum link fixes

{{parent_link|
|parent=[[Development]]
}}
----
This article is a work in progress, and is intended to become a centralized list of what we want to see for each release, how it can be accomplished, and who is planning to work on it.

General roadmap discussion should occur on the [http://forums.vega-strike.org/viewforum.php?f=27 Developer Focus Forum]. The wiki [[Talk:Development:Roadmap|talk page]] may be used for discussion and refinement of specific points, and conversations pertaining to the roadmap article itself.

=Roadmap=

==0.4.3==
[[Development:Roadmap:0.4.4|Road map to v0.4.4]]

==0.5.0==
[[Development:Roadmap:0.5.0|Road map to v0.5.0]]

==0.6.0==
[[Development:Roadmap:0.6.0|Road map to v0.6.0]]

==0.7.0 to 1.0.0 ==
Roadmap is not yet available.

=Unscheduled Topics and Tasks=

==Bugfixing==
* [http://sourceforge.net/tracker/?group_id=19507&atid=119507 Sourceforge Bug Tracker]
* The economic system needs a review (see [http://forums.vega-strike.org/viewtopic.php?t=10597 forum thread])
Bugs reported through the forum:
* In in system defend missions, the type of enemy ship didn't seem to display, it just had an extra space in the mission description (should have said Redeemer)
* Javelin rockets cost 30,000 credits a piece. Should be more like 30 credits I think.
* Finally, in the output after I quit, there were about 50 python traceback warnings about not finding a cultivator.stock entry in units.csv. maybe one should be added, although it's probably not vital. Peace out all.
* In some cases ship travels through stars.

==Multiplayer==

* (''ace123'') Multi-player support beta
* Server list support, ala Quake
** See [[Development:Network]]
** [http://forums.vega-strike.org/viewtopic.php?t=3895 what would you like to see in the vegastrike multiplayer?]
** [http://forums.vega-strike.org/viewtopic.php?t=3632 Multiplayer questions?]
** [http://forums.vega-strike.org/viewtopic.php?t=2176 multiplayer concerns]
** [http://forums.vega-strike.org/viewtopic.php?t=6930 if VS does go multiplayer...]

==Engine==

* Get mac building under a unified central build file (if it doesn't use ./configure)
* Rewrite vssetup so that it parses sane XML, leading the way to a more understandable config file setup.
* Fix multi-ship ownership loopholes.
* Faction level AI (or at least the imitation of one)
* Cubemap environment to replace sphere meshes [DONE]
* Make ships (ai too) dock sanely. (auto way points?) Super big ships cant dock inside small docking bays.
* Implement [http://www.ogre3d.org/ OGRE] as the rendering backend
**See [[Development:Ogre]]
**[http://forums.vega-strike.org/viewtopic.php?t=4288 Graphic engine and graphic technologies] forums thread
**[http://forums.vega-strike.org/viewtopic.php?t=6032 Ogre interface framework] forums thread
* High Dynamic Range Lighting (HDRL)
** [http://forums.vega-strike.org/viewtopic.php?t=3436 forum thread]
* Fine-tuning SPEC
** Forum threads [http://forums.vega-strike.org/viewtopic.php?t=2709 SPEC drive changes] (thread started by pincushionman) [http://forums.vega-strike.org/viewtopic.php?t=3482 spec system]
* Inter-system SPEC travel (''without'' jump nodes)
* Keyboard remap
** [http://forums.vega-strike.org/viewtopic.php?t=3445 Keyboard Bindings] (thread started by [[User:Silverain|Silverain]])
** See [[Manual:Keyboard layout]] for graphics/templates for new bindings
** See [[Manual:Config:Advanced]] for the binding-syntax in the config file
*A hierarchical fidelity model for physics simulation so as to expand the number of objects that can be concurrently simulated [ This may already have been done in 0.5, Verification?]
**Benefit: Improved ship spawn distances/locations
* Space dust
** [http://forums.vega-strike.org/viewtopic.php?t=4904 A forum discussion on the pros and cons of space debris and other means to get a feeling for speed]
* Phasing out all XMESH files
* Bump mapping [DONE - needs texturing work]
* Seamless planetary flight
* Upgrades
** user-warehouse for intermediate part storage
** selection interface for activating/deactivating parts
** fix displaying of irrelevant stats
** decouple tags and names, more tag types
*Debris Fields
*Run-time changeable configuration option and key-binding infrastructure
*In-flight map improvement
* Support full expressivity of BFXM animations
* Install time generation of all BSP files
* Videos of system or battles in the news
* Salvage-marker buoy would be a nice wrinkle to salvage economics

==Python==

* Make jump point wire frames HUD only. Allow for selective disabling/enabling of jump point wire frame representations via python.
* New campaigns. Some to put you into different factions to start out with (and thus different systems/ships).
* Flesh out storyline / Devise more story-based missions
** [http://forums.vega-strike.org/viewtopic.php?t=3246 CVS Testing -- The Campaign] (sticky forum thread)
* (''ace123'') Fixing the ugly mission class (things that would change are the functions "VS.terminateMission" and "Director.Mission.__init__")

==Data and Artwork==

* '''[OPEN]''' ''(pyramid)'' Cockpit graphics for all units.
* '''[OPEN]''' ''(pyramid)'' Supplement missing cargo graphics and improvement of low-quality cargo graphics
* '''[OPEN]''' ''(pyramid)'' Improvement of space backgrounds
* '''[OPEN]''' ''(pyramid)'' Improvement of some low-quality star images
* '''[OPEN]''' ''(pyramid)'' New ship HUD images (see: [[http://forums.vega-strike.org/viewtopic.php?p=98173 cockpit HUD shields and armor]])
* '''[OPEN]''' ''(pyramid)'' moons around planets
* New logo/icons
**See [[Development:Logos & Signage]]

* Fixers, fixers, and more fixers
* Improved planet textures (Higher quality/Fractal Enhanced?)
** [http://forums.vega-strike.org/viewtopic.php?t=3543 Auto-Enhancing Textures]
** [http://forums.vega-strike.org/viewtopic.php?t=1970 Fractal Generation System]
** [http://forums.vega-strike.org/viewtopic.php?t=2371 More pretty stuff: atmospheres and planet surfaces]
* Rework HUD & 3D Cockpits
* Strangelet's new LODs
* Ethereal walker's ship/weapons pack
* Stats rebalance
** See [[Development:Rebalance]] for detailed task list and information
**[http://forums.vega-strike.org/viewtopic.php?t=6190 Rebalance Countdown] forums thread
** [http://forums.vega-strike.org/viewtopic.php?t=3806 Announcement and discussion in the forum]
* Re-working cargo organization?
* Mine fields (just a minefield unit + AI script)

==Documentation==
* readme, sys requirements, and installation instructions for each release
* player guide update for each release
* Vega Strike universe information:
** Complete Ships list.
** Complete histories.
* Forum consolidation (Development, Artwork, Feature Requests) (Help and Bug Reports)
* Move forum to phbb3

=See Also=
* [[FAQ:Feature Requests]]
* [[Vegastrike:Features]]
* [[Development:Spaceflight]]

[[Category:Development]] [[Category:Roadmaps]]

Development:Roadmap:0.6.0

2012-12-02T05:31:11Z

Pheonixstorm: Fixed links to forum topics

Vega Strike Upon the Coldest Sea stable version 0.5.0 was released on 2008-04-24.

This is a task list for intermediate 0.5.x releases. The stuff that should get done for each intermediate and until the 0.6.0 release.

=Generic Roadmap=
This roadmap is in need of further broken down into release specific tasks and assignment of those.

==Factions rework==
*Hierarchical factions (e.g. *_citizen, affects *)
*Allowing for non-factions (privateer is already our non-faction, we just need to fix some of the behavior.)
*Ability for player joining a faction

==AI==
*Faction-level AI (race / faction strategy)
*Micro AI (ship, fg, collision avoidance, tactical and navigational AI, roles definition)
*Macro (fg/faction)
* Flightgroups
** Classification (fleet, squadron, flotilla? etc. - something to differentiate between {5 plowshares} and {3 archimedes, 2 Tesla, 8 kahan, 20 schroedinger, 10 goddard, 5 watson} )
** Flightgroups should have subsets of ships that spawn together (combined arms)
* add another dimension to roles (attack AND defend/predator AND prey roles) instead of forcing both to be the same.
* AI spec drive use, escorts...

==Content Creation Tools==
*Prerequisite: straight XML, DTD (Document Type Definition) support
*System Editor
*Unit Editor
*CSV Editor (MPL, faction_ships.py, units.csv)
*Mission Editor
*Campaign Editor
*Config Editor

==Multiplayer==
*Persistence (systems, bases, flight groups, …)

==Building/Packaging==
*Move to cmake

==Documentation==
*Document the general function/flow of the game
*Engine internals, API (development documentation)
*Python bindings
*Should we use the builtin python documentation standards for documenting this stuff--maybe in the stubs folder?
*Faction documentation

==Engine rework==
*Audio subsystem overhaul
*Support for texture versions and normal map tangents
*Shader updates

=Release Roadmap=

There are up to three sections in each roadmap release chapter:
* '''VS Engine''' relates to: modifications to c++, shaders, and python code (not including missions), repository structure changes, packaging system, support tools, ogre version
* '''VS Data - Upon The Coldest Sea''' relates to: modifications to art, data, and mission scripts for Upon The Coldest Sea (sometimes also called Vega Strike The Game as opposed to Vega Strike The Engine
* '''Documentation & Mod Tools & Other''' relates to: documentation, wiki, project web page, masters repository, project management

Each task item should also have a prefixed tag in the form of ['''STATUS'''{=OPEN, ONGOING, DONE}, development-coordinator{=''username''}]

== 0.5.1 ==

'''VS Engine'''
* '''[FINISHED]''' (''safemode'') Separate bin and data tree structure. Note: those who have data4.x already, set your client to not pull external repos or cancel when it tries to download data4.x. Then move your current data4.x alongside /bin, renaming it to data. Updates should work seamlessly and recurse into /data and /bin afterwards. Newcomers can just pull win32.
* '''[FINISHED]''' (''ace123'') Rename data4.x to data and patch corresponding source code where necessary.
* '''[FINISHED]''' (''safemode'') Make a high quality graphics texture pack (''hqtextures'').
* '''[FINISHED]''' (''safemode'') Preparation of a cross-platform packaging system (cmake)
* '''[FINISHED]''' (''pyramid'') Updates to the shader (commit chuck's unit shader)
* '''[FINISHED]''' (''pyramid'') Correct rings generation to be always in the same plane
* '''[FINISHED]''' (''pyramid'') Support for target shield gauges definition
* '''[FINISHED]''' (''klauss'') Add support for "TexturePackingVersion" variable in xmesh
* '''[FINISHED]''' (''klauss'') Add support for techniques and far z-buffering correction
* '''[FINISHED]''' (''klauss'') Tangent support for normal maps
* '''[FINISHED]''' (''klauss'') sound refactoring phase I - basic functionality
* '''[FINISHED]''' (''klauss'') movie support
* '''[FINISHED]''' (''klauss'') CubeMap engine support
* Minor bug fixes.
** '''[FINISHED]''' (''ace123'') fixed player relationship with each faction in savegame
** '''[FINISHED]''' (''pyramid'') planetary rings are always coplanar
** '''[FINISHED]''' (''pyramid'') system ownership (faction) and sector info shown in RVDU and on map
** '''[FINISHED]''' (''pyramid'') python modules can be organized in additional subfolders (ai, mission, quests)

'''VS Data - Upon The Coldest Sea'''
* '''[FINISHED]''' (''pyramid'') Extensions renaming and standardization (.image, .texture, .sprite).
* '''[FINISHED]''' (''safemode'') Added some textures to hqtextures.
* '''[FINISHED]''' (''pyramid'') 8 faces for armor HUD images
* '''[FINISHED]''' (''pyramid'') Higher pay for combat missions.
* '''[FINISHED]''' (''pyramid'') Tutorial mission
* '''[FINISHED]''' (''pyramid'') splash screen grouping in pre-load and load ani directories
* '''[FINISHED]''' (''pyramid'') additional art (planet backgrounds for lava, forest, rock, and frigid_mud, new space backgrounds, hud images)
* '''[FINISHED]''' (''pyramid'') partial extensions renaming (cockpits, sprites, backgrounds)
* '''[FINISHED]''' (''pyramid'') Visually enhanced target shield gauges
* '''[FINISHED]''' (''pyramid'') New and updated cargo and upgrade image contributions
* '''[FINISHED]''' (''pyramid'') Standardized factions coloring scheme
* '''[FINISHED]''' (''pyramid'') Units subdirectories for vessels and installations
* '''[FINISHED]''' (''pyramid'') Various new ship models (Kahan, Knight, Tridacna, ....) [http://vegastrike.sourceforge.net/devblog/?p=36 see blog]
* '''[FINISHED]''' (''pyramid'') Various new installation models (Rlaan, Uln, Shaper, ...) [http://vegastrike.sourceforge.net/devblog/?p=36 see blog]
* '''[FINISHED]''' (''pyramid'') Porting of old quests to new engine; done for: blockade, dispute, shipyard bomb, slaver, surplus

'''Documentation & Mod Tools & Other'''
* '''[FINISHED]''' (''pyramid'') Unit Converter OBJ->BFXM - a mesher frontend.
* '''[FINISHED]''' (''pyramid'') Re-organization of vessels model requirements on [[Development:3D_Models]].

== 0.5.1.5 ==

'''VS Engine'''
* '''[FINISHED]''' (''strook'') Implementing alpha version of VegaOgre, merging it into vegastrike.
the Ogre technology preview will be executable with '''VegaOgre --with-ogre-engine''' until it is released.[http://sourceforge.net/projects/vegaogre/files/trunk/ downloadable here]
* '''[FINISHED]''' (''strook'') fix bugs of the 0.5.1.5 mac version.
* '''[FINISHED]''' (''strook'') fix bugs of the 0.5.1.5 linux version.[http://forums.vega-strike.org/viewtopic.php?f=27&t=15545 see blog]
---- download the vegaogre svn release 184 to get it, there is no trunk version of it yet ---

== 0.5.1.6 ==

'''VegaOgre/VS Engine'''
* '''[STOPPED]''' (''strook'') Creating a Mac OSX app store release.
* '''[ONGOING]''' (''strook'') figure out a way to render both ogre and OpenGL contents in one window without display errors.[http://forums.vega-strike.org/viewtopic.php?f=6&t=16406 see here]
* '''[ONGOING]''' (''strook'') create a proper startup sequence for vegaogre.
* '''[ONGOING]''' (''strook'') cleanup project.

== 0.5.1.7 ==

'''VegaOgre/VS Engine'''
* '''[OPEN]''' (''strook'') create a patch for a modified unit class for creating units consisting from multiple subunits.
* '''[OPEN]''' (''strook'') create sky.
* '''[OPEN]''' (''strook'') create water.
* '''[OPEN]''' (''strook'') create surface.
* '''[OPEN]''' (''strook'') create planet physics.
* '''[OPEN]''' (''strook'') create different planet types.

== 0.5.1.8 ==

'''VegaOgre/VS Engine'''
* '''[OPEN]''' (''strook'') fix bugs of the mac version.
* '''[OPEN]''' (''strook'') fix bugs of the linux version.

== 0.5.1.9 ==

'''VS Engine'''
* '''[OPEN]''' (''???'') merging the VegaOgre code together into the vegastrike codebase trunk.

== 0.5.2 ==
'''VS Engine'''
* '''[OPEN]''' (''safemode'') Implement opcode's Ray Collider for ray-mesh collisions. (alongside bsp collider tunable via configure switch ala how opcode was done). Wont be turned on by default until 0.5.3
* '''[ONGOING]''' (''klauss'') More shader fixes, texture updates/additions.
* '''[OPEN]''' (''safemode'') Make tools and readers operate on a Proper XML format , this could be switchable via special comment at top of xml input. This is for backwards compat with non proper xml files in mods. To be made default in 0.5.5
* '''[OPEN]''' (''klauss'') sound refactoring Phase II would add mixer channels (a feature to get seamless blending with music, comm chatter and sfx)
* '''[OPEN]''' (''klauss'') put gfxlib into a class, or at the _very_least_ a namespace
* '''[ONGOING]''' (''chuck_starchaser'') CineMut shader family - v0.5
* Minor bug fixes and improvements
** '''[FINISHED]''' (''pyramid'') Show, save, and load correct stardate
** '''[FINISHED]''' (''pyramid'') Corrected missing mission description for fixer missions
** '''[OPEN]''' (''ace123'') show ship sell price in user interface

'''VS Data - Upon The Coldest Sea'''
* '''[FINISHED]''' ''(pyramid)'' Added quit image with default key mapping
* '''[OPEN]''' ''(pyramid)'' New quests, missions, and campaigns
* '''[OPEN]''' ''(pyramid)'' Revision of planet types
* '''[OPEN]''' (''chuck_starchaser'') Units re-texturing for CineMut texture packing version 0.5
* '''[ONGOING]''' (''pyramid'') Porting of old quests to new engine

'''Documentation & Mod Tools & Other'''
* '''[OPEN]''' (''???'') The Player's Guide tutorial glitches: Example: It says to buy the jump drive from Jenek...; The Alt-0 key

== 0.5.3 ==
'''VS Engine'''
* '''[OPEN]''' ''(safemode)'' Ray collider turned on, BSP stuff removed.
* '''[OPEN]''' ''(klauss)'' XGUI support for scripts
* '''[OPEN]''' ''(klauss)'' More shader fixes (should be pretty good by now), texture updates/additions
* '''[OPEN]''' ''(safemode)'' Continue to work on proper XML parsing in engine
* '''[OPEN]''' ''(safemode)'' update xml files in VS to be proper mode
* '''[OPEN]''' ''(safemode)'' setup tool
* '''[OPEN]''' (''chuck_starchaser'') CineMut shader family - v1.0

'''VS Data - Upon The Coldest Sea'''
* '''[OPEN]''' ''(pyramid)'' Create custom systems with Homeworlds for races and factions
* '''[OPEN]''' (''chuck_starchaser'') Units re-texturing for CineMut texture packing version 1.0

== 0.5.4 ==
'''VS Engine'''
* '''[ONGOING SPECIFICATION]''' (''klauss, darkmage'') content creation tools: end user tools for helping with content creation. These should be a part of vegastrike code-base, to keep things in sync and reduce maintenance.
* make proper xml mode default, remove code to parse obsolete xml-ish code.
* Get codebase stabilized in prep for refactoring graphics code.
* '''[OPEN]''' ''(safemode)'' new wormhole effects
* '''[OPEN]''' ''(safemode)'' improved ship AI
* '''[OPEN]''' ''(klauss)'' cleaning up unused mesh legacy formats (mesh_bin.cpp, ...)

'''VS Data - Upon The Coldest Sea'''

== 0.5.5 ==
'''VS Engine'''
* Refactor graphics code.
* ['''OPEN'''] (''ace123'') Make jump points be drawn on HUD only.

'''VS Data - Upon The Coldest Sea'''

== 0.5.6 ==
'''VS Engine'''
* Bug fixes.
* Texture additions/ etc
* Document refactored graphics and sound code.

'''VS Data - Upon The Coldest Sea'''

== 0.5.7 ==
'''VS Engine'''
* Thread graphics code and sound code with boost threads.
* Bug Fixing.

'''VS Data - Upon The Coldest Sea'''

== 0.5.9 ==
'''VS Engine'''
* sound refactoring Phase III would add environmental effects
* Bug Fixing.
* Documentation
* Credits

'''VS Data - Upon The Coldest Sea'''

== 0.6.0 ==
'''VS Engine'''
* Minor bug fixes from previous revision
* Packaging

'''VS Data - Upon The Coldest Sea'''
* documentation

[[Category:Roadmaps]]

Vegastrike:Project

2012-11-23T04:42:56Z

Pheonixstorm: Changed facebook link

Project Information

=About=
Vega Strike is an Open Source 3d Space Simulator. Work is proceeding on both the Vega Strike game engine and a Vega Strike Universe game data set. Both, engine and data, are in a playable state, but under continuous development.

The Vega Strike engine serves as the foundation for the Parallel Universe, Privateer Gemini Gold, Privateer Remake, Vega Trek, and Pi Armada projects, whose websites can be reached via the sidebar to the right on the project web page.

= Vision =

We enjoy the futuristic genre, and we enjoy creating content for this genre in an interesting, vast, and profoundly complex but believable universe with endless expansion and enhancement possibilities.

We want to create a generic, open, and free space simulator game of outstanding quality, both in technology and content.

We want to be the vehicle for the creation and recreation of other space games and provide the possibility for users to create their own stories.

= Mission =

We have three development drivers:
* The Vega Strike Game
* The Modding capability
* The Engine that enables both

VS (the engine) is a vehicle for groups of people to produce content in a set of genres that they enjoy creating and playing.

The particular universe (VS game) that the Minister of Information (jackS) has been working on for some time now should be the target game, to help focus and separate required features from nice features. We also want to create an entangling, profound, and believable space game whose story is set in the Vega Strike Universe.

We want to maintain close relationship with and provide to the freedom loving community a moddable open source space simulation engine that can be used to create other independent space games.

We develop feature sets for the underlying content that requires those features: a campaign, a story, a well defined economy model, well defined game play mechanics, modding requirements.

Our approach is not myopic because of a particular perception as to what resources/technology will be available.

Users can write their own stories for the universe and share them around - and if they're good we can include them as well. Think of it as universe supporting easy-to-make fan-fiction (which can include mod-based fiction).

Factions are given the ability to make their own decisions ... God's (campaign) commands are suggestions ... the campaign evolves as the players force it, and the goals need to be written to handle that.

Shortly, Vega Strike will become a space combat/simulator game and engine with fully dynamic universe creation, scriptable ai responses with dynamic decision ability, completely non-determinant campaigns, fully functional economic system that responds to the real-time gameplay state of
the universe, shader-fied openGL graphics with nifty special effects.

"One universe, infinite possibilities"

= Features =

See [[Vegastrike:Features]]

= Active Development Team =

== Project Leads and Lead Developers ==
* Daniel R Horn aka ''hellcatv'',''danielrh'' (overall coordination, lead programming, ...)
* Patrick Horn aka ''ace123'' (lead development, multiplayer, python, forum support)
* Jack Sampson aka ''jackS'' (Minister of Information, VS Universe development, art directing)

== Programmers and Developers ==
* Claudio Freire aka ''klauss'', ''klausfreire'' (engine and python development)
* Ed Sweetman aka ''safemode'' (engine development)
* aka ''pyramid'', ''pyramid3d'' (art development, python scripting, documentation)

== Developers and Contributors ==

There are also developers that have in the past but do not contribute actively at this moment. Those are listed in the credits.

Besides the developers, there is a large number of contributors from the community, be it for the engine or art and other content type for VS game.

And not to forget the modders, who give significant direction and contribution to engine development.

See: [[Vegastrike:Credits]]

= Artistic Organization =
This is the artistic organization for unit model (ships, bases) development in Vega Strike - Upon The Coldest Sea.

'''Art Director''' - provides the design briefs, gives the model final approval before it goes into the game.
* jackS

'''Art Administrator''' - knows what models go where, organizes the wiki, prioritizes development
* pyramid

'''Technical Liaison''' - tells artists what to do with regard to technical stuff
* chuck_starchaser

'''Concept Artists''' - come up with concept art
* Fendorin

'''Modeling Artists''' - model the ships and other assets
* Fendorin - senior modeling artists
* Deus Siddis
* rivalin

'''Texture Artists''' - texture the ships and stations
* Fendorin - senior texture artists

'''Voice Artists''' - provide speech voices
* [[User:Turbo|Turbo]] (tutorial quest voice, alien speech audio)
* CLoneWolf (andolian speech audio)

'''Data Integrators''' - contributors that integrate the models into the game data, fill in missing simple textures and placeholders, do file format conversions
* jackS
* esgaroth
* pyramid

'''Front End Artist''' - does overlays, wallpapers, screen savers, renders, runs the ModDB page, a deviantart page, conceptart.org thread, Game-Artist.net thread
* rivalin

= Project Setup =

== Open Source Principles ==

We often hear the complaint that features don't get implemented for a long time though they are being requested over and over again.

Being an open source community, most developers or contributors have their day-time jobs or commitments. Time is a scarce resource for those people and naturally they tend to prioritize their work on things that they are personally most interested in. Active developers do not dictate what gets contributed and what doesn't. The dictate is solely coming from contributions.

The really best way to see a particular feature implemented quickly is to pull up your sleeves and start implementing them, first integrating with your local VS copy, and when a particular feature is working satisfactory, submit it to one of the active developers for inclusion. Bear in mind that only, and only working code will get committed fast. If code or data needs additional work it will most certainly have to wait either for developer time or interest.

In this way, contributors who submit a lot will become developers.

Don't know how and what to contribute? Have a look at the [[HowTo:Contribute]] page for a starter.

== Communication Structure ==

Developers communicate between themselves on a need basis via forum personal messages, email, and irc. In addition there are frequent project meetings scheduled to discuss online ongoing developments.

In addition, we communicate with the community primarily through the forum, the web page, the dev blogs, the wiki, and equally through pm's and irc.

= History =

I read it somewhere but can't find the text right now.

In any case, it was ''hellcatv'' who started it all. The first news entry on the project page is from March 1, 1998 with news about flight engine completion, basic AI functionality, and 4 available ships. This suggests that development was going on already before that time.

= On The Web =

* [http://en.wikipedia.org/wiki/Vega_Strike Vega Strike] Wikipedia entry.
* [http://www.youtube.com/results?search_query=Vega+Strike&aq=f VS on YouTube].
* [http://www.facebook.com/pages/VegaStrike/188522714499479 Vega Strike] on facebook.
* [http://www.linuxlinks.com/article/20080523214626193/VegaStrike.html Vega Strike] on linuxlinks.com.
* [http://www.onlylinuxgames.com/vega-strike/ Vega Strike] on OnlyLinuxGames.
* 2010: [http://www.makeuseof.com/tag/space-adventures-vega-strike/ Go On Space Adventures With Vega Strike] in makeuseof.
2010: [http://www.dodownload.com/games/simulator/vega+strike.html Vega Strike 0.5] on dodownload.
* 2009: [http://blog.eracc.com/2009/09/24/gnulinux-gaming-vega-strike-for-all/ GNU/Linux Gaming – Vega Strike for All] on The ERACC Web Log.
* 2009: [http://www.webupd8.org/2009/10/free-open-source-space-simulation-game.html Vega Strike: Free, Open Source Space Simulation Game for Windows, Linux and Mac OSX].
* 2009 (DE): [http://www.linux-community.de/Internal/Artikel/Online-Artikel/Das-Spiel-zum-Wochenende-Vega-Strike Das Spiel zum Wochenende: Vega Strike ] on linux-community.
* 2007: [http://www.freesoftwaremagazine.com/articles/vegastrike Vega Strike - My kind of fun] in the [http://www.freesoftwaremagazine.com/ Free Software Magazine]
* 2003: [http://www.insidemacgames.com/news/story.php?ArticleID=6826 Vega Strike Released for Mac OS X] on insidemacgames.
* [http://tvtropes.org/pmwiki/pmwiki.php/Main/VegaStrike Vega Strike] on tvtropes.
* [http://linux.about.com/od/softgame/fr/fr_VegaS.htm Linux Game: Vega Strike] on About.com.
* [http://www.reloaded.org/download/Vega-Strike/40/ Vega Strike] on reloaded.org.
* [http://www.absoluteastronomy.com/topics/Vega_Strike Vega Strike] on absoluteastronomy.

= Roadmap =
See [[Development:Roadmap]]

Vegastrike

2012-11-23T04:39:02Z

Pheonixstorm: Corrected forum url

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

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956; 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|Player's Planet]]'''</center>
|style="background:#afa8ee;" width="50%"|<center>'''[[Development|Contributor's Station]]'''</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="color:#493956;"
|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|Information for new users]]
* [[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 the Vega Strike Engine
|}
|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>
'''''Want to contribute but don't know where to start'''''
* [[HowTo:Contribute|The Vega Strike Contributor's Guide]]
* [[Development]] & [[HowTos]] - Miscellaneous information for contributors
'''''For Artists and Modders'''''
* [[Development#Artistic_Contribution|Artists Guidelines]] - 3d models, space scapes, planet and station backgrounds, ...
* [[Development#Data_Modding|Modding Guidelines]] - config variables, missions, quests, modding tools, ...
* [[Artstyle_guides|Art Style Guides]] - VS universe style information for artists
'''''Engine References'''''
* [[DOCs]] - Engine documentation
'''''For Coders'''''
* [[Development#Code-related_Development|Coding Guidelines]] - dependencies, svn layout, code style, network protocol, ...
'''''Administrative'''''
* [[Vegastrike:Project|Project]] - Project information page
* [[Development:Roadmap|Roadmap]] - Vega Strike development plan
* [[Development#Status.2Ftask_list_pages|Status & Task List pages]]
* [[FAQ:Feature_Requests|Feature Requests]] - Ask, and you will have asked.
'''''Other'''''
* [[FAQ]]s - Frequently asked questions
* [[HowTos#Sourcecode HowTos|Sourcecode HowTos]] - Getting and installing the latest unstable version.
* [http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/ Browse the SVN repository]

|}

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956;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:#7dcf7d;" width="50%"|<center>'''Wiki Trading Post'''</center>
|style="background:#ae6e9f;" width="50%"|<center>'''Help Shipyard'''</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]].
*[http://forums.vega-strike.org/viewtopic.php?f=21&t=13186 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://forums.vega-strike.org 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)

Recommended open-source multi-protocol clients (IRC, ICQ/AIM, Jabber, Y!M, ...):
* Linux: [http://kopete.kde.org/ Kopete]
* Windows: [http://ayttm.sourceforge.net/ Ayttm]
* Mac: [http://fire.sourceforge.net/ Fire]

|}

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956;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://forums.vegastrike.org forum] and create an account there'''. This is because the logins are linked and creation is only possible there.
</center>
|}

----
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.

Development:Operating System Compatibility

2012-11-23T04:34:55Z

Pheonixstorm:

=== Operating System List ===
{|
|'''Platform'''
|'''Operating System Version (Build)'''
|'''Download Method'''
|'''Functional'''
|'''Ram+Swap'''
|'''Vegastrike Version'''
|'''Username+caveats'''
|-
|Windows
|Windows Vista SP1 (6.0.6001.16659)
|SVN Download via TortoiseSVN
|Yes
|1G+1G
|SVN Rev. 12496
|programmerandrew
|-
|Windows
|Windows 7 M3 (6.1.6801)
|SVN Download via TortoiseSVN
|Yes- with caveats
|1G+1G
|0.5 & SVN Rev. 12496
|programmerandrew + Extremely slow load and framerate on SVN
|-
|Windows
|Windows 7 x64
|SVN Download via TortoiseSVN
|Partial
|1G+1G
|0.5.1 & SVN Rev. 13449
|pheonixstorm + Crash reports on some Win7 64bit users. Possible fix
|-
|Windows
|Windows XP SP2
|.exe installer
|Yes
|1G+1G
|0.5.0
|Minthos
|-
|Linux
|Linux Ubuntu (8.10 Intrepid, 64-bit)
|.RAR Version, through VS homepage
|Yes - with caveats
|1G+1G
|0.5.0
|MC707 + Minimal system requirements (except for graphics card). Only the vegastrike-64 binary works. vssetup, mesher and vegaserver do not seem to work. To change settings, modify vegastrike.config.
|-
|Linux
|Linux Ubuntu (8.10 Intrepid, 64-bit)
|SVN Download via Terminal
|Yes - with caveats
|1G+1G
|SVN Rev. 12536
|MC707 + Problems with Compiz. If you don't have compiz, don't worry. Otherwise, use an external application (like [http://forlong.blogage.de/entries/pages/Compiz-Switch this]) to temporarly disable compiz, then run normally.
|-
|Linux
|Gentoo 2008.0, x86_64 multilib (2.6.25-gentoo-r6 gcc 4.1.2)
|.rar from sourceforge
|Yes - with caveats
|1G+1G
|0.5.0
|Minthos + Game works, vssetup works, installer doesen't quite work. No problem, just run the game from where you extracted the rar.
|-
|Linux
|Gentoo 2008.0, x86_64 multilib (2.6.25-gentoo-r6 gcc 4.1.2)
|svn linux from terminal
|Yes - with caveats
|1G+1G
|0.5.0 data and 12550 code
|Minthos + Compiles and runs with datafiles from 0.5.0 and the techniques directory added from svn. Noticed some texture missing, didn't test thoroughly.
|-
|Macintosh
|Mac OS X ({{FIXME}})
|{{FIXME}}
|{{FIXME}}
|{{FIXME}}
|{{FIXME}}
|{{FIXME}}

Development:Texture Guidelines

2011-11-28T06:35:29Z

Pheonixstorm: Minor update

=Texture Guidelines=
==Introduction==
The intention of this document is to give artists using the Vega Strike engine some suggested guidelines to follow in creating materials for models. These are not fixed rules, and those of you with experience will appreciate that some of these can be broken. For those of you who are unsure of Vega Strike's capabilities, this may be of use. If you haven't already, you may also wish to have a look at the corresponding [[Development:Model_Guidelines|model guidelines]].

'''Note:''' If you wish to contribute a ship to the game Vega Strike, please see the [[Development:3D_Models|3D Models]] page and/or contact [[User:jackS|jackS]]. Texturing styles will be of extra importance in characterizing a ship.

==Specifics==
{{Fixme}}Incomplete, unedited, inaccurate braindump:

Image maps ... bigger is better (as we can keep the originals and use scaled down if it's too big for current vid cards). .png or .jpg are supported (we prefer to receive .png so we don't lose quality through whatever, but if it's big it doesn't really matter).

We support specular, glow, damage, and normal maps ... I think that's it?

Don't limit yourself to black and white....colour is good!

[[Category:Development|Texture Guidelines]]
[[Category:Artwork|Texture Guidelines]]
[[Category:Modeling|Texture Guidelines]]

Vegastrike

2011-11-28T06:32:26Z

Pheonixstorm: Edit forums link

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

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956; 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|Player's Planet]]'''</center>
|style="background:#afa8ee;" width="50%"|<center>'''[[Development|Contributor's Station]]'''</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="color:#493956;"
|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|Information for new users]]
* [[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 the Vega Strike Engine
|}
|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>
'''''Want to contribute but don't know where to start'''''
* [[HowTo:Contribute|The Vega Strike Contributor's Guide]]
* [[Development]] & [[HowTos]] - Miscellaneous information for contributors
'''''For Artists and Modders'''''
* [[Development#Artistic_Contribution|Artists Guidelines]] - 3d models, space scapes, planet and station backgrounds, ...
* [[Development#Data_Modding|Modding Guidelines]] - config variables, missions, quests, modding tools, ...
* [[Artstyle_guides|Art Style Guides]] - VS universe style information for artists
'''''Engine References'''''
* [[DOCs]] - Engine documentation
'''''For Coders'''''
* [[Development#Code-related_Development|Coding Guidelines]] - dependencies, svn layout, code style, network protocol, ...
'''''Administrative'''''
* [[Vegastrike:Project|Project]] - Project information page
* [[Development:Roadmap|Roadmap]] - Vega Strike development plan
* [[Development#Status.2Ftask_list_pages|Status & Task List pages]]
* [[FAQ:Feature_Requests|Feature Requests]] - Ask, and you will have asked.
'''''Other'''''
* [[FAQ]]s - Frequently asked questions
* [[HowTos#Sourcecode HowTos|Sourcecode HowTos]] - Getting and installing the latest unstable version.
* [http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/ Browse the SVN repository]

|}

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956;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:#7dcf7d;" width="50%"|<center>'''Wiki Trading Post'''</center>
|style="background:#ae6e9f;" width="50%"|<center>'''Help Shipyard'''</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]].
*[http://vegastrike.sourceforge.net/forums/viewtopic.php?f=21&t=13186 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)

Recommended open-source multi-protocol clients (IRC, ICQ/AIM, Jabber, Y!M, ...):
* Linux: [http://kopete.kde.org/ Kopete]
* Windows: [http://ayttm.sourceforge.net/ Ayttm]
* Mac: [http://fire.sourceforge.net/ Fire]

|}

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956;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://forums.vegastrike.org forum] and create an account there'''. This is because the logins are linked and creation is only possible there.
</center>
|}

----
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.

Manual

2011-11-28T06:31:01Z

Pheonixstorm: Corrected a few things and took out a non-functional link

{{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 are tired 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 hunting, patrols, battles and escort missions. Feel like traveling? 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)]]

|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 (deprecated) [http://cvs.sourceforge.net/viewcvs.py/*checkout*/vegastrike/data4.x/documentation/Vega_Strike_Players_Guide.pdf Vega Strike Player's Guide (PDF)]

SVN [http://vegastrike.svn.sourceforge.net/viewvc/*checkout*/vegastrike/trunk/data/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)
* 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}} referring to the w key; {{Key:EN:Shift left}} + {{Key:EN:W}} referring 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]]

Manual:Views

2011-10-17T16:26:03Z

Pheonixstorm: Spam Removal

{{Languages|En|Manual:Views}}
{{NAV_Manual |
| previous=[[Manual:Targeting|Targeting]]
| up=[[Manual#Inflight|Manual]]
| next=[[Manual:HUD|HUD]]
}}
----
=Views=
Vega Strike allows you to look around your ship, and your local space. It does this in two ways: by providing a cockpit view and an outside camera position view. You may move from one view directly to another by pressing the appropriate key.

==Cockpit View==
Cockpit views are just that: from your pilot's seat, this is what you would see. These views represent looking through the front and side cockpit view ports, and a camera pointing from the rear of the ship.

==Cockpit View Keys==
* {{Key:EN:1}} = View Forward. This view is what appears initially in flight and is otherwise known as the cockpit view. This view contains all the necessary information and displays to fly. While in view forward, pressing {{Key:EN:1}} will change from the cockpit view (with cockpit struts) to the Heads Up Display ([[Manual:HUD|HUD]]). The [[Manual:HUD|HUD]] provides the same information as the forward view but removes the cockpit surround. Press the key once more to return to cockpit view.
* {{Key:EN:2}} = View Left. This view is looking through the cockpit plasglass over your left shoulder.
* {{Key:EN:3}} = View Right. This view is looking through the cockpit plasglass over your right shoulder.
* {{Key:EN:4}} = View Reverse. As a pilot cannot look back through the ship, this view represents a camera mounted and looking to the rear of the ship.

==Camera View==
A camera view is best described as a single viewpoint or eye located in one position in space. The Panning Camera's ({{Key:EN:5}} and {{Key:EN:6}}) position is movable. While in these views, use these keys {{Key:EN:Q}} {{Key:EN:Z}} {{Key:EN:S}} {{Key:EN:F}} to move the camera position in the appropriate direction.

==Camera View Keys==
* {{Key:EN:5}} = Chase cam. This view seats a camera behind and above your ship's engines, looking forward. This position is static no matter the ship's movements. Best imagined as having a second ship tailing your current ship, with you in that second cockpit. This view allows you to examine all markings and detail on your ship.
* {{Key:EN:6}} = Panning Camera. This view positions a camera at a single point in space, facing your ship. You may rotate the camera about your ship using the panning keys.
* {{Key:EN:7}} = Target Camera. This view places the camera at a location looking past your ship towards your current target.
* {{Key:EN:8}} = Target Panning Camera. This view positions a camera at a single point in space, facing your target. You may rotate the camera about your target using the panning keys.
* {{Key:EN:9}} = Zoom View In. While in one of the camera views, this function will move the viewpoint towards the object viewed.
* {{Key:EN:0}} = Zoom View Out. While in one of the camera views, this function will move the viewpoint towards the object viewed.
* {{Key:EN:I}} = Screenshot. Takes a screenshot of your current view, removing any targeting brackets or docking clamps from the shot.

= See also =
* See [[Manual:Keyboard layout]] for the necessary command keys.
----
{{NAV_Manual |
| previous=[[Manual:Targeting|Targeting]]
| up=[[Manual#Inflight|Manual]]
| next=[[Manual:HUD|HUD]]
}}
[[Category:Manual|Views]]

HowTo:VCPP Compiling

2011-10-13T23:55:09Z

Pheonixstorm: Added entry for VC10

{{NAV_Manual |
| previous=[[HowTo:Checkout SVN (Ubuntu Linux)|Checkout SVN (Ubuntu Linux)]]
| 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-vc</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-vc9</code> for all Visual C++ editions, <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) Deprecated
* <code>vegastrike/vega-vc7/</code> - The project files. (VISUAL C++ 7.x) Deprecated
* <code>vegastrike/vega-vc8/</code> - The project files. (VISUAL C++ 8.0) Deprecated
* <code>vegastrike/vega-vc9/</code> - The project files. (VISUAL C++ 9.0 and higher)
* <code>vegastrike/win32/</code> - The newer version of data. Until the change is made in the Vegastrike project setting binaries will be create in vega-vc9/Release or vega-vc9/Debug. <strike>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.</strike>

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++ 10.0 (2010 Express)==

Currently there are no working project files for VC10. This will be changing in the near future so please be patient. For now just copy everything from the <code>trunk/vega-vc9</code> folder into a newly created vega-vc10 folder and convert the VC9 project files.

You can download a copy of VC10 Express from [http://www.microsoft.com/express/download/ Download Visual C++ 2008 Express Edition].
If you encounter any issues post a new topic in the [http://vegastrike.sourceforge.net/forums/viewforum.php?f=5 Compiling Problems] forum.

==Visual C++ 9.0 (2008 Express)==

This is likely only for Windows XP SP3 and Vista (so probably not Windows 2000). Apparently no Platform SDK is necessary. Note that it is required that the local file and directory structure is identical to the one on SVN. You need to checkout the following: <code>trunk/vegastrike</code>, <code>trunk/vega-vc9</code>, <code>trunk/win32</code>. If the above is wrong you will need to download the 2008 SDK or higher.

# [http://www.microsoft.com/express/download/ Download Visual C++ 2008 Express Edition].
# Make sure you are logged on as admin. Otherwise the VC++ 2008 EE installation will fail. 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.
# To update for Python 2.7 you will need to download the latest 2.7 release: [http://www.python.org/download/ Download latest Python 2.7]
# Compile Python using their <code>Python-2.7.1\PCbuild\pcbuild.sln</code> solution file. Make sure it works (<code>python.exe</code> starts up).
# Substitute the corresponding Python 2.7 files from <code>Python-2.7.1\PCbuild</code> and <code>Python-2.7.1\include</code>. Python also requires a <code>pyconfig.h</code> inside your <code>vega-vc9\include\python</code>, you can copy it from <code>Python-2.7.1\PC</code>.
# In VC++ 2008 EE, update the vegastrike project properties: in configuration properties -> linker -> input -> additional dependencies, change the python version to 2.7. (It should be the last one in the list.)
# Apply the <code>VCExpress.diff</code> to fix the resource file for use with Visual C++ Express.
# Vegastrike should now build normally.

==Visual C++ 8.0 (2005 Express)(deprecated)==
This is left here in case someone wants to attempt a working VC8 build
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 C++ 8.0(2005 Express) plus the Code::Blocks IDE (deprecated)==
You can download Visual C++ 8.0(2005 Express) after you acquired a vcsetup.exe for Visual C++ 8.0. These are still being offered on some download sites.
The main advantages of Visual C++ 8.0 over later versions are that it works for older OSes like Windows 2000 and that there is a vegastrike project file for it, which you can check out from svn as vega-vc8.
You will also need an SDK, I used the Platform SDK PSDK-x86.exe (1.3 MB) which you can find with the query “Windows Server 2003 Platform SDK Web” in a search engine.
You will need to enable internet explorer for a minute as the default browser to install the PSDK.
Also try to get the vcredist_x86.exe for Visual C++ 8.0(2005 Express) if you want to share your vegastrike binary with others.
You can acquire the code::block development environment from www.codeblocks.org.

You might want to make a copy of your SVN checkout tree now, to have a clean copy just in case of the code in VegaStrike/ and the project files in vega-vc8/
Start code::blocks, choose VC2005/2008 as default tool chain and import the .sln solution file from vega-vc8 into a workspace. Use the vc8 2005/2008 compiler.
Double click the vegastrike project so that it is selected in bold. Go to Project/Build options and add /EHsc to vegastrike in other compiler options, remove /W from all projects and choose a warning level you like instead for each compiling option, like /W1 for release and /W3 for a debug build.
I have only tried the Win32 and Win32 debug buildsYou will notice that the debug build sets other libraries in linker settings. Basically the left side of the settings is used to include libraries while the right side is used to NOT include the default libraries. Some people have reported that they need to add "/NODEFAULTLIB:libcmt" manually there to exclude libcmt from being linked which results in a conflict.(I also removed /ZI and added insted on the left side /Zi /D_DEBUG to have debug symbols, I'm not sure which is better).

You need to edit the file Resources.rc to read 
#include <WinResrc.h>
instead of 
#include "afxres.h"

If you should discover a problem with the PNG or Python libraries, or simply want to try out newer ones, recall that each of these libraries/dlls needs to be one built with the same compiler you use for vegastrike.
Be warned that for libpng-1.2.34 the optimized build does not work, while the debug build(without any optimization) works with the vc8 compiler.

You can also choose where the binaries you produced end up, but I left it to default settings which is in the ../win32/bin directory, thats right aside ../VegaStrike.
Finally I took the executable, which is named vegastrikeR.exe for the release version, and all other files produced and placed them into the directory structure of an old VegaStrike install.
Running vegaStrike produced errors, which meant I had to resolve them by checking out the directories bases,mission,programs,sounds/missions,techniques and textures directories from SVN using the repository browser. (I think you can even do without some of these.)
Copying the directories into and over the directory tree of the old install produced a working binary.
At least it works as far as I know - I didn't get to test much yet.

You can debug programs in the VC++ IDE by creating a new project and adding an executable as a subproject.

Enjoy!

==Visual Studio 7.x (deprecated)==

===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 (deprecated)===
''(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'''

==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)

=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]]

Vegastrike

2011-10-13T17:40:36Z

Pheonixstorm: Spam Removal

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

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956; 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|Player's Planet]]'''</center>
|style="background:#afa8ee;" width="50%"|<center>'''[[Development|Contributor's Station]]'''</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="color:#493956;"
|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|Information for new users]]
* [[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 the Vega Strike Engine
|}
|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>
'''''Want to contribute but don't know where to start'''''
* [[HowTo:Contribute|The Vega Strike Contributor's Guide]]
* [[Development]] & [[HowTos]] - Miscellaneous information for contributors
'''''For Artists and Modders'''''
* [[Development#Artistic_Contribution|Artists Guidelines]] - 3d models, space scapes, planet and station backgrounds, ...
* [[Development#Data_Modding|Modding Guidelines]] - config variables, missions, quests, modding tools, ...
* [[Artstyle_guides|Art Style Guides]] - VS universe style information for artists
'''''Engine References'''''
* [[DOCs]] - Engine documentation
'''''For Coders'''''
* [[Development#Code-related_Development|Coding Guidelines]] - dependencies, svn layout, code style, network protocol, ...
'''''Administrative'''''
* [[Vegastrike:Project|Project]] - Project information page
* [[Development:Roadmap|Roadmap]] - Vega Strike development plan
* [[Development#Status.2Ftask_list_pages|Status & Task List pages]]
* [[FAQ:Feature_Requests|Feature Requests]] - Ask, and you will have asked.
'''''Other'''''
* [[FAQ]]s - Frequently asked questions
* [[HowTos#Sourcecode HowTos|Sourcecode HowTos]] - Getting and installing the latest unstable version.
* [http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/ Browse the SVN repository]

|}

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956;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:#7dcf7d;" width="50%"|<center>'''Wiki Trading Post'''</center>
|style="background:#ae6e9f;" width="50%"|<center>'''Help Shipyard'''</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]].
*[http://vegastrike.sourceforge.net/forums/viewtopic.php?f=21&t=13186 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)

Recommended open-source multi-protocol clients (IRC, ICQ/AIM, Jabber, Y!M, ...):
* Linux: [http://kopete.kde.org/ Kopete]
* Windows: [http://ayttm.sourceforge.net/ Ayttm]
* Mac: [http://fire.sourceforge.net/ Fire]

|}

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956;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.
</center>
|}

----
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.

Vegastrike

2011-10-11T08:12:01Z

Pheonixstorm: Spam Removal

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

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956; 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|Player's Planet]]'''</center>
|style="background:#afa8ee;" width="50%"|<center>'''[[Development|Contributor's Station]]'''</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="color:#493956;"
|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|Information for new users]]
* [[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 the Vega Strike Engine
|}
|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>
'''''Want to contribute but don't know where to start'''''
* [[HowTo:Contribute|The Vega Strike Contributor's Guide]]
* [[Development]] & [[HowTos]] - Miscellaneous information for contributors
'''''For Artists and Modders'''''
* [[Development#Artistic_Contribution|Artists Guidelines]] - 3d models, space scapes, planet and station backgrounds, ...
* [[Development#Data_Modding|Modding Guidelines]] - config variables, missions, quests, modding tools, ...
* [[Artstyle_guides|Art Style Guides]] - VS universe style information for artists
'''''Engine References'''''
* [[DOCs]] - Engine documentation
'''''For Coders'''''
* [[Development#Code-related_Development|Coding Guidelines]] - dependencies, svn layout, code style, network protocol, ...
'''''Administrative'''''
* [[Vegastrike:Project|Project]] - Project information page
* [[Development:Roadmap|Roadmap]] - Vega Strike development plan
* [[Development#Status.2Ftask_list_pages|Status & Task List pages]]
* [[FAQ:Feature_Requests|Feature Requests]] - Ask, and you will have asked.
'''''Other'''''
* [[FAQ]]s - Frequently asked questions
* [[HowTos#Sourcecode HowTos|Sourcecode HowTos]] - Getting and installing the latest unstable version.
* [http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/ Browse the SVN repository]

|}

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956;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:#7dcf7d;" width="50%"|<center>'''Wiki Trading Post'''</center>
|style="background:#ae6e9f;" width="50%"|<center>'''Help Shipyard'''</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]].
*[http://vegastrike.sourceforge.net/forums/viewtopic.php?f=21&t=13186 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)

Recommended open-source multi-protocol clients (IRC, ICQ/AIM, Jabber, Y!M, ...):
* Linux: [http://kopete.kde.org/ Kopete]
* Windows: [http://ayttm.sourceforge.net/ Ayttm]
* Mac: [http://fire.sourceforge.net/ Fire]

|}

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956;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.
</center>
|}

----
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.

Vegastrike

2011-10-11T08:08:59Z

Pheonixstorm: Spam Rmoval

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

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956; 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|Player's Planet]]'''</center>
|style="background:#afa8ee;" width="50%"|<center>'''[[Development|Contributor's Station]]'''</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="color:#493956;"
|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|Information for new users]]
* [[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 the Vega Strike Engine
|}
|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>
'''''Want to contribute but don't know where to start'''''
* [[HowTo:Contribute|The Vega Strike Contributor's Guide]]
* [[Development]] & [[HowTos]] - Miscellaneous information for contributors
'''''For Artists and Modders'''''
* [[Development#Artistic_Contribution|Artists Guidelines]] - 3d models, space scapes, planet and station backgrounds, ...
* [[Development#Data_Modding|Modding Guidelines]] - config variables, missions, quests, modding tools, ...
* [[Artstyle_guides|Art Style Guides]] - VS universe style information for artists
'''''Engine References'''''
* [[DOCs]] - Engine documentation
'''''For Coders'''''
* [[Development#Code-related_Development|Coding Guidelines]] - dependencies, svn layout, code style, network protocol, ...
'''''Administrative'''''
* [http://www.mightydesigners.com Logo Design Contest]
* [[Vegastrike:Project|Project]] - Project information page
* [[Development:Roadmap|Roadmap]] - Vega Strike development plan
* [[Development#Status.2Ftask_list_pages|Status & Task List pages]]
* [[FAQ:Feature_Requests|Feature Requests]] - Ask, and you will have asked.
'''''Other'''''
* [[FAQ]]s - Frequently asked questions
* [[HowTos#Sourcecode HowTos|Sourcecode HowTos]] - Getting and installing the latest unstable version.
* [http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/ Browse the SVN repository]

|}

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956;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:#7dcf7d;" width="50%"|<center>'''Wiki Trading Post'''</center>
|style="background:#ae6e9f;" width="50%"|<center>'''Help Shipyard'''</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]].
*[http://vegastrike.sourceforge.net/forums/viewtopic.php?f=21&t=13186 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)

Recommended open-source multi-protocol clients (IRC, ICQ/AIM, Jabber, Y!M, ...):
* Linux: [http://kopete.kde.org/ Kopete]
* Windows: [http://ayttm.sourceforge.net/ Ayttm]
* Mac: [http://fire.sourceforge.net/ Fire]

|}

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956;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.
</center>
|}

----
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.

Vegastrike

2011-10-10T19:58:41Z

Pheonixstorm: Spam Removal

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

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956; 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|Player's Planet]]'''</center>
|style="background:#afa8ee;" width="50%"|<center>'''[[Development|Contributor's Station]]'''</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="color:#493956;"
|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|Information for new users]]
* [[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 the Vega Strike Engine
|}
|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>
'''''Want to contribute but don't know where to start'''''
* [[HowTo:Contribute|The Vega Strike Contributor's Guide]]
* [[Development]] & [[HowTos]] - Miscellaneous information for contributors
'''''For Artists and Modders'''''
* [[Development#Artistic_Contribution|Artists Guidelines]] - 3d models, space scapes, planet and station backgrounds, ...
* [[Development#Data_Modding|Modding Guidelines]] - config variables, missions, quests, modding tools, ...
* [[Artstyle_guides|Art Style Guides]] - VS universe style information for artists
'''''Engine References'''''
* [[DOCs]] - Engine documentation
'''''For Coders'''''
* [[Development#Code-related_Development|Coding Guidelines]] - dependencies, svn layout, code style, network protocol, ...
'''''Administrative'''''
* [[Vegastrike:Project|Project]] - Project information page
* [[Development:Roadmap|Roadmap]] - Vega Strike development plan
* [[Development#Status.2Ftask_list_pages|Status & Task List pages]]
* [[FAQ:Feature_Requests|Feature Requests]] - Ask, and you will have asked.
'''''Other'''''
* [[FAQ]]s - Frequently asked questions
* [[HowTos#Sourcecode HowTos|Sourcecode HowTos]] - Getting and installing the latest unstable version.
* [http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/ Browse the SVN repository]

|}

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956;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:#7dcf7d;" width="50%"|<center>'''Wiki Trading Post'''</center>
|style="background:#ae6e9f;" width="50%"|<center>'''Help Shipyard'''</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]].
*[http://vegastrike.sourceforge.net/forums/viewtopic.php?f=21&t=13186 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)

Recommended open-source multi-protocol clients (IRC, ICQ/AIM, Jabber, Y!M, ...):
* Linux: [http://kopete.kde.org/ Kopete]
* Windows: [http://ayttm.sourceforge.net/ Ayttm]
* Mac: [http://fire.sourceforge.net/ Fire]

|}

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956;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.
</center>
|}

----
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:Checkout SVN

2011-10-09T02:29:26Z

Pheonixstorm: Undo revision 18372 by Greggggg (talk)

{{Languages|En|HowTo:Checkout SVN}}
{{NAV_Manual |
| previous=[[HowTo:Edit News|Edit News]]
| up=[[HowTos]]
| next=[[HowTo:Checkout SVN (Ubuntu Linux)|Checkout SVN (Ubuntu Linux)]]
}}
----

NOTE:Recently the SVN location of the data directory has changed. Use svn -switch to fix this.

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.
* '''hqtextures''' - Optional High Quality Texture pack
* '''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.

--------------
Ogre Branch

* '''data6.x''' - Data for the old OGRE branch - included in the old OGRE branch.
* '''ogre_branch''' - the old OGRE branch.

You may download the old OGRE branch including the data6.x dir using this URL: http://vegastrike.svn.sourceforge.net/svnroot/vegastrike/branches/ogre_branch/

The [[Development:Ogre|new OGRE branch - vegaogre]] resides on a new repository.
Plz visit it here: https://sourceforge.net/projects/vegaogre/

-------------------------------------------

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

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

=Linux Clients=
== Ubuntu ==
''Ubuntu users (Debian as well?) go [[HowTo:Checkout SVN (Ubuntu Linux)|here]] for a copy-paste, step by step, newb friendly tutorial.''

==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>
The following syntax...
<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 tutorial purposes, we will create a directory called ''VegaStrike'' in our user's home-directory.
<pre>User@UserMachine:~$ mkdir VegaStrike</pre>
* Change into this newly created directory. In our case:
<pre>User@UserMachine:~$ cd VegaStrike</pre>
Note for newbs: The directory ''is case sensitive''. If you type: cd vegastrike or Vegastrike, it won't find the directory.

===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, (optionally) 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. Copy and paste, ''in order''.
<pre>User@UserMachine:~/VegaStrike$ svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike
then
User@UserMachine:~/VegaStrike$ svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/data</pre>
This leaves you with two 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

''Notice:''
As of 0.5.1 you will be able to choose not to download the boost revisions included in the vegastrike module. The Boost revisions are external definitions, so including the --ignore-externals argument when checking out vegastrike will result in none of the boost revisions from downloading. This greatly reduces your download time. If you dont have a system installed boost setup with boost-python, you can pull the specific version of boost you want (1.28 or 1.35) by updating that directory specifically. eg:
No Boost:
svn co --ignore-externals https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/vegastrike vegastrike

* You want 1.35:
<pre>svn update vegastrike/boost/1_35</pre>

Now, you have to supply ./configure with a specific boost rev when you are choosing anything other than 1.28. Also, choosing a boost rev that you haven't downloaded yet would be problematic. If none are to be downloaded, use --with-boost=system, when using system boost, you have to make sure the python version ./configure uses matches the one boost-python was linked with. Some distros will supply multiple boost revs, python revs, but only one rev combo for boost-python.

===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, so just follow the steps in the compile from SVN page.

===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 (''vegastrike'' 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.

As of 0.5.1 there is a module in svn called ''hqtextures''. hqtextures, is an optional high quality texture pack that will override the textures in data that exist in hqtextures. These are jpegs that wont be compressed in-game. Prior to 0.5.1, you have to edit the config file by hand to uncomment the line that enables the hqtextures module. At 0.5.1, it should be a setting in vssetup. Enabling it while not having it downloaded wont hurt anything.

You have to check it out of svn and put it next to data. So if data is in /usr/local/games/vegastrike You would:
<pre>svn co https://vegastrike.svn.sourceforge.net/svnroot/vegastrike/trunk/hqtextures /usr/local/games/vegastrike/hqtextures</pre>
To be sure that hq textures is being used, check for the message about finding HQ Texture Pack at the start of the console output when running vegastrike.

===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. Checking out "win32" will download the "bin" and "data" directories. You will find the executable program inside the "bin" folder.

As of 2010-11-20, the win32 module is working on the HEAD. However, there are times that the win32 module is out of date and incompatible with the data directory in svn. Revision 12933 is a known revision where things work if you find HEAD broken for some reason. Please update this wiki entry if HEAD breaks and you have a later revision number that has no problems preventing gameplay.

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===
Tortoise SVN lets you work with files under SVN version control directly from Windows Explorer (just like TortoiseCVS). 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 Explorer where you will download your modules (called Sandbox, SVN or similar working location name);
* Within that folder, create another folder (for example, VS or win32);
* 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.
[Note: The download is 800+ MB and will take some time.]
* After downloading, run the Setup program in the "bin" folder to set your screen size, etc. More importantly, this will tell Vegastrike where to find the "data" directory. You only have to do this once.
* Then you can run VEGASTRIKE.EXE in the "bin" directory to play.

===Specifying a Revision===
Because SVN is the active development repository, sometimes the latest copy will have problems and won't work. At the time of this writing this section (2010-09-18) the units.csv file has a problem and the game won't load. This has been resolved in a later version, but we may run into the problem again so these instructions might be helpful if HEAD breaks again. Luckily SVN has a revision system that allows you to choose a point in time from before the problem was introduced. See the above section "Windows Clients" for the latest known revision that works with win32.

{{FIXME}}: We need a way for people to determine the best revision number to use when the HEAD is broken. Perhaps a section at the top of this document? In the mean time, check out the help section of the forums.

If you need to specify a revision when using TortoiseSVN , you need to do so for each module, including dependent modules. So assuming you used the directory name "VS" on the above usage directions, you would:

* Right mouse click on your "VS" directory, and choose "TourtoiseSVN->Update to revision..."
* Type in the revision number, and hit OK. This will update everything under VS/bin, but VS/data will not be updated because it is a separate, dependent module.
* Right mouse click on your "data" directory, under the top level ("VS" in this example) directory. Again choose "TourtoiseSVN->Update to revision..."
* Again type in the revision number, and hit OK. This will update everything under VS/data directory.

=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]]

Installation:Rlaan Weapons Platform

2011-10-06T21:56:20Z

Pheonixstorm: spam removal

[[Category:Database]] [[Category:Ships]] [[Category:VS Tech]]
{{NAV_Database |
| previous=FIXME
| up=[[Ships]]
| next=FIXME
}}
----

== Model and Texture Status ==

----

== Description ==

----

== Performance Statistics ==

Vegastrike

2011-10-06T21:47:48Z

Pheonixstorm: Spam removal

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

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956; 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|Player's Planet]]'''</center>
|style="background:#afa8ee;" width="50%"|<center>'''[[Development|Contributor's Station]]'''</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="color:#493956;"
|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|Information for new users]]
* [[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 the Vega Strike Engine
|}
|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>
'''''Want to contribute but don't know where to start'''''
* [[HowTo:Contribute|The Vega Strike Contributor's Guide]]
* [[Development]] & [[HowTos]] - Miscellaneous information for contributors
'''''For Artists and Modders'''''
* [[Development#Artistic_Contribution|Artists Guidelines]] - 3d models, space scapes, planet and station backgrounds, ...
* [[Development#Data_Modding|Modding Guidelines]] - config variables, missions, quests, modding tools, ...
* [[Artstyle_guides|Art Style Guides]] - VS universe style information for artists
'''''Engine References'''''
* [[DOCs]] - Engine documentation
'''''For Coders'''''
* [[Development#Code-related_Development|Coding Guidelines]] - dependencies, svn layout, code style, network protocol, ...
'''''Administrative'''''
* [[Vegastrike:Project|Project]] - Project information page
* [[Development:Roadmap|Roadmap]] - Vega Strike development plan
* [[Development#Status.2Ftask_list_pages|Status & Task List pages]]
* [[FAQ:Feature_Requests|Feature Requests]] - Ask, and you will have asked.
'''''Other'''''
* [[FAQ]]s - Frequently asked questions
* [[HowTos#Sourcecode HowTos|Sourcecode HowTos]] - Getting and installing the latest unstable version.
* [http://vegastrike.svn.sourceforge.net/viewvc/vegastrike/ Browse the SVN repository]

|}

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956;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:#7dcf7d;" width="50%"|<center>'''Wiki Trading Post'''</center>
|style="background:#ae6e9f;" width="50%"|<center>'''Help Shipyard'''</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]].
*[http://vegastrike.sourceforge.net/forums/viewtopic.php?f=21&t=13186 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)

Recommended open-source multi-protocol clients (IRC, ICQ/AIM, Jabber, Y!M, ...):
* Linux: [http://kopete.kde.org/ Kopete]
* Windows: [http://ayttm.sourceforge.net/ Ayttm]
* Mac: [http://fire.sourceforge.net/ Fire]
* [http://www.easyessayhelp.com/buy-essay.php buy an essay online]
|}

{| cellspacing="3" class="mainpagetable" align="center" style="color:#493956;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.
</center>
|}

----
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:VCPP Compiling

2010-12-16T16:43:01Z

Pheonixstorm: /* Compiling under Visual C++ */

{{NAV_Manual |
| previous=[[HowTo:Checkout SVN (Ubuntu Linux)|Checkout SVN (Ubuntu Linux)]]
| 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-vc</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-vc9</code> for all Visual C++ editions, <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) Deprecated
* <code>vegastrike/vega-vc7/</code> - The project files. (VISUAL C++ 7.x) Deprecated
* <code>vegastrike/vega-vc8/</code> - The project files. (VISUAL C++ 8.0) Deprecated
* <code>vegastrike/vega-vc9/</code> - The project files. (VISUAL C++ 9.0 and higher)
* <code>vegastrike/win32/</code> - The newer version of data. Until the change is made in the Vegastrike project setting binaries will be create in vega-vc9/Release or vega-vc9/Debug. <strike>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.</strike>

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++ 9.0 (2008 Express)==

This is likely only for Windows XP SP3 and Vista (so probably not Windows 2000). Apparently no Platform SDK is necessary. Note that it is required that the local file and directory structure is identical to the one on SVN. You need to checkout the following: <code>trunk/vegastrike</code>, <code>trunk/vega-vc9</code>, <code>trunk/win32</code>. If the above is wrong you will need to download the 2008 SDK or higher.

# [http://www.microsoft.com/express/download/ Download Visual C++ 2008 Express Edition].
# Make sure you are logged on as admin. Otherwise the VC++ 2008 EE installation will fail. 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.
# To update for Python 2.7 you will need to download the latest 2.7 release: [http://www.python.org/download/ Download latest Python 2.7]
# Compile Python using their <code>Python-2.7.1\PCbuild\pcbuild.sln</code> solution file. Make sure it works (<code>python.exe</code> starts up).
# Substitute the corresponding Python 2.7 files from <code>Python-2.7.1\PCbuild</code> and <code>Python-2.7.1\include</code>. Python also requires a <code>pyconfig.h</code> inside your <code>vega-vc9\include\python</code>, you can copy it from <code>Python-2.7.1\PC</code>.
# In VC++ 2008 EE, update the vegastrike project properties: in configuration properties -> linker -> input -> additional dependencies, change the python version to 2.7. (It should be the last one in the list.)
# Apply the <code>VCExpress.diff</code> to fix the resource file for use with Visual C++ Express.
# Vegastrike should now build normally.

==Visual C++ 8.0 (2005 Express)(deprecated)==
This is left here in case someone wants to attempt a working VC8 build
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 C++ 8.0(2005 Express) plus the Code::Blocks IDE (deprecated)==
You can download Visual C++ 8.0(2005 Express) after you acquired a vcsetup.exe for Visual C++ 8.0. These are still being offered on some download sites.
The main advantages of Visual C++ 8.0 over later versions are that it works for older OSes like Windows 2000 and that there is a vegastrike project file for it, which you can check out from svn as vega-vc8.
You will also need an SDK, I used the Platform SDK PSDK-x86.exe (1.3 MB) which you can find with the query “Windows Server 2003 Platform SDK Web” in a search engine.
You will need to enable internet explorer for a minute as the default browser to install the PSDK.
Also try to get the vcredist_x86.exe for Visual C++ 8.0(2005 Express) if you want to share your vegastrike binary with others.
You can acquire the code::block development environment from www.codeblocks.org.

You might want to make a copy of your SVN checkout tree now, to have a clean copy just in case of the code in VegaStrike/ and the project files in vega-vc8/
Start code::blocks, choose VC2005/2008 as default tool chain and import the .sln solution file from vega-vc8 into a workspace. Use the vc8 2005/2008 compiler.
Double click the vegastrike project so that it is selected in bold. Go to Project/Build options and add /EHsc to vegastrike in other compiler options, remove /W from all projects and choose a warning level you like instead for each compiling option, like /W1 for release and /W3 for a debug build.
I have only tried the Win32 and Win32 debug buildsYou will notice that the debug build sets other libraries in linker settings. Basically the left side of the settings is used to include libraries while the right side is used to NOT include the default libraries. Some people have reported that they need to add "/NODEFAULTLIB:libcmt" manually there to exclude libcmt from being linked which results in a conflict.(I also removed /ZI and added insted on the left side /Zi /D_DEBUG to have debug symbols, I'm not sure which is better).

You need to edit the file Resources.rc to read 
#include <WinResrc.h>
instead of 
#include "afxres.h"

If you should discover a problem with the PNG or Python libraries, or simply want to try out newer ones, recall that each of these libraries/dlls needs to be one built with the same compiler you use for vegastrike.
Be warned that for libpng-1.2.34 the optimized build does not work, while the debug build(without any optimization) works with the vc8 compiler.

You can also choose where the binaries you produced end up, but I left it to default settings which is in the ../win32/bin directory, thats right aside ../VegaStrike.
Finally I took the executable, which is named vegastrikeR.exe for the release version, and all other files produced and placed them into the directory structure of an old VegaStrike install.
Running vegaStrike produced errors, which meant I had to resolve them by checking out the directories bases,mission,programs,sounds/missions,techniques and textures directories from SVN using the repository browser. (I think you can even do without some of these.)
Copying the directories into and over the directory tree of the old install produced a working binary.
At least it works as far as I know - I didn't get to test much yet.

You can debug programs in the VC++ IDE by creating a new project and adding an executable as a subproject.

Enjoy!

==Visual Studio 7.x (deprecated)==

===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 (deprecated)===
''(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'''

==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)

=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:VCPP Compiling

2010-12-16T16:29:37Z

Pheonixstorm: /* Visual C++ 9.0 (2008 Express) */

{{NAV_Manual |
| previous=[[HowTo:Checkout SVN (Ubuntu Linux)|Checkout SVN (Ubuntu Linux)]]
| 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)==

This is likely only for Windows XP SP3 and Vista (so probably not Windows 2000). Apparently no Platform SDK is necessary. Note that it is required that the local file and directory structure is identical to the one on SVN. You need to checkout the following: <code>trunk/vegastrike</code>, <code>trunk/vega-vc9</code>, <code>trunk/win32</code>. If the above is wrong you will need to download the 2008 SDK or higher.

# [http://www.microsoft.com/express/download/ Download Visual C++ 2008 Express Edition].
# Make sure you are logged on as admin. Otherwise the VC++ 2008 EE installation will fail. 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.
# To update for Python 2.7 you will need to download the latest 2.7 release: [http://www.python.org/download/ Download latest Python 2.7]
# Compile Python using their <code>Python-2.7.1\PCbuild\pcbuild.sln</code> solution file. Make sure it works (<code>python.exe</code> starts up).
# Substitute the corresponding Python 2.7 files from <code>Python-2.7.1\PCbuild</code> and <code>Python-2.7.1\include</code>. Python also requires a <code>pyconfig.h</code> inside your <code>vega-vc9\include\python</code>, you can copy it from <code>Python-2.7.1\PC</code>.
# In VC++ 2008 EE, update the vegastrike project properties: in configuration properties -> linker -> input -> additional dependencies, change the python version to 2.7. (It should be the last one in the list.)
# Apply the <code>VCExpress.diff</code> to fix the resource file for use with Visual C++ Express.
# Vegastrike should now build normally.

==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 C++ 8.0(2005 Express) plus the Code::Blocks IDE==
You can download Visual C++ 8.0(2005 Express) after you acquired a vcsetup.exe for Visual C++ 8.0. These are still being offered on some download sites.
The main advantages of Visual C++ 8.0 over later versions are that it works for older OSes like Windows 2000 and that there is a vegastrike project file for it, which you can check out from svn as vega-vc8.
You will also need an SDK, I used the Platform SDK PSDK-x86.exe (1.3 MB) which you can find with the query “Windows Server 2003 Platform SDK Web” in a search engine.
You will need to enable internet explorer for a minute as the default browser to install the PSDK.
Also try to get the vcredist_x86.exe for Visual C++ 8.0(2005 Express) if you want to share your vegastrike binary with others.
You can acquire the code::block development environment from www.codeblocks.org.

You might want to make a copy of your SVN checkout tree now, to have a clean copy just in case of the code in VegaStrike/ and the project files in vega-vc8/
Start code::blocks, choose VC2005/2008 as default tool chain and import the .sln solution file from vega-vc8 into a workspace. Use the vc8 2005/2008 compiler.
Double click the vegastrike project so that it is selected in bold. Go to Project/Build options and add /EHsc to vegastrike in other compiler options, remove /W from all projects and choose a warning level you like instead for each compiling option, like /W1 for release and /W3 for a debug build.
I have only tried the Win32 and Win32 debug buildsYou will notice that the debug build sets other libraries in linker settings. Basically the left side of the settings is used to include libraries while the right side is used to NOT include the default libraries. Some people have reported that they need to add "/NODEFAULTLIB:libcmt" manually there to exclude libcmt from being linked which results in a conflict.(I also removed /ZI and added insted on the left side /Zi /D_DEBUG to have debug symbols, I'm not sure which is better).

You need to edit the file Resources.rc to read 
#include <WinResrc.h>
instead of 
#include "afxres.h"

If you should discover a problem with the PNG or Python libraries, or simply want to try out newer ones, recall that each of these libraries/dlls needs to be one built with the same compiler you use for vegastrike.
Be warned that for libpng-1.2.34 the optimized build does not work, while the debug build(without any optimization) works with the vc8 compiler.

You can also choose where the binaries you produced end up, but I left it to default settings which is in the ../win32/bin directory, thats right aside ../VegaStrike.
Finally I took the executable, which is named vegastrikeR.exe for the release version, and all other files produced and placed them into the directory structure of an old VegaStrike install.
Running vegaStrike produced errors, which meant I had to resolve them by checking out the directories bases,mission,programs,sounds/missions,techniques and textures directories from SVN using the repository browser. (I think you can even do without some of these.)
Copying the directories into and over the directory tree of the old install produced a working binary.
At least it works as far as I know - I didn't get to test much yet.

You can debug programs in the VC++ IDE by creating a new project and adding an executable as a subproject.

Enjoy!

==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]]