Configure the VPB elevation mesh via properties:
/scenery/elevation-mesh/sample-ratio controls the elevation
mesh sampling, allowing reduction in mesh size
/scenery/elevation-mesh/vertical-scale is just for fun and
scales the mesh vertically making mountains taller.
/scenery/elevation-mesh/constraint-gap-m controls how much below
airports etc. elevation vertices are forced to be.
gui/dialogs/multiplayer.xml: added checkbox.
defaults.xml: default /sim/mp-carriers/auto-attach to false with
userarchive="y".
Multiplayer carrier auto-attach is implemented in
fgaddon/MPCarrier/Systems/MPCarriers.nas.
Previously a <condition> block was assumed to contain
a single child, and other children were ignored, largely due to the PUI code.
Most developers would expect multiple children to be evaluated
as if surrounded by an <and> block, which is how the tutorial code
behaves.
This change wraps the children in an <and> making it consistent.
defaults.xml
Set new property /sim/mouse/mouse-rudder-elevator to false, but with
userarchive="y".
gui/dialogs/input-config.xml
Added checkbox to control /sim/mouse/mouse-rudder-elevator.
mice.xml:
Allow mouse control of elevator with button 0 down if
/sim/mouse/mouse-rudder-elevator is true.
Fix the created binding for toggle buttons.
Add autopilotDisconnect helper to controls.nas, and expose the new
function in the joystick configurator dialog.
Fixes from Henning Stahlke
Has a note saying 'May need restart to take affect' because it seems that
shadows never work unless enabled on startup. Note that the property setting is
persisted.
This change automatically changes the view direction to look
at a <marker> if any is defined for a checklist item or tutorial
step.
Both the tutorial and checklist features support a <marker> element
which can be used by an aircraft developer to display a magenta
circle around an item of interest (typically a control in the
cockpit).
Previously aircraft developers had to add a <view> element to move
the viewpoint to look at the marker, while users of checklists had
to look for the marker manually.
Now:
- For checklists, pressing the "?" button on a checklist will pan the viewpoint
to the marker.
- For tutorials, if there is not a <view> element defined for a
tutorial step, the view will automatically pan to the marker.
Show number of errors separately, don't override status if there are a non-zero
number of errors - this was unhelpful if we've managed to resume after errors.
New dialogue is accesible from the File menu.
Allows enable/disable of three new features: multiplayer record, continuous
record and recovery snapshot. Also moved load/save tape from the file menu into
the new dialogue.
Also removed recently-added flight recorder items from the multiplayer dialogue.
The recovery snapshot interval is 1s second if enabled. Might be better to make
it longer, e.g. 5s, but don't know how to change checkbox value.
Adds standard view option to enable pilot models.
Set /sim/rendering/pilot-model/available=true in aircraft
using pilot models.
/sim/rendering/pilot-model/enabled is used by users to
enable/disable the pilot models from the View Options dialog.
Note that pilot models are only visible for non-internal views.
Previously the Select Airport dialog set
the heading preset to 0. A recent change in the
reposition code meant that this was now being
complied with. This change fixes it by setting
the heading to the "uninitialized" special value
of 9999.0.
Checked by default. If unchanged, cursor keys are ignored instead of panning
the map; e.g. this allows them to be used with autopilot.
This requires associated flightgear commit.
METAR description is too big to fit in 'Weather Conditions' window.
Also moved the description of item selected in the popup (Live data, Manual
input, ... etc.) so it is immediately below the popup. Used to be the other
side of the METAR info, which was a little confusing.
Consolidate the two nasal sections into one (only one nasal section would be used).
Make controls work properly and accurately reflect status.
Remove OK and Apply as enable/disable takes effect immediately.
Comment out unsupported "Download other data files" checkbox.
Revised logic of AI Traffic to reflect status; added button to force update (normally AI Traffic update is only performed during startup)
PTT now in
/controls/radios/comm-ptt as an int; non zero indicates which comm radio to use
/comm-radio-selected is the default comm channel to use. This should usually be the same as will be set by PTT into /controls/radios/comm-ptt
NOTE: that PTT will switch the FG comm inbound and outbound frequency to whichever radio was PTT'd.
Patch by Daniel Wickstrom, requires a corresponding FLightGear change
to extend the special search function used by this dialog to add
support for a type-prefix.
Big rework of the Adjust LOD ranges dialog to hopefully make it easier to understand, and harder to setup so that models aren't visible by accident.
All range entry is now via sliders.
The sliders are deltas from the previous value.
There is now the option to specifically choose either low detail or high detail AI/MP models. *NOTE* that for models without a fallback index the low detail model will be the blue yellow glider.
There is now clear indication of what happens for the Meters or Pixel modes.
Added a defaults button that will restore a reasonable set of default values.
The properties that were used have been renamed to ensure that sensible defaults will be picked, ideally we'd have a way to migrate things like this but I don't think we do, so this is a reasonable alternative.
Since we mutate the (cached) definition properties on each call to
clone(), we need to reset these values back, or the non-clone()-ed
instance gets confused paths to its input and list widgets.
https://sourceforge.net/p/flightgear/codetickets/2044/
