Gperon (talk) 09:47, 21 November 2020 (EST)
|
|
Benvenuto nel portale dello sviluppo
|
|
|
Visita our forum se non trovi qui quello che stai cercando.
|
|
|
Put a piece of yourself into FlightGear!
|
|
|
|
|
For 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). Also see the Jenkins build page and the Bug tracker.
Help needed:
The YASim FDM is looking for a new maintainer:
|
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.[1]
— James Turner
|
|
|
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.[2]
— Andy Ross
|
|
|
|
|
|
Coding Help Needed! (Updated 06/2020)
|
|
|
|
|
Wanted: interview candidates
|
|
|
Stato del repository di sviluppo
|
Getting started
Come funziona il progetto FlightGear
Il processo dello sviluppo · Piano dei rilasci
Compilare FlightGear · Git · Compilare il server
Strutture delle proprietà · Formato dei file · Strumenti del Trade · Bug tracker
|
General
Obiettivi a lungo termine · Idee popolari · Google Summer of Code
Miglioramenti della infrastruttura di progetto
Improving glider realism / helicopter realism
Setting up a multiplayer server · Expo checklist
|
Aircraft
Howto:Troubleshooting Aircraft Performance Issues·
Making an aircraft · Flight dynamics model
3D aircraft models · Liveries · Resources
Soaring instrumentation sdk · Creating instruments · System dependent instruments
Designing an autopilot
|
Animations
Animate models · Illuminate objects
Gear scissors (con tracking animation)
Clickable panels · Knob / slider animation
|
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:Using Ada in FlightGear (updated!)
Howto:Use Property Tree Objects · Code cleanup
FlightGear-Points of Interest · Request for comments
OpenSceneGraph · Rendering system improvements · Jenkins build page · Bug tracker
|
Scenery
Procedural Texturing
Placing objects · Airport signs
Converting from X-Plane/MSFS
Making an airport · Generating terrain
AI Traffic
|
Scripting
Frequently asked questions · Writing simple scripts
Nasal for C++ programmers · Variables and their types
Conditionals · Loops · Operators · In-sim console
|
Effects and shaders
Shaders · Project Rembrandt
Shader programming in FlightGear
Best Practices · GLSL resources
|