PioneerWiki - User contributions [en]

Commit access

2014-01-15T13:26:35Z

Jpab: Add section about changing git history

== What is commit access? ==

Having commit access means you have the ability to push code directly to the main Pioneer repository.

== How do I get commit access? ==

Usually, just by asking. If you're known to the other committers to be someone who can be trusted to be a good steward of the project (usually shown by the quality of previous contributions) then you'll be given access to push to the repository. This is deliberately a subjective measure, but rest assured, the bar is set pretty low. Its mostly just a check to make sure you aren't going to do something stupid.

In some circumstances you might be offered commit access. The same bar is set there. It usually happens when the other committers finds themselves thinking "this person would be a good committer".

== What do I need to know when pushing? ==

There's a few things that are special to the way we work that you need to know about.

=== Code style ===

We have a [[Code_style|code style guide]]. Learn it, love it. There's almost certainly something in there you'll hate, because we all have different opions on code style. Don't argue, just use it - its what we've got!

=== Code review ===

Read the page about the [[Code_review|code review process]]. You're expected to be reviewing your own code according to the guildlines set out there, and you're encouraged to find another person to review your code if its particularly large or complex. Read that page for more info about that.

There is no obligation for commiters to review other people's work, but it would be very helpful if you could. If everyone is involved, then the total workload on any individual remains small, giving everyone time to work on their code.

=== Update the changelog ===

[https://github.com/pioneerspacesim/pioneer/blob/master/Changelog.txt Changelog.txt] is where we track the history of the project. Each time you make a change, add a brief description of it to the Changelog. Include the Github issue or pull request number if it has one. The description should be something that is understandable by players. Choose an appropriate category, start a new month header at the start of the month, and preserve the existing formatting. Have a look through the history to get a feel for how it works.

=== Don't break the build ===

Pioneer is regularly built by an autobuild script, sometimes as often as once per day. This is done using the Makefile/autotools system (all platforms). You must take care to ensure that everything that lands on the master branch builds correctly with the autotools/GCC build. This could be a problem for Windows-based developers using MSVC; please do the best you can and ask for help if you need it.

=== Don't change existing git history ===

Once a commit is in the master repository, it must stay there: You must never force-push. That means, never use the -f or --force switch to the 'git push' command when you're pushing to the pioneerspacesim repository. If you're getting an error when you push, ask for help, because forcing things is a guaranteed way to break the repository for everyone.

Code review

2014-01-15T10:51:41Z

Jpab: /* When does it happen? */

== Why do code review? ==

Code review is simply getting someone to check your code before you it gets included in the Pioneer code proper to make sure that the code is of a good quality, is consistent with the rest of the codebase and takes Pioneer in the direction that the community wants it to go.

== When does it happen? ==

Code review can happen at any time, whenever you like. For small items of work it will get at least one review when it is submitted for inclusion (via a pull request). For a large development you may wish to find to someone to review your code periodically, to make sure you're on the right track. If you're starting to feel a bit unsure about what you're doing, that's probably a good time to ask someone!

You don't have to do this of course, but be aware that the reviewers don't particularly being asked to review hundreds or thousands of lines of code changes that appear out of nowhere. You face a good chance of having your code rejected outright or ignored completely, and that sucks. So if you're going to do something massive, at least check in at the start to make sure someone knows about it.

== Who can review code? ==

Anyone that wants to! Anyone can use the review tools on Github to read and comment on code while its under development or test pull requests.

In the case of a pull request, someone with commit access needs to do the final sign-off (typically, but not necessarily, at the same time as merging). If you don't have commit access you can still help make life easier for that person by leaving comments and working with the original submitter.

== I have commit access, does my code need to be reviewed? ==

No, you have commit access for a reason - you've proven that you can be trusted to be a good steward for the project. You should feel free to change whatever you want or need to, but as you do you should be considering all the points normally covered by a review. Self-review, if you like.

That said, no person is an island. Be sure to ask for help if you need it, even if its just a feeling that something isn't right.

== What gets reviewed? ==

Every single change is a candidate for review, no matter how small. Most review will happen in a pull request, but you can be reviewing code by reading the commit history or even by reading code as you're working on it.

Here are some good things to look out for:

* Bugs, logical errors, mathematical errors, typos (any simple, isolated code error). These are easy. If you find a bug during testing or by looking at the code, either fix it or tell the submitter to fix it. It's easy because everyone agrees that bugs need to be fixed.

* Uncertainty about some code logic or behaviour ("Is this maths right?" "Did the submitter intend this weird behaviour?"). These are easy: Ask the submitter (obviously). Explanatory comments are usually the "fix" here.

* Code style errors (braces, whitespace, naming conventions, etc). Same as bugs: fix it, or tell the submitter fix it. Not everyone agrees about the importance of code style, or perhaps even what style we should be using (particularly since the existing codebase is not totally consistent), but we have a code style guide and we want everything to conform to it. If there is some aspect of style not covered by the code style guide on the wiki, amend the guide and tell the submitter to fix their style. Yes, style is subjective, and it's not the submitter's fault that they didn't use the "correct" style, since it may not have been clear what was the "correct" style when they made the PR, but its not worth arguing about - the time and energy to discuss it costs more than just fixing the code.

* Messy git history. Fix it or ignore it. The trouble with telling the submitter to fix it is that many of our contributors don't have enough confidence wth git to do it right and the ones that do tend not to submit messy histories in the first place. So its not worth arguing about. Just do the best you can to keep your own history tidy, but if its not working out don't stress too much about. If you really need help, talk to someone that can drive Git well; they can help you out.

* Game design uncertainty ("Do we want this feature?", "Do we want it to behave this way?"). For the most part you should choose what you think is best. You should be paying attention to what the other developers and the players are asking for and be aware of what other developments are happening, and from there be able to make a reasonable decision. If you don't know, ask someone who does. But remember that you should not reject an idea simply because you prefer it a different way. Of course your opinion matters, but try to balance everyone's needs as much as possible. (This is hard. Please ask for help).

* Code structure problems ("We want the feature, but not implemented like this"). Structural problems can take a significant effort to fix and they make future code maintenance harder. They're the ones that often end up needing to be ripped out or rewritten later. The difficulty is that its often a ridiculous amount of effort to do something the "right" way, especially if it relates to a very old piece of code. The rule of thumb then is to permit mess if its necessary, but do the best you can to keep it contained. Remember that you're now adding to the cleanup work that someone else will have to do in the future.

Roadmap

2013-06-30T17:08:46Z

Jpab: add items about the bulletin board

== First milestone ==

Basically we want external interfaces to be stable.

* New save file format
* Separate Player from Ship (breaks Lua)
* Turn Missiles into guided Projectiles
* Lua equipment
* Module manifest
* Convert to new UI (but not redesigned HUD)
* JSON data files (ship defs)
* Starsystem generation rewrite (plus custom systems)

== Second milestone ==

Gameplay stuff, redesigned UI. Dunno yet.

== Older stuff ==

Pioneer version 1.0 will be the first "stable" release. This will not be the final state of the game: development will continue, particularly adding a lot more content and game-play features, but features present in version 1.0 are expected to be supported for a long time.

Things that must be done before we can release version 1.0:

'''''Warning:''' This list is incomplete - and under active discussion so subject to change''
=== Technical features ===
* The save system will be changed to allow future versions to be made without breaking all prior saved games.
* Equipment control will be moved to Lua.
* All user-interface will be converted to use the new-ui system and be driven by Lua.
* Star system generation will be rewritten to allow partially custom systems, and to allow some types of changes to be made without having knock-on effects through the entire galaxy or system.

=== Gameplay features ===
* Military progression / treason.
* Something like the Scout missions the walterar has done, exploration jobs.
* No hypersace from in atmosphere / or too close to a planet surface.
* In-system hyperspace jumps to make assassination missions and piracy actually possible.
* Alternatively a Fast-As-Light drive, Shadmar has taken a hacked one I (fluffyfreak) wrote and updated it for Paragon.

=== More proposed stuff ===

From [[User:Luomu|Luomu]] ([[User talk:Luomu|talk]]) 17:09, 1 May 2013 (PDT)

* New, fault tolerant save system: this is the most important thing ever
* Rewrite the HUD
** Gather a list of components before doing any visual design
* Controls
** New input system: do we need one, or can the current one be fixed?
** Current problems: conflicting binds, cannot bind multiple inputs per action
** Remove rarely used buttons?
* Camera
** Add chase camera, padlock
* Weapons
** goals: allow more than just laser bolts (beams, missiles), auto-tracking guns and turrets
** rewrite, basically
** turn missiles into guided projectiles instead of ships
** conflicts with lua trade goods/equipment?
* Star views and navigation
** combine system (orbit) view into star map
** maybe other streamlining as well?
** bookmarks, travel log
* Missions and station interface
** Redesign the bulletin board to allow filtering and searching (e.g., adverts have tags, as shown in this old mock-up: http://i.imgur.com/HJH9L.png)
** Centralise bulletin board within the station interface (ie, everything else hangs off the bulletin board; the BB is basically the station-wide-web)
** Replace the "standard" commodity market with multiple traders/shops advertising on the BB
** Replace the "standard" ship equipment and servicing screens with mechanics advertising on the BB
** Replace the "standard" ship purchase screen with specialist shops advertising on the BB, plus also individual pilots posting ship-for-sale and ship-wanted adverts
** Allow player to buy some types of ship equipment as cargo and have it fitted elsewhere
* Separate Player from Ships
** to enable shuttlecraft and remote drones
** must be done during alpha, not sensible afterwards (breaks modules)
* Hitpoints: use generic HP value instead of mass
* Cargo: use kg instead of tons
* AI
** needs more higher level stuff like basic self preservation, modules must not have to implement their own (like tradeships...)
** formations, anyone?
* Ship visual customization
* Space stations
** external docking
** traffic rules (don't allow modules to let ships idle forever)
* JSON for data files (ship defs etc)

Roadmap

2013-04-22T16:47:48Z

Jpab: Starting the roadmap

== Version 1.0 ==

Pioneer version 1.0 will be the first "stable" release. This will not be the final state of the game: development will continue, particularly adding a lot more content and game-play features, but features present in version 1.0 are expected to be supported for a long time.

Things that must be done before we can release version 1.0:

'''''Warning:''' This list is incomplete''

* The save system will be changed to allow future versions to be made without breaking all prior saved games.
* Equipment control will be moved to Lua.
* All user-interface will be converted to use the new-ui system and be driven by Lua.
* Star system generation will be rewritten to allow partially custom systems, and to allow some types of changes to be made without having knock-on effects through the entire galaxy or system.

Deneb

2013-03-01T13:27:55Z

Jpab: Add the Deneb Transport

{{Infobox_Ship
|name = Deneb Transport
|type = Freighter
|image =
|forward_thrust = 30e6
|reverse_thrust = 20e6
|up_thrust = 20e6
|down_thrust = 8e6
|left_thrust = 8e6
|right_thrust = 8e6
|angular_thrust = 30e6
|max_atmoshield = 1
|max_cargo = 235
|gun_mounts = 2
|max_laser = 1
|max_missile = 8
|max_engine = yes
|max_cargoscoop = 1
|max_fuelscoop = 1
|min_crew = 2
|max_crew = 3
|capacity = 235
|hull_mass = 100
|fuel_tank_mass = 100
|effective_exhaust_velocity = ???
|price = 430000
|hyperdrive_class = 3
}}

==Description==
The Deneb Transport is a medium capacity freighter. It's slow to turn, but its complement of missiles help to keep pirates at bay.

[[Category:Ships]]

Asset List

2013-02-19T03:17:20Z

Jpab: Fighter is done. Shuttle is in progress.

A list of models that we have/want/need in the core game.

== Ships ==

{| class="wikitable"
|-
!Type
!Purpose
!Model
!Status
|-
| Shuttle || Small shuttlecraft for in-system trips, package deliveries, etc. Not hyperspace-capable. || ip_shuttle || '''In progress''' [https://github.com/pioneerspacesim/pioneer/pull/2082 #2082]
|-
| Starter || Small multirole craft, capable of hyperspace and atmospheric flight. || natrix || '''Done''' [https://github.com/pioneerspacesim/pioneer/pull/2033 #2033]
|-
| Medium || Medium/large multirole craft, for cargo runs, exploration, etc. || lanner, wave || '''Done''' [https://github.com/pioneerspacesim/pioneer/pull/1957 #1957] [https://github.com/pioneerspacesim/pioneer/pull/2022 #2022]
|-
| Freighter || Large hyperspace-capable cargo ship || dsminer || '''Done''' [https://github.com/pioneerspacesim/pioneer/pull/2023 #2023]
|-
| Fighter || Small, fast short-range fighter, not hyperspace-capable. For use by police/pirates. || kanara || '''Done''' [https://github.com/pioneerspacesim/pioneer/pull/2037 #2037]
|-
| Bulk || Enormous supply ship, for positioning near stations (and later convoys etc). Non-playable || lrc, lynx || Needs to be replaced or converted from LMR
|}

== Stations ==

Surface and spacestations.

{| class="wikitable"
|-
!Type
!Purpose
!Model
!Status
|-
| Orbital || Ring-type space station with internal docking space for four ships. || big_crappy_spacestation || '''Done''' [https://github.com/pioneerspacesim/pioneer/pull/1964 #1964], updates in progress [https://github.com/pioneerspacesim/pioneer/pull/2046 #2046]
|-
| Surface || Open-air surface station with four 100x100m landing pads || ground_station_4 || Placeholder. Needs conversion from LMR or recreation. See [https://github.com/pioneerspacesim/pioneer/pull/1932 #1932]
|}

== Buildings ==

== Others ==

{| class="wikitable"
|-
!Type
!Purpose
|-
| Cargo container || A generic container, should be well visible
|-
| Gun || Ship weapon model, used for all types for now
|-
| Missile launcher || Weapon model attached to ships that carry missiles
|-
| Missile || Fired missile model, used for all types
|}

[[Category:Art]]

Creating Ships and Stations

2013-02-19T02:49:25Z

Jpab: Add stub for Station Properties section

Before a ship or station can appear in the game, you have to specify its properties.

== Ship Properties ==

Ship definitions live in data/ships. Each .lua file in this directory contains one ship definition. The file name (minus the .lua extension) is used as a unique identifier for the ship type (e.g., "wave"), so that code (e.g., mission scripts) can refer to a particular ship type. That identifier is case sensitive -- it is best to stick to the convention used for existing ships (all lower case, using underscores instead of spaces).

The easiest way to create a ship is to copy an existing ship definition and then edit it. The properties you can set (as of alpha 31) are:

define_ship {
-- Name of the ship shown to the player (e.g., in the shipyard)
name = "",

-- Name of the model used for the ship (minus the ".model" extension. This is case sensitive)
model = "",

-- Linear thruster power in Newtons
forward_thrust = 65e5,
reverse_thrust = 12e5,
up_thrust = 18e5,
down_thrust = 18e5,
left_thrust = 18e5,
right_thrust = 18e5,

-- Angular thruster power
-- This currently uses non-standard units, but is proportional to Newton-metres
-- It is best to find the right value by experimenting in-game
angular_thrust = 25e5,

-- Table of gun mount positions
-- note: in the future, gun positions will be specified as tag nodes in the model
gun_mounts =
{
{ v(0,-2,-46), v(0,0,-1), 5, 'HORIZONTAL' },
{ v(0,0,0), v(0,0,1), 5, 'HORIZONTAL' },
},

-- Equipment limits
-- Each type of item or equipment has a particular slot that it can fit into;
-- equipment can only be fitted if the ship has the right slot available,
-- and also has enough capacity to carry the extra mass
-- For most types of equipment, the slot limit should be set to
-- 0 (to disable that equipment) or 1 (to enable it)
-- Some types of equipment could have limits greater than 1 (e.g., cabins, shields)

-- note: in the future, these slots will change, because a new Lua-driven equipment
-- system is being created (see [https://github.com/pioneerspacesim/pioneer/pull/1719 github issue 1719])

max_cargo = 100, -- usually the same as the 'capacity' value
max_engine = 1, -- set to 0 to prevent fitting a hyperdrive
max_laser = 2, -- should be <= the number of gun mounts you have specified
max_missile = 4,
max_ecm = 1,
max_scanner = 1,
max_radarmapper = 1,
max_hypercloud = 1,
max_hullautorepair = 1,
max_energybooster = 1,
max_atmoshield = 1,
max_cabin = 2,
max_shield = 5,
max_fuelscoop = 1,
max_cargoscoop = 1,
max_lasercooler = 1,
max_cargolifesupport = 1,
max_autopilot = 1,

-- crew limits
-- note: in the future, the ship will not be able to launch with fewer than min_crew crew-members
min_crew = 1,
max_crew = 2,

-- total capacity (in tonnes)
capacity = 15,
-- mass of the empty hull (in tonnes)
hull_mass = 10,
-- size of the propellant tank (in tonnes)
fuel_tank_mass = 15,

-- Exhaust velocity Vc [m/s] is equivalent of engine efficiency and depend on used technology.
-- Higher Vc means lower fuel consumption. Smaller ships built for speed often mount engines
-- with higher Vc. Another way to make faster ship is to increase fuel_tank_mass.
effective_exhaust_velocity = 59167e3,

-- base price of a ship with just a hyperdrive
price = 70000,
-- base hyperdrive fitted as standard (set to 0 if the ship is not hyperspace capable)
hyperdrive_class = 0,
}

== Station Properties ==

'''To be written...'''

Note: The way that docking bays work is currently being improved. See [https://github.com/pioneerspacesim/pioneer/pull/2058 github issue 2058]

Creating Ships and Stations

2013-02-19T02:46:36Z

Jpab: Write up notes about ship definition properties

Pioneer Wiki

2013-02-19T02:04:00Z

Jpab: Add a link to the (not-yet-created) "Creating Ships and Stations" page

Pioneer is a space adventure game set in the milkyway galaxy at the turn of the 31st century. The game is open-ended, and you are free to explore the millions of star systems in the game. You can land on planets, slingshot past gas giants, and burn yourself to a crisp flying between binary star systems.
----
If you are new to pioneer you may want to know [[How to start| how to start]].

* [http://pioneerspacesim.net/download Download Pioneer] for Windows, Linux and Mac OSX

* [http://sourceforge.net/projects/pioneerspacesim/files/nightly/ Development Builds] (warning, may be more unstable than a release)

----

Please make this wiki nice. Add stuff about mods, dev, whatever. Be awesome! [[Getting started|How to get started]].

And write a nice front page and get rid of this, ok? :)

----
{|width=100%
|width="33%" style="background:#bbffbb; border:2px solid #99ee99; padding:2px 2px 4px 4px; vertical-align: top"|
===Community===
* [http://pioneerspacesim.net/ Pioneer Space Sim Homepage]
* [http://pioneerspacesim.net/forum Forums]
* [http://webchat.freenode.net/?channels=#pioneer Pioneer Space Sim on IRC]
* [http://pioneerspacesim.net/+ Pioneer Space Sim] on Google+
* [http://twitter.com/pioneerspacesim @pioneerspacesim] on Twitter
----
* [[Tutorials]]
* [[Keyboard and mouse controls]]
* [[FAQ]]
* [[Media Coverage]]

|width="33%" style="background:#fff9b1; border:2px solid #f0fe66; padding:2px 2px 4px 4px; vertical-align: top"|
===The Pioneer universe===
* [[Story]]
* [http://pioneerwiki.com/wiki/Category:Ships Ships] (work in progress)
|}

{|width=100%
|width="33%" style="background:#f0f0ff; border:2px solid #c6c9ff; padding:2px 2px 4px 4px; vertical-align: top"|

===Content Creation===
* [[Mods]]
* [[Introduction to Mission Scripting]]
** [[Interacting with the game: Event-based programming]]
** [[Interacting with the player: BBS forms]]
** [[Surviving a reload]]
* [http://eatenbyagrue.org/f/pioneer/codedoc/ Lua API Reference]
* Models
** [[Model system]]
** [[Model viewer]]
** [[Transitioning to the new model system]]
** Making models
*** [[Textures]]
*** [[Transparency]]
*** [[Optimising geometry]]
*** [[Stations]]
** [[3DS Max]]
** Blender
*** [[Blender Tips]]
*** [[UV coordinates in Blender]]
*** [[Asteroids and rocks in Blender]]
* [[Creating Ships and Stations]]
* [[Music]]
* [[Sound Effects]]
* [[Translations]]
* [[Licensing]]

|width="33%" style="background:#fff3e3; border:2px solid #ffc9c9; padding:2px 2px 4px 4px; vertical-align: top"|

===Development===
* [[Design Scope|Game Scope]]
* [[Getting Started with Development]]
** [[How to communicate]]
** [[Using git and GitHub]] (work in progress)
** [[Core Team]]
* [[Development Model]]
* [[Design_Workflow|Design and Project Management Workflow]]
* [https://github.com/pioneerspacesim/pioneer/issues Issue tracker]
|}

Pioneer is brung to you by a flock of [https://github.com/pioneerspacesim/pioneer/blob/master/AUTHORS.txt opensource beardy-weirdies], and is [http://www.gnu.org/licenses/gpl.html Free Software]

__NOTOC__

FAQ

2013-02-16T16:02:54Z

Jpab: /* Can I hire crew for my ship? */

=Frequently Asked Questions=
==What is Pioneer?==
Pioneer is a freeform single player space adventure in the spirit of [https://en.wikipedia.org/wiki/Frontier:_Elite_II Frontier: Elite II].

==Is this a game or a simulation?==
Frontier was a game, but with a newtonian flight model and a slightly more scientific flavour to the universe than usually in space games. Pioneer will follow this same path.

==Can I play online?==
There will be no multiplayer. This does not rule out the possibility of minor network features, but multiplayer as it is commonly known is not compatible with the core mechanics of Pioneer.

==Can I colonize planets, build space stations or conquer the universe?==
No, these are out of the game scope. While the game universe might not stay static for the duration of a game, the player can not generally influence major events.

==Can I walk around space stations and planets?==
No, you cannot exit your ship. The ship is always your avatar.

==Is the universe pre-defined or randomly generated?==
There are millions of stars in the galaxy. A few hundred on them are based on real-world astronomic catalogues. some of the planets (obvious ones being in the Sol system) are pre-defined, but most things are procedurally generated. This means that a planet does not exist until you actually visit it, but it will be generated the same way for every player.

==Can I hire crew for my ship?==
Yes. As of alpha 31, you can hire crew.

==Are savegames compatible between releases?==
While the game is still in alpha, this cannot be guaranteed. The situation will stabilize in a few years.

==Are savegames compatible between Mods?==
Again as with savegames between alpha versions, compatability between mods can not be guaranteed. It all depends on what mods you have installed.

==Where is star system X from Frontier? Can I buy ship Y?==
Pioneer is not an exact clone of Frontier. You will have to figure out new trade routes!

==How do I take screenshots?==
Ctrl+Printscreen saves .png files in the same directory where the game .ini and savegames are.

==Where is the configuration file, saved games, screenshots?==

* Windows: My Documents\Pioneer
* OS X: /Users/your_username/Library/Application Support/Pioneer
* Linux: /home/your_username/.pioneer

==Technical FAQ==

===I'm getting "ARB_vertex_buffer_object not supported" error on startup===
Your graphics card should support at least OpenGL 1.5 to run Pioneer in Legacy (non-shaders) mode. If your hardware is not hopelessly old, it could be just that the drivers supplied with your operating system are out of date.
* [http://www.nvidia.com/Drivers Nvidia]
* [http://support.amd.com/us/gpudownload/Pages/index.aspx AMD (ATI)]
* [http://downloadcenter.intel.com/ Intel]

===I'm getting graphical issues, such as wrong textures on the intro screen===
Try turning off "Use shaders" in the options screen. Try updating your drivers.

===The game freezes at the intro screen===
If you cannot start the game at all, edit the configuration file and change value DisableShaders to 1.

===My joystick is "drifting"===
The game has a deadzone setting, but it is only accessible through the configuration file. Open config.ini and raise the JoystickDeadzone value.

===I'm getting poor performance===
The heaviest part of the game is planetary terrain generation. Turn down the "Detail distance" and "Fractal detail" settings, they have the most impact for performance.

===I've enabled anti-aliasing in the config file, but it does not work===
Make sure the AA settings are not overridden by your graphics card settings, on NVidia AA should be set to "application controlled" mode.

===Full screen mode is incorrectly scaled===

If you are on Windows, try:

<pre>
Sounds like windows 7 desktop-scaling issues.
Try adding some compatability modes to the Pioneer.exe.
Right click it and Choose properties -> Compatability -> Tick
Disable desktop scaling, and Disable desktop composition.
</pre>

Asset List

2013-02-07T20:27:50Z

Jpab: /* Ships */

A list of models that we have/want/need in the core game.

== Ships ==

{| class="wikitable"
|-
!Type
!Purpose
!Model
!Status
|-
| Shuttle || Small shuttlecraft for in-system trips, package deliveries, etc. Not hyperspace-capable. || ip_shuttle || Needs to be replaced or converted from LMR
|-
| Starter || Small multirole craft, capable of hyperspace and atmospheric flight. || natrix || '''Done''' [https://github.com/pioneerspacesim/pioneer/pull/2033 #2033]
|-
| Medium || Medium/large multirole craft, for cargo runs, exploration, etc. || lanner, wave || '''Done''' [https://github.com/pioneerspacesim/pioneer/pull/1957 #1957] [https://github.com/pioneerspacesim/pioneer/pull/2022 #2022]
|-
| Freighter || Large hyperspace-capable cargo ship || dsminer || '''Done''' [https://github.com/pioneerspacesim/pioneer/pull/2023 #2023]
|-
| Fighter || Small, fast short-range fighter, not hyperspace-capable. For use by police/pirates. || talon? || Needs to be replaced or converted from LMR
|-
| Bulk || Enormous supply ship, for positioning near stations (and later convoys etc). Non-playable || lrc, lynx || Needs to be replaced or converted from LMR
|}

== Stations ==

Surface and spacestations.

{| class="wikitable"
|-
!Type
!Purpose
!Model
!Status
|-
| Orbital || Ring-type space station with internal docking space for four ships. || big_crappy_spacestation || '''Done''' [https://github.com/pioneerspacesim/pioneer/pull/1964 #1964]
|-
| Surface || Open-air surface station with four 100x100m landing pads || ground_station_4 || Placeholder. Needs conversion from LMR or recreation. See [https://github.com/pioneerspacesim/pioneer/pull/1932 #1932]
|}

== Buildings ==

== Others ==

{| class="wikitable"
|-
!Type
!Purpose
|-
| Cargo container || A generic container, should be well visible
|-
| Gun || Ship weapon model, used for all types for now
|-
| Missile launcher || Weapon model attached to ships that carry missiles
|-
| Missile || Fired missile model, used for all types
|}

[[Category:Art]]

Getting Started with Development

2013-01-25T13:38:02Z

Jpab: /* Getting the Code */

==Getting the Code==
Pioneer is managed using Git, and is stored on [http://github.com Github]. The [http://github.com/pioneerspacesim/pioneer official repository] is the best one to get. To get it:

git clone git://github.com/pioneerspacesim/pioneer.git

This will get you on the "master" branch, which is where new code is merged. This is the latest and greatest development and is quite unstable. To build a specific alpha, you need to checkout the appropriate release tag:

git checkout alpha30

You may also need to clone the [https://github.com/pioneerspacesim/pioneer-thirdparty pioneer-thirdparty] repository, depending on what platform you're on. It is needed to build on Windows. You should clone this in a directory ''next to'' your clone of the pioneer directory (''not'' a sub-directory). Further instructions are in the COMPILING.txt file (linked below).

==Compiling==

There are instructions for how to compile the code included in the repository:

[https://github.com/pioneerspacesim/pioneer/blob/master/COMPILING.txt COMPILING.txt]

===Debugging===

For developers on Linux, gdb can be used for debugging

gdb ./src/pioneer
run

Bugs, and feature requests, should be logged on the issue tracker.

Getting Started with Development

2013-01-25T13:33:47Z

Jpab: Scrap notes about how to build; point to COMPILING.txt in the repository instead

Blender Tips

2013-01-22T14:53:13Z

Jpab: "in easily groups for easy control"!

= Blender's UI =

Some things to keep in mind when using Blender:

* Do check the [http://wiki.blender.org/index.php/Doc:2.6/Manual Blender Manual]. It's not complete, but there ''is'' a lot of stuff in there.
* Always have one hand on the keyboard and one hand on the mouse. Blender has lots of keyboard shortcuts, but you'll want to use the mouse to move the view around and position/scale/rotate things.
* Most things in Blender are context sensitive, and that context includes: What is selected? Are you in edit mode? What window is the mouse cursor in? The last of those can be confusing, but it works as long as you stick to the golden rule of having one hand on the keyboard and one hand on the mouse (and it's necessary so that the keyboard shortcuts can be used efficiently). Operations that aren't available in the current context will typically not be shown at all, for example if you use the "Space Menu" when you're not in edit mode, then "Remove Doubles" (which is a mesh edit operation and therefore only works in edit mode) won't be listed at all.
* The middle mouse button controls the view in all windows. That means it also works as a way of scrolling control panels (you can drag them with the middle mouse button or use the scroll wheel), scrolling window headers (you can drag them with the middle mouse button or use the scroll wheel), dragging curve editors, and so on.

=== Selection and Simple Editing ===

Basic controls that work in several places (e.g., 3D view, animation curve editor, UV map editor) include:

* "Select All"/"Deselect All". 'A' key. If there is anything selected, this will deselect everything. If there is nothing selected, it will select everything. Extremely useful!
* "Grab". 'G' key. For moving things around.
* "Delete". 'X' key.
* "Toggle Edit Mode". Tab key.
* "Space Menu". Space key. Most things can be done through this menu; just open it and start typing the name of an operation (e.g., "Remove Doubles", or just "Doubles").

And probably a load more.

= Object Management =

=== Layers ===

Use Blender's layers to keep your objects in groups for easy control of selection and visibility. For example, the Lanner uses separate layers for:

# High detail static mesh
# High detail landing gear components (the animated bits)
# Medium/low detail static mesh & landing gear
# Collision mesh
# Thruster and navigation light tag nodes
# Decal meshes and label tag nodes
# Blender lamp & camera objects (you could just delete these, but they're needed if you want to make renders of the object outside the game)

The "select all" toggle ('A' key) only works on the selectable objects on currently enabled layers. So, when exporting the objects I use turn on a different combination of layers for different purposes. For the high LOD I turn on the high detail layers and the tag layers. For medium/low LOD I turn on the medium detail layer and the thruster/light tag layer (but leave decals & labels off). For the collision mesh I just turn on the collision layer.

[[File:blender-layer-controls.png]]

=== Visibility & Selectability ===

The 'H' key hides currently selected objects. Alt-H unhides everything on the currently enabled layers. You can also control visibility for each object with the 'eye' icon in the Outliner window.

Selectability is useful too. This is controlled with the 'mouse cursor' icon in the Outliner window. In the Lanner, I have actual Blender text nodes attached to my label tag objects, so that I can get a better idea of where the text will go (actually this doesn't work great yet because the text in game is centered vertically on the node I think). I turn off selectability for the text objects, which lets me use the "select all" toggle to select everything for export while still excluding the text.

[[File:blender-outliner-visibility-selectability.png]]

= Meshing Tips =

=== Mesh Modifier: Mirror ===

Lots of things you might want to model are symmetrical. There's no point doubling the work you have to do by modelling both halves separately, or awkwardly using manual duplicate & mirror operations to cope with this. Instead, just turn on the mirror modifier. You usually want to mirror the X axis, and have "Merge" turned on (so that vertices on the centre-line aren't duplicated).

Here is the Lanner's mesh in edit mode. Note that only half of it exists. The other half is being maintained by the mirror modifier.

[[File:lanner-half-mesh.png]]

Here are the mirror modifier controls:

[[File:blender-mirror-modifier.png]]

=== Mesh Modifier: Edge Split ===

The way the model responds to lighting depends on the surface normal. The surface normal is the direction that the surface is facing. A surface facing directly towards a light will be bright; a surface at a glancing angle to a light will be dim. The surface normal that Pioneer uses comes from the mesh data, but it doesn't actually come from the faces, it comes from the ''vertices''. For a particular point in a triangle, the normal used for lighting is calculated by interpolating from the normals that are taken from the three vertices of the triangle. This is useful for curved surfaces, because although the triangle itself is flat, the interpolation of the normals makes the surface look like it's curved because the shading is right. However, it means that where two triangles meet, they have the same normal for lighting, which means that even if they're at a sharp angle (not just an internal edge of a curved surface) the lighting will make it look like it's not a sharp edge.

Here is part of the Lanner, with really weird lighting caused by having a sharp edge that shares normals.

[[File:lanner-sharp-edge-incorrect-lighting.png]]

And here is what it's supposed to look like:

[[File:lanner-sharp-edge-lighting.png]]

One way to achieve this is to duplicate the vertices along each sharp edge, so that the two sides of the edge can use different normals (note: this is what the "Rip" tool does). But that's a massive pain to edit and maintain because then if you want to reposition one of those vertices or change its UV coordinates, you have to make sure you move both copies at the same time, and for corners that connect more than one sharp edge you get even more duplicates.

The right way to do it is to use the "Edge Split" modifier. Edge Split does the same duplication of vertices that you can do by hand, but because it's a modifier you can just turn it on and it will manage the duplicates for you. Edge Split needs some way to decide which edges are supposed to be "sharp" so that it ''only'' duplicates vertices on the sharp edges. It has two ways of deciding whether an edge is sharp: you can give it an angle threshold, so all edges greater than the specified angle will be sharp, or you can mark edges manually. Here is the control panel for Edge Split:

[[File:blender-edge-split-modifier.png]]

In this case, I've used a high threshold to avoid making too many edges sharp, and I've marked some edges manually as well. Here the manually marked edges are shown in blue:

[[File:lanner-mesh-sharp-edges.png]]

To mark edges as sharp, select them in edit mode and use the "Mark Sharp" tool (type it in the "Space Menu"). The tool is a little confusing, because it has a mode toggle: in one mode it marks edges as sharp, in the other mode it ''clears'' the marks. So, first select the edges you want to (un)mark, then use the tool, and then if necessary toggle the check-box marked "Clear" in the tool controls panel.

'''Note:''' The tool controls panel is at the bottom of the 3D view tool panel, which can be toggled with the 'T' key.

Blender Tips

2013-01-21T18:35:58Z

Jpab: /* Mesh Modifier: Edge Split */

= Blender's UI =

Some things to keep in mind when using Blender:

* Do check the [http://wiki.blender.org/index.php/Doc:2.6/Manual Blender Manual]. It's not complete, but there ''is'' a lot of stuff in there.
* Always have one hand on the keyboard and one hand on the mouse. Blender has lots of keyboard shortcuts, but you'll want to use the mouse to move the view around and position/scale/rotate things.
* Most things in Blender are context sensitive, and that context includes: What is selected? Are you in edit mode? What window is the mouse cursor in? The last of those can be confusing, but it works as long as you stick to the golden rule of having one hand on the keyboard and one hand on the mouse (and it's necessary so that the keyboard shortcuts can be used efficiently). Operations that aren't available in the current context will typically not be shown at all, for example if you use the "Space Menu" when you're not in edit mode, then "Remove Doubles" (which is a mesh edit operation and therefore only works in edit mode) won't be listed at all.
* The middle mouse button controls the view in all windows. That means it also works as a way of scrolling control panels (you can drag them with the middle mouse button or use the scroll wheel), scrolling window headers (you can drag them with the middle mouse button or use the scroll wheel), dragging curve editors, and so on.

=== Selection and Simple Editing ===

Basic controls that work in several places (e.g., 3D view, animation curve editor, UV map editor) include:

* "Select All"/"Deselect All". 'A' key. If there is anything selected, this will deselect everything. If there is nothing selected, it will select everything. Extremely useful!
* "Grab". 'G' key. For moving things around.
* "Delete". 'X' key.
* "Toggle Edit Mode". Tab key.
* "Space Menu". Space key. Most things can be done through this menu; just open it and start typing the name of an operation (e.g., "Remove Doubles", or just "Doubles").

And probably a load more.

= Object Management =

=== Layers ===

Use Blender's layers to keep your objects in easily groups for easy control of selection and visibility. For example, the Lanner uses separate layers for:

# High detail static mesh
# High detail landing gear components (the animated bits)
# Medium/low detail static mesh & landing gear
# Collision mesh
# Thruster and navigation light tag nodes
# Decal meshes and label tag nodes
# Blender lamp & camera objects (you could just delete these, but they're needed if you want to make renders of the object outside the game)

The "select all" toggle ('A' key) only works on the selectable objects on currently enabled layers. So, when exporting the objects I use turn on a different combination of layers for different purposes. For the high LOD I turn on the high detail layers and the tag layers. For medium/low LOD I turn on the medium detail layer and the thruster/light tag layer (but leave decals & labels off). For the collision mesh I just turn on the collision layer.

[[File:blender-layer-controls.png]]

=== Visibility & Selectability ===

The 'H' key hides currently selected objects. Alt-H unhides everything on the currently enabled layers. You can also control visibility for each object with the 'eye' icon in the Outliner window.

Selectability is useful too. This is controlled with the 'mouse cursor' icon in the Outliner window. In the Lanner, I have actual Blender text nodes attached to my label tag objects, so that I can get a better idea of where the text will go (actually this doesn't work great yet because the text in game is centered vertically on the node I think). I turn off selectability for the text objects, which lets me use the "select all" toggle to select everything for export while still excluding the text.

[[File:blender-outliner-visibility-selectability.png]]

= Meshing Tips =

=== Mesh Modifier: Mirror ===

Lots of things you might want to model are symmetrical. There's no point doubling the work you have to do by modelling both halves separately, or awkwardly using manual duplicate & mirror operations to cope with this. Instead, just turn on the mirror modifier. You usually want to mirror the X axis, and have "Merge" turned on (so that vertices on the centre-line aren't duplicated).

Here is the Lanner's mesh in edit mode. Note that only half of it exists. The other half is being maintained by the mirror modifier.

[[File:lanner-half-mesh.png]]

Here are the mirror modifier controls:

[[File:blender-mirror-modifier.png]]

=== Mesh Modifier: Edge Split ===

The way the model responds to lighting depends on the surface normal. The surface normal is the direction that the surface is facing. A surface facing directly towards a light will be bright; a surface at a glancing angle to a light will be dim. The surface normal that Pioneer uses comes from the mesh data, but it doesn't actually come from the faces, it comes from the ''vertices''. For a particular point in a triangle, the normal used for lighting is calculated by interpolating from the normals that are taken from the three vertices of the triangle. This is useful for curved surfaces, because although the triangle itself is flat, the interpolation of the normals makes the surface look like it's curved because the shading is right. However, it means that where two triangles meet, they have the same normal for lighting, which means that even if they're at a sharp angle (not just an internal edge of a curved surface) the lighting will make it look like it's not a sharp edge.

Here is part of the Lanner, with really weird lighting caused by having a sharp edge that shares normals.

[[File:lanner-sharp-edge-incorrect-lighting.png]]

And here is what it's supposed to look like:

[[File:lanner-sharp-edge-lighting.png]]

One way to achieve this is to duplicate the vertices along each sharp edge, so that the two sides of the edge can use different normals (note: this is what the "Rip" tool does). But that's a massive pain to edit and maintain because then if you want to reposition one of those vertices or change its UV coordinates, you have to make sure you move both copies at the same time, and for corners that connect more than one sharp edge you get even more duplicates.

The right way to do it is to use the "Edge Split" modifier. Edge Split does the same duplication of vertices that you can do by hand, but because it's a modifier you can just turn it on and it will manage the duplicates for you. Edge Split needs some way to decide which edges are supposed to be "sharp" so that it ''only'' duplicates vertices on the sharp edges. It has two ways of deciding whether an edge is sharp: you can give it an angle threshold, so all edges greater than the specified angle will be sharp, or you can mark edges manually. Here is the control panel for Edge Split:

[[File:blender-edge-split-modifier.png]]

In this case, I've used a high threshold to avoid making too many edges sharp, and I've marked some edges manually as well. Here the manually marked edges are shown in blue:

[[File:lanner-mesh-sharp-edges.png]]

To mark edges as sharp, select them in edit mode and use the "Mark Sharp" tool (type it in the "Space Menu"). The tool is a little confusing, because it has a mode toggle: in one mode it marks edges as sharp, in the other mode it ''clears'' the marks. So, first select the edges you want to (un)mark, then use the tool, and then if necessary toggle the check-box marked "Clear" in the tool controls panel.

'''Note:''' The tool controls panel is at the bottom of the 3D view tool panel, which can be toggled with the 'T' key.

Blender Tips

2013-01-21T17:44:53Z

Jpab: Write out some tips for using Blender

= Blender's UI =

Some things to keep in mind when using Blender:

* Do check the [http://wiki.blender.org/index.php/Doc:2.6/Manual Blender Manual]. It's not complete, but there ''is'' a lot of stuff in there.
* Always have one hand on the keyboard and one hand on the mouse. Blender has lots of keyboard shortcuts, but you'll want to use the mouse to move the view around and position/scale/rotate things.
* Most things in Blender are context sensitive, and that context includes: What is selected? Are you in edit mode? What window is the mouse cursor in? The last of those can be confusing, but it works as long as you stick to the golden rule of having one hand on the keyboard and one hand on the mouse (and it's necessary so that the keyboard shortcuts can be used efficiently). Operations that aren't available in the current context will typically not be shown at all, for example if you use the "Space Menu" when you're not in edit mode, then "Remove Doubles" (which is a mesh edit operation and therefore only works in edit mode) won't be listed at all.
* The middle mouse button controls the view in all windows. That means it also works as a way of scrolling control panels (you can drag them with the middle mouse button or use the scroll wheel), scrolling window headers (you can drag them with the middle mouse button or use the scroll wheel), dragging curve editors, and so on.

=== Selection and Simple Editing ===

Basic controls that work in several places (e.g., 3D view, animation curve editor, UV map editor) include:

* "Select All"/"Deselect All". 'A' key. If there is anything selected, this will deselect everything. If there is nothing selected, it will select everything. Extremely useful!
* "Grab". 'G' key. For moving things around.
* "Delete". 'X' key.
* "Toggle Edit Mode". Tab key.
* "Space Menu". Space key. Most things can be done through this menu; just open it and start typing the name of an operation (e.g., "Remove Doubles", or just "Doubles").

And probably a load more.

= Object Management =

=== Layers ===

Use Blender's layers to keep your objects in easily groups for easy control of selection and visibility. For example, the Lanner uses separate layers for:

# High detail static mesh
# High detail landing gear components (the animated bits)
# Medium/low detail static mesh & landing gear
# Collision mesh
# Thruster and navigation light tag nodes
# Decal meshes and label tag nodes
# Blender lamp & camera objects (you could just delete these, but they're needed if you want to make renders of the object outside the game)

The "select all" toggle ('A' key) only works on the selectable objects on currently enabled layers. So, when exporting the objects I use turn on a different combination of layers for different purposes. For the high LOD I turn on the high detail layers and the tag layers. For medium/low LOD I turn on the medium detail layer and the thruster/light tag layer (but leave decals & labels off). For the collision mesh I just turn on the collision layer.

[[File:blender-layer-controls.png]]

=== Visibility & Selectability ===

The 'H' key hides currently selected objects. Alt-H unhides everything on the currently enabled layers. You can also control visibility for each object with the 'eye' icon in the Outliner window.

Selectability is useful too. This is controlled with the 'mouse cursor' icon in the Outliner window. In the Lanner, I have actual Blender text nodes attached to my label tag objects, so that I can get a better idea of where the text will go (actually this doesn't work great yet because the text in game is centered vertically on the node I think). I turn off selectability for the text objects, which lets me use the "select all" toggle to select everything for export while still excluding the text.

[[File:blender-outliner-visibility-selectability.png]]

= Meshing Tips =

=== Mesh Modifier: Mirror ===

Lots of things you might want to model are symmetrical. There's no point doubling the work you have to do by modelling both halves separately, or awkwardly using manual duplicate & mirror operations to cope with this. Instead, just turn on the mirror modifier. You usually want to mirror the X axis, and have "Merge" turned on (so that vertices on the centre-line aren't duplicated).

Here is the Lanner's mesh in edit mode. Note that only half of it exists. The other half is being maintained by the mirror modifier.

[[File:lanner-half-mesh.png]]

Here are the mirror modifier controls:

[[File:blender-mirror-modifier.png]]

=== Mesh Modifier: Edge Split ===

The way the model responds to lighting depends on the surface normal. The surface normal is the direction that the surface is facing. A surface facing directly towards a light will be bright; a surface at a glancing angle to a light will be dim. The surface normal that Pioneer uses comes from the mesh data, but it doesn't actually come from the faces, it comes from the ''vertices''. For a particular point in a triangle, the normal used for lighting is calculated by interpolating from the normals that are taken from the three vertices of the triangle. This is useful for curved surfaces, because although the triangle itself is flat, the interpolation of the normals makes the surface look like it's curved because the shading is right. However, it means that where two triangles meet, they have the same normal for lighting, which means that even if they're at a sharp angle (not just an internal edge of a curved surface) the lighting will make it look like it's not a sharp edge.

Here is part of the Lanner, with really weird lighting caused by having a sharp edge that shares normals.

[[File:lanner-sharp-edge-incorrect-lighting.png]]

And here is what it's supposed to look like:

[[File:lanner-sharp-edge-lighting.png]]

One way to achieve this is to duplicate the vertices along each sharp edge, so that the two sides of the edge can use different normals (note: this is what the "Rip" tool does). But that's a massive pain to edit and maintain because then if you want to reposition one of those vertices or change its UV coordinates, you have to make sure you move both copies at the same time, and for corners that connect more than one sharp edge you get even more duplicates.

The right way to do it is to use the "Edge Split" modifier. Edge Split does the same duplication of vertices that you can do by hand, but because it's a modifier you can just turn it on and it will manage the duplicates for you. Edge Split needs some way to decide which edges are supposed to be "sharp" so that it ''only'' duplicates vertices on the sharp edges. It has two ways of deciding whether an edge is sharp: you can give it an angle threshold, so all edges greater than the specified angle will be sharp, or you can mark edges manually. Here is the control panel for Edge Split:

[[File:blender-edge-split-modifier.png]]

In this case, I've used a high threshold to avoid making too many edges sharp, and I've marked some edges manually as well. Here the manually marked edges are shown in blue:

[[File:lanner-mesh-sharp-edges.png]]

To mark edges as sharp, select them in edit mode and use the "Mark Sharp" tool (type it in the "Space Menu"). The tool is a little confusing, because it has a mode toggle: in one mode it marks edges as sharp, in the other mode it ''clears'' the marks. So, first select the edges you want to (un)mark and then if necessary toggle the check-box marked "Clear" in the tool controls panel.

'''Note:''' The tool controls panel is at the bottom of the 3D view tool panel, which can be toggled with the 'T' key.

File:Lanner-sharp-edge-incorrect-lighting.png

2013-01-21T17:24:43Z

Jpab:

File:Lanner-sharp-edge-lighting.png

2013-01-21T17:24:28Z

Jpab:

File:Blender-edge-split-modifier.png

2013-01-21T17:14:44Z

Jpab:

File:Lanner-mesh-sharp-edges.png

2013-01-21T17:14:20Z

Jpab:

File:Blender-mirror-modifier.png

2013-01-21T17:13:59Z

Jpab:

File:Lanner-half-mesh.png

2013-01-21T17:13:45Z

Jpab:

File:Blender-outliner-visibility-selectability.png

2013-01-21T16:38:42Z

Jpab:

File:Blender-layer-controls.png

2013-01-21T16:38:27Z

Jpab:

Pioneer Wiki

2013-01-21T16:15:03Z

Jpab: Add a Blender Tips item

Pioneer is a space adventure game set in the milkyway galaxy at the turn of the 31st century. The game is open-ended, and you are free to explore the millions of star systems in the game. You can land on planets, slingshot past gas giants, and burn yourself to a crisp flying between binary star systems.

* [http://pioneerspacesim.net/download Download Pioneer] for Windows, Linux and Mac OSX

* [http://sourceforge.net/projects/pioneerspacesim/files/nightly/ Development Builds] (warning, may be more unstable than a release)

----

Please make this wiki nice. Add stuff about mods, dev, whatever. Be awesome! [[Getting started|How to get started]].

And write a nice front page and get rid of this, ok? :)

----
{|width=100%
|width="33%" style="background:#bbffbb; border:2px solid #99ee99; padding:2px 2px 4px 4px; vertical-align: top"|
===Community===
* [http://pioneerspacesim.net/ Pioneer Space Sim Homepage]
* [http://pioneerspacesim.net/forum Forums]
* [[FAQ]]
* [[Keyboard and mouse controls]]
* [http://twitter.com/pioneerspacesim @pioneerspacesim] on Twitter
* [[Media Coverage]]
* [[Tutorials]]
|width="33%" style="background:#f0f0ff; border:2px solid #c6c9ff; padding:2px 2px 4px 4px; vertical-align: top"|

===Content Creation===
* [[Mods]]
* [[Introduction to Mission Scripting]]
** [[Interacting with the game: Event-based programming]]
** [[Interacting with the player: BBS forms]]
** [[Surviving a reload]]
* [http://eatenbyagrue.org/f/pioneer/codedoc/ Lua API Reference]
* Modeling
** [[Model system]]
** [[Model viewer]]
** [[Transitioning to the new model system]]
** [[3DS Max]]
** Creating Models with Blender
*** [[Blender Tips]]
*** [[UV coordinates in Blender]]
* [[Music]]
* [[Sound Effects]]
* [[Translations]]
|width="33%" style="background:#fff3f3; border:2px solid #ffc9c9; padding:2px 2px 4px 4px; vertical-align: top"|

===Development===
* [[Design Scope|Game Scope]]
* [[Getting Started with Development]]
** [[Using git and GitHub]] (work in progress)
** [[Core Team]]
* [[Development Model]]
* [[Design_Workflow|Design and Project Management Workflow]]
* [https://github.com/pioneerspacesim/pioneer/issues Issue tracker]
|}

Pioneer is brought to you by a flock of [https://github.com/pioneerspacesim/pioneer/blob/master/AUTHORS.txt opensource beardy-weirdies], and is [http://www.gnu.org/licenses/gpl.html Free Software]

Model viewer

2013-01-20T14:47:52Z

Jpab: Expand notes about starting the model viewer a little for clarity

= Starting the Model Viewer =

=== Windows ===

Create a shortcut to pioneer.exe. Edit shortcut properties, and add " -mv" to the end of the Target box, so that the whole Target is something like:

C:\Users\jpab\pioneer\Pioneer.exe -mv

Then you can run the model viewer by using the shortcut.

Or use the command line (like Linux)

=== OS X ===

Hold down the Option key while clicking on the pioneer.app icon to launch the model viewer instead of the game.

Or use the command line (like Linux)

=== Linux ===

Pass the "-mv" flag when running the game:

pioneer -mv <optional model name>

= Hotkeys =

Esc: Quit

Tab: Toggle UI

PrintScr: Screenshot

Space: Reset camera view + thruster sliders

G: Cycle grid mode

R: Randomize colour sliders

Z: Toggle wireframe mode

Camera view presets are like Blender:

* Numpad 1 - Front view
* Ctrl+Numpad - Rear view
* Numpad 3 - Right view
* Ctrl+Numpad 3 - Left view
* Numpad 7 - Top view
* Ctrl+Numpad 7 - Bottom view
* Numpad2/4/6/8: Rotate view

[[Category:Art]]

Github Wiki Migration

2012-11-09T13:38:40Z

Jpab: add Idea.Network-features, which was missing from the list

Page checklist from the old wiki: https://github.com/pioneerspacesim/pioneer/wiki/_pages

See a red link? Convert the page! Compare with [[Special:AllPages]] if you think the content might already exist under another name.

* [[Blender Model Export]]
* [[Ship AI]]
* [[Coding Conventions]]
* [[Compiling]]
* [[Custom Systems]]
* [[Design]] (index page)
** [[Design Process]]
* [[Design Scope]]
* [[Development Model]]
* [[Active Discussions]] (index page)
** [[Discussion Storyline, Background, Narrative]]
** [[Discussion Celebrities]]
** [[Discussion FTL Jumps]]
** [[Discussion Input System]]
** [[Discussion Model System Overhaul]]
** [[Discussion Modelling Guidelines]]
** [[Discussion Planetary System Information]]
** [[Discussion Political Entitites]]
** [[Discussion Sysgen and Custom Systems]]
** [[Discussion Timeline]]
* [[Pioneer UI]]
* [[FAQ]]
* [[Game Data]]
* [[Getting Started with Development]]
* [[Ideas and Requests]] (Index page)
** [[Idea Crew]]
** [[Idea Escape Capsules]]
** [[Idea Power Use in Ships]]
** [[Idea Space Only Ships]]
** [[Idea Network features]]
* [[Introduction to Mission Scripting]]
* [[Lua Module Tutorial]]
* [[Lua Scripting]]
* [[Missions and NPC Interaction]]
* [[Modding]]
* [[Modelling]]
* [[Music]]
* [[Planet Heightmaps]]
* [[Roadmap]]
* [[Sound Effects]]
* [[Story]]
* [[Translations]]

Pioneer Wiki

2012-10-17T17:56:56Z

Jpab: