Make more space for OpenXR information in the VR options dialog. The
OpenXR Runtime string on Monado is quite long, and VR State can now
include a couple of lines of error messages.
Tackle issue #2022: under advanced weather, using high-pressure-core
resulted in weather that did not match the METAR of the 'Fair weather'
scenario (but the 'High pressure core' scenario instead). With this fix
AW will go into METAR mode when fair weather is selected to match the
METAR.
See: https://sourceforge.net/p/flightgear/codetickets/2853/
Squashed commit of the following:
commit 28d4891e613f0ec14e13da2db3a1dd294ef0d922
Author: hbeni <beni@hallinger.org>
Date: Tue Jan 9 08:03:40 2024 +0100
Walker menu item label changed
fix#2655
see: https://sourceforge.net/p/flightgear/codetickets/2655/
commit 61adecd3b7d706ef13462e855ba9c141a8d0995b
Author: hbeni <beni@hallinger.org>
Date: Mon Jan 8 08:43:36 2024 +0100
Walker flashlight moved to own XML file and renamed colour-attributes to color
commit ef7c6119506368abc02d9ee0c239d6fa6b0ad6af
Author: hbeni <beni@hallinger.org>
Date: Sun Jan 7 16:53:11 2024 +0100
Walker/Flashlight: add CTRL+F as default keybind to toggle modes
commit 55d62498e5a86aa83d0447cce99ff054c0596076
Author: hbeni <beni@hallinger.org>
Date: Sun Jan 7 16:25:45 2024 +0100
Dimmed walker flashlight, so it better corresponds to the old c172 one
commit 0c8bc8a6c1c6c07308ddfb4d73ca6cf92fe40cae
Author: hbeni <beni@hallinger.org>
Date: Sun Jan 7 14:46:47 2024 +0100
Walker: Add a flashlight
This adds a compositor based flashlight to the walker model.
The flashlight currently has three modes: off/white/red.
It can be toggled using the walker menu entry.
Previously we did not take into account the atmospheric transmittance
to render the stars, leading to stars being incorrectly rendered in
low visibility conditions.
Also place the stars in the correct render bin.
Canvas placements are being added / removed through a listener on "placement" node adds / removals on the canvas's node.
Previously, when the canvas's del method was called, the canvas's node was removed, but not its "placement" subnodes.
This caused the canvas to be destroyed without the placements being removed.
This in turn causes problems when setting up a canvas with the same placement(s).
This is fixed by this commit by removing the "placement" nodes separately before destroying the canvas.
Previously both PeriodicPropertyPublisher and TriggeredPropertyPublisher
published irrespective of the property value.
This change adds an optional epsilon value below which a
notification will not be made. This significantly reduces the number
of Emesary notifications generated and therefore updates to the
displays.
The setValue() fuction expect 'path' and 'value' or only 'value', so in these cases, the content was treated as a path and caused "Illegal character in leaf of property path" error
