The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
|
|
Welcome to the developer portal
|
|
|
Please visit our forum if you cannot find what you're looking for.
|
|
|
Get involved!
|
If you would like to help with FlightGear's development, it's a good idea to subscribe yourself to the FlightGear development mailing list. Use the list or the FlightGear issue tracker to get in touch with fellow FlightGear core developers.
Visit Category:Core development projects to see a list of currently ongoing projects!
See Category:Developer Plans to see a list of developer plans for the upcoming release.
See request for comments for a list of long-standing issues and challenges affecting FlightGear's evolution and overall development progress (admittedly a little outdated meanwhile).
Help needed: SimGear 2.11+ now has experimental support for a libsvn replacement, people building from source are encouraged to help with testing and debugging this new feature:
|
First, I need some help; for people to rebuild simgear with -DSG_SVN_CLIENT=1, and mv / erase their TerraSync dir. Then simply run FGFS as normal, as if you were starting on a new machine / account with no previous use of TerraSync.[1]
— James Turner
|
|
|
So, as I've previously asked before, I really need people running from 'next'
to try with -DSG_SVN_CLIENT=1 when configuring SimGear, move their existing
TerraSync dir out the way, and test, test, test. I'm sure the new code isn't
100% trouble free (in particular I think there is still the occasional time
when it gets stuck not doing any more downloads until FG is restarted), but I
really don't want to move forwards with the code until I have a bit more
assurance it's not going to make everyone's setup crash 80% of the time, which
is what some people have reported.
Note this applies even if you 'don't use' terrasync since the SVN sync engine
is going to be used for other pieces of data as soon as it's stable. (I will be
adding a new preference to globally control whether FG works in online/offline
mode, of course)[2]
— James Turner
|
|
|
|
|
|
Coding Help Needed! (Updated 11/2013)
|
|
|
|
|
Wanted: interview candidates
|
|
|
|
Development repository status
|
Getting started
How the FlightGear project works
The development process · Release plan
Building FlightGear · Git · Build server
Property tree · File formats · Tools of the Trade
|
General
Long term goals · Google Summer of Code
Project infrastructure enhancements
Improving glider realism / helicopter realism
Setting up a multiplayer server · Expo checklist
|
Aircraft
Making an aircraft · Flight dynamics model
3D aircraft models · Liveries · Resources
Creating instruments · System dependent instruments
Designing an autopilot
|
Animations
Animate models · Illuminate objects
Gear scissors · Tracking animation
Clickable panels · Knob / slider animation
|
Core
List of Core Developers · Developer Plans · Projects
Getting started · Programming resources
Adding fgcommands · Creating subsystems
Built-in Profiler · Howto:Extend Nasal
Howto:Use Property Tree Objects · Code cleanup
FlightGear-Points of Interest · Request for comments
OpenSceneGraph · Rendering system improvements
|
FlightGear Scripting with Nasal
Frequently asked questions · Writing simple scripts
Nasal for C++ programmers · Variables and their types
Conditionals · Loops · Operators · In-sim Console
|
Scenery
Procedural Texturing
Placing objects · Airport signs
Converting from X-Plane/MSFS
Making an airport · Generating terrain
Interactive traffic
|