Talk:Main Page
From Gcbluewiki
Hi, Since Dewitt has been good enough to install the Wiki I thought I'd start by pitching in some ideas for an outline of the Wiki for discussion, so we can then get down to populating it with some text. Below is my first pass at a table of contents with some explanation. Because I've formatted this in wiki code between this intro and my explanation of the outline you'll see a table of contents preview which should also help us work out if the structure has any hope.
Since I'm new to GCB I don't pretend to have got this right, but we have to start someplace....so here goes!
Stryker 05:07, 18 June 2006 (PDT)
Contents |
GCBlue user reference
The content for this can be imported from the existing document as a starting point, with a troubleshooting section added where we can grab learnings from the issues raised in the forum.
Introduction
Summary of keyboard and mouse controls
In-game user interface
Airbase operations
Multiplayer
Tutorial scenarios
Error messages
Credits
Troubleshooting
GCBlue developer reference
This is really a place where all existing doc can first be centralised and anything as yet documented can be added. I don't know if Doxygen pages can be generated to Wiki format, but if not they can still be linked where appropriate.
Introduction
A peek under the hood to show an intro on the structure of the game. Also define any naming/style conventions to be used throughout here.
Python
Introduction
Introducing the integrated Boost interpreter, recommended editor etc.
Class reference
If Doxygen dox can be imported, else just include a link to the Doxygen pages in the Introduction, and through tutorial and leave this section out.
GCB scripting tutorial
Content drawn from existing site as starting text.
Game database
Introduction
A few words on what it contains, what it does, and the ability to plug in additional custom databases for scenarios.
Editing records
Note on using SQLite db browser or equivalent.
Database structure
Content drawn from existing database documentation as starting text.
3D engine
Introduction
Explaining what capabilities of OSG are used with links to further reading on that.
Writing a scenario
Introduction
Workflow for adding scenarios to GCB.
TBC
Since I've not done this perhaps Raven can flesh out the headings needed for this section in order to give a step by step guide.
Will give a wack at it... over time :o) - Raven58
Conceptualization
Before actually digging into writing a scenario in Python, it's advisable to map out the particulars of the scenario you want to create. This items include:
Location - the "WHERE". Where in the world is the scenario to take place.
Sides - Who's involved? Which countries (or groups) make up the opposing sides in the conflict.
Units - Which land, sea, and air units are to be employed, otherwise known as ORBAT - Order of Battle.
Story Line - The "WHY" and/or circumstances surrounding the conflict and the pre-battle briefing instructions for the sides involved.
Testing and troubleshooting
Common issues and how to fix them.
Creating platforms
Introduction
Workflow for adding platforms to GCB. Reference the available example (.3ds) models included with the game builds. Talk about the pre-requisite data required for creating a platform in the game, the tools used to create the model, and any guidelines on polygon count and maximum texture sizes.
Model requirements
Supported formats, orientation considerations for various 3d suites/formats.
XML wrapper & database entry
Explaining the supported tags and options and how they refer to the model itself. Where the file is referenced in the database.
Converting to OSG binary (.ive) format
Explaining the optional step, and any useful features of osgconv.exe
Testing and troubleshooting
Common issues and how to fix them.
