For each add-on, the subtree of the global Property Tree starting at
/addons/by-id/ADDON_ID/addon-devel is reserved for the specific needs of
the add-on, where ADDON_ID stands for the add-on identifier.
- Engines control now use the same axis methods as the flight controls; which allows for these to have an inverted checkbox.
- Change the axis combo boxes to instead show a popup dialog (much like the button config). This is better because the items can be grouped sensibly.
- Changed the way that the "all engines" controls work - the dialog binds these to a "engines/XXXX-all" for which there is a listener in controls.nas which propogates over all engines.
- Added extra bindings to both the buttons and the axis dialogs.
- moved the "None" button to the bottom and renamed it to the more comprehensible "Remove assignment"
https://github.com/c172p-team/c172p-detailed/tree/version/2018.1b90f547039
Changelog:
New images for the new splash screen and thumbnails system
FDM improvements:
Fixed deflection angles of ailerons and roll moment due to ailerons
Added spiraling propwash effect (requiring right rudder at full throttle, low airspeed)
Made the elevator action at high AoA asymmetric in order to take into account the screening effect of the horizontal stabilizer in such stall conditions
Increasing the side force due to rudder, to make it consistent with the exerted moment
Decreasing the adverse yaw (the aileron trim gave too much slip-skid-ball deviation at cruise)
Increased maximum rotation of yoke from 70 to 90 degrees
Use shift + q to reset view
Added avionics sound
Fixed bug with oil temperature and pressure gauges (they were not working when complex engine procedures was toggled off)
Fixed bug with lighting of pontoon wake effect
Eliminated wingtip and tail sparks when over water
Eliminated sparks of broken gear while aircrafts sits on the flight deck of a moving carrier
Fixed some bugs with the walker
The add-on framework now uses the following files in each add-on
directory:
- addon-config.xml (previously: config.xml)
- addon-main.nas (previously: main.nas)
This is consistent with the addon-metadata.xml file that is already part
of the interface between FG core and add-ons. The goal is to make it
clearer, when browsing an add-on directory, which files belong to the
"FG core <-> add-on" interface and which files belong to the add-on
proper. This will be beneficial also when more files are added to the
"FG core <-> add-on" interface, such as possibly addon-events.xml in the
future.
This change is incompatible, thus it is the right time to do *before*
2018.2.1 is out, especially considering that this upcoming release
already has incompatible changes in the add-on API, namely the
requirement of the addon-metadata.xml file and the type of the argument
passed to each add-on's main() function. We'll try harder not to break
compatibility in the add-on API once 2018.2.1 is out. For now, it is
still a good time to try to get the API as clean as possible.
