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/
This will only work for valid VORTAC or TACAN stations.
Not all frequencies can be mapped to VOR frequency range. These will be displayed (and entered) without a decimal place to differentiate them.
Realistically 768 pixels is the minimum height for most displays these days, so 500 is a reasonable figure for all displays, and it does make it easier to operate.
- added extra bindings
- reworked the view axis (usually bound to the hat); to move at a better rate.
- trim to elevator position. When selected this will remember the current position and when the joystick is centered it will apply this as the trim. Very useful for carrier approaches; and also it helps to do something that is much easier with loaded controls when you can feel the pressure being reduced by the operations of the trim switch
By setting /sim/model/fallback-model-index, an MP model
can transmit an index into the AI/Aircraft/fallback_models.xml
file which will be used if the aircraft model cannot be found
in other instances Aircraft or AI/Aircraft directories.
GUI and default property for /sim/multiplay/use-detailed-models
to indicated if we prefer to use detailed models from Aircraft (true)
or simpler models from AI (false).
Checklists now support grouping by placing a group of checklists
under a <group> node.
e.g. /sim/checklists/group/checklist
The group can have a <name>, which is used by the checklist dialog
and can be used by other interfaces, such as the FG1000.
- 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"
Change /sim/multiplay/transmit-only-generics to /sim/multiplay/transmit-filter-property-base, which can be 1 to transmit only generics, or a number greater than 1 to indicate the start index to transmit (e.g. 12000 for new emesary mp bridge properties)
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
Change fonts; make use of the new feature to allow fonts to be specified using property from dialog xml.
Ensure that all fonts are defined within the style.
Change to use the ports defined in the property tree when connecting from the dialog.
Ensure properties for ports are set to a valid (non zero, not null) value on dialog initialisation.
Add ability to change receive port from dialog firstly to see what it is and secondly to allow multiple fg sessions
As suggested in
<https://sourceforge.net/p/flightgear/mailman/message/35580843/>, use
$FG_HOME/Export rather than $FG_HOME as the default directory for the
file selector dialogs popping up when loading or saving a flightplan
from the route manager dialog. This is because $FG_HOME/Export will not
trigger the "this path is not authorized for writing" refusal added in
280cd523686fbdb175d50417266d2487a8ce67d2, whereas $FG_HOME normally
will.
Since a typical (and suggested) allowed directory for saving flightplans
from the Route Manager dialog is $FG_HOME/Export, it makes sense for the
Load and Save file selection dialogs to open in at least $FG_HOME. And
since $FG_HOME is a hidden dir by default on Unix systems, it is more
user-friendly to display hidden files and dirs in these dialogs as well.
Note: when hidden files/dirs are not displayed, it *is* possible, at
least in the QtFileDialog, to type .fgfs and get inside when
browsing $HOME, but that is probably not obvious to everyone!
The value of "/environment/moonlight" is now automatically set based on the phase of the moon.
Therefore the Moonlight option and slider in the PUI Environment Settings window have been deleted.
