Difference between revisions of "Portal:Developer"

From FlightGear wiki
Jump to: navigation, search
(added link to new howto)
m (Undo revision 69851 by Bigstones (talk) removing my lousy article)
Line 60: Line 60:
 
[[Howto: Place 3D objects with the UFO|Placing objects]] · [[Signs|Airport signs]]<br/>
 
[[Howto: Place 3D objects with the UFO|Placing objects]] · [[Signs|Airport signs]]<br/>
 
[[Howto: Convert objects from X-Plane|Converting from X-Plane/MSFS]]<br/>
 
[[Howto: Convert objects from X-Plane|Converting from X-Plane/MSFS]]<br/>
[[Howto:Convert objects with ModelConverterX|Converting with ModelConverterX]]<br/>
 
 
[[Howto: Make an airport|Making an airport]] · [[Using TerraGear|Generating terrain]]<br/>
 
[[Howto: Make an airport|Making an airport]] · [[Using TerraGear|Generating terrain]]<br/>
 
[[Interactive traffic]]</span>
 
[[Interactive traffic]]</span>

Revision as of 16:51, 8 May 2014

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:

Creating an integrated Canvas based GUI launcher/package manager ticket #1295:

Cquote1.png For aircraft, the system supports aircraft dirs, there is the package manager code which works but is currently unused, which can download and extract zipped aircraft. This needs a GUI but thanks to the new reset architecture we can finally build this GUI inside FG - i.e an ‘aircraft chooser’ UI - however I am find building such a UI rather outside my comfort zone. If anyone would like to help in this area, let me know.[1]
— James Turner
Cquote2.png


The YASim FDM is looking for a new maintainer:

Cquote1.png There are some pending merge requests[1] to add some YASim features, but we have an issue that since none of the current C++ developers own, or are experts in YASim, we're reluctant to be the person who merges such changes, and potentially introduces subtle regressions.

Obviously this is chicken-and-egg, since no one can become expert enough in the code to become a maintainer :)

So, I'm more than happy to apply patches *providing* I can be convinced they are sane+reasonable from a pure code perspective (happy to help with that, too, if people are new to C++), and providing we have some assurance that a representative sample of YASim aircraft are unchanged or improved by the patch. Suggestions for that means in practice, are most welcome!

Otherwise I worry, given the nature of the solver, we'll keep optimising the solver for some aircraft, and making other existing aircraft worse - until someone tests them, and announced that they're no longer working.[2]
— James Turner
Cquote2.png
Cquote1.png I am still broadly happy to answer questions if posed (as long as I remember enough to come up with a meaningful answer). Just cc: me if you do, because my latencies here are measured in weeks.Bugs can always be fixed. What YASim needs is a maintainer, not really expertise per se. The latter comes from the former.[3]
— Andy Ross
Cquote2.png
  1. James Turner (2014-04-17 18:23:24). size of flightgear-data.
  2. James Turner (Fri, 05 Oct 2012 03:54:43 -0700). YASim and documentation.
  3. Andy Ross (Fri, 05 Oct 2012 03:54:43 -0700). YASim and documentation.
 
 

Coding Help Needed! (Updated 11/2013)


 
 

Wanted: interview candidates

Every month we try to include an interview with a contributor in the FlightGear Newsletter. Anyone contributing to FlightGear, in whatever way, is welcome to answer a few questions and write his/her own interview.

More info at FlightGear Newsletter: Interview.
Development repository status
Current release: 2020.1 (26 Jun 2020)
Next release: 2020.3 (4 days from now)
See release plan for details.

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 · Popular Ideas · Google Summer of Code
Project infrastructure enhancements
Improving glider realism / helicopter realism
Setting up a multiplayer server · Expo checklist

Portal aircraft.png

Aircraft
Making an aircraft · Flight dynamics model
3D aircraft models · Liveries · Resources
Soaring instrumentation sdk · Creating instruments · System dependent instruments
Designing an autopilot

Nuvola apps kaboodle.png

Animations
Animate models · Illuminate objects
Gear scissors · Tracking animation
Clickable panels · Knob / slider animation

Portal developer.png

Core
List of Core Developers · Developer Plans · Projects
Getting started · Programming resources · Adding scripting bindings
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

Portal scenery.png

Scenery
Procedural Texturing
Placing objects · Airport signs
Converting from X-Plane/MSFS
Making an airport · Generating terrain
Interactive traffic

Nasallogo3.png

Scripting
Frequently asked questions · Writing simple scripts
Nasal for C++ programmers · Variables and their types
Conditionals · Loops · Operators · In-sim console

Animation Icon.png

Effects and shaders
Shaders · Project Rembrandt
Shader programming in FlightGear
Best Practices · GLSL resources