These need to be included aircraft model side to work;
e.g.
<signals include="/Aircraft/Generic/flightrecorder/components/ai-models-carrier.xml">
<count type="int">4</count>
</signals>
<signals include="/Aircraft/Generic/flightrecorder/components/ai-models-escorts.xml">
<count type="int">12</count>
</signals>
<signals include="/Aircraft/Generic/flightrecorder/components/ai-models-tanker.xml">
<count type="int">4</count>
</signals>
Periodically (default every 5 s), publish all properties
being tracked by the TriggeredPropertyPublisher.
This ensures that clients created after the TriggeredPropertyPublisher
will receive values for properties that change rarely (e.g. NAV/COM)
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
- Add fgcommands FG1000HardKeyPushed, FG1000SoftKeyPushed, to
simplify bindings from model XML. See FG1000/Nasal/commands.nas
- Use Device ID to ensure commands affect only the device to which
they belong. Navigation data, FMS, EIS and ADC information is shared
across all devices.
ConfigStore for storing and retrieving config settings (needs XML import/export)
Header display with 4 different header fields (all configurable)
Publisher for ADC and FMS.
SVG files from Michat on the forum:
Sat Jan 13, 2018 7:36 pm
Me, Michat. I donate the so called garmin1000B.svg file created by me using GPL Inkscape software to FlightGear, the Free Flight Simulator as a present to the flightgear.org. Since now I derived all legal rights to FlightGear via two active developers representatives on this forum topic: Stuart and hooray. They will proceed to upload the file to the FG repository, choosing the best license in order to protect FlightGear from any scammer simulation software, if is possible. Having account the nature of the Flightgear project as public well.
The 13TH of January 2018 in Madrid Spain.
Michat.
- Add new Emesary notification type for NAV/COM data
- Create Update/Publish interfaces using Emesary from properties
- Use interfaces to drive updates to EIS and NAV/COM frequencies
- Change the PageGroupController to a "proper" MFD page
- DTO MapStructure layer to provide a DTO line to a lat/lon
- Support for scrolling lists in the PFD/GroupElement
- Support MAP (NavigationMap) and ENGINE (EIS) soft-keys from other pages.
The instruments can now be enabled easily for testing purposes:
simply toggle their "serviceable" properties:
/instrumentation/mk-viii/serviceable or
/instrumentation/tcas/serviceable
Emesary is a simple and efficient class based interobject communcation system to allow decoupled disparate parts of a system to function together without knowing about each. It allows decoupling and removal of dependencies by using notifications to cause actions or to query values.
Emesary is all about decoupling and removing dependecies, and improving the structure of code. Using Emesary you can more easily define the what rather than the how. By using what is essential an event driven system it is easy to add or remove modules, and also for extra modules to be inserted that the rest of the aircraft knows nothing about (e.g. FGCamera or the Walker).
see: http://chateau-logic.com/content/emesary-nasal-implementation-flightgear
The AN/SPN-46 is an ACLS implementation using Emesary. ACLS is the Navy's version of ILS.
From https://github.com/Juanvvc/c172p-detailed/ release/2016.1
commit 3f33b88bb015a8ee685ab3178932d16d6e072410
A big Thank-You to the c172p-detailed team for their ongoing work.
- Small update to the main hydrodynamics system.
- Added initial versions of two systems for modelling hydrodynamic planing.
Signed-off-by: Anders Gidenstam <anders@gidenstam.org>
Channel spacing in NAV band is 50kHz not 25kHz as in COMM band.
Also convert line endings to LF instead of CR/LF
And remove BOM which is not necessary for UTF-8
The transponder instrument MUST be named "transponder" in the instrumentation
file to work with multiplayer and the radio dialog.
Thanks to lens(at)bitwisetech.com for the report and patch.
- Fix: runtime exception in remove_failure_mode()
- Fix: keep failure & trigger status on teleport.
- Fix: allow random failures from the gui to be enabled/disabled multiple times.
- Fix: mcbf/mtbf are set to zero when they fire, so they can be reactivated from the gui.
- Fix: string casts of several trigger types had syntax errors.
- Usability: screen messages related to failures now use positive logic:
"condition 100%" instead of "failure level 0%"
- Performance: Time triggers now use internal timers, instead of requiring being polled.
- Reviewed Trigger interface for more rational usage. reset() is replaced by arm()/disarm()
- Added a subscription interface to listen to FailureMgr events.
- Added an internal log buffer to keep a record of relevant events and present them to gui elements.
- Several usability improvements to the FailureMgr Nasal API.
- Making run_tests accept a target namespace as an argument.
- Fixed asynchronous trigger callback mechanism.
MCBF triggers working again.
- Fixed numerical problems when calculating standard deviation
for rand triggers.
Includes a simple automated testing framework for Nasal
(Aircraft/Generic/Systems/Tests/test.nas) and a collection of unit tests
for the failure manager, mostly for the different triggers.
Replaces existing Nasal/failures.nas script with a programmable failure
manager. The failure manager allows dynammic creation and removal of
failure modes, on demand activation and a flexible set of triggers.
The public interface can be found in Nasal/FailureMgr/public.nas
Aircraft/Generic/Systems/failures.nas provides a library of triggers and
failure actuators ready to use for programming the failure manager.
A compatibility layer is included under
Aircraft/Generic/Systems/compat_failure_modes.nas.
This compatibility layer is currently loaded on startup and programs the
FailureMgr to emulate the former behavior (same set of failure modes and
compatible interface through the property tree).
This first milestone is only intended to replace the failure management
engine underneeth with minimum visible changes, and hopefully no aircraft
breakages. Future milestones will build upon this to add a Canvas based
procedural GUI and example integration on aircrafts.
