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
Before fallback models were introduced, the ufo
was invisible to other MP pilots that were not in a
ufo themselves.
When fallback models were introduced, at long range
the ufo was replaced by the glider model, and so became
visible.
This change makes it invisible again by using the ufo as its
own fallback model. This is safe because the ufo model is
very lightweight and also shipped with fgdata.
Previously pilot models would stay visible when the
walker was active. Which is a bit unrealistic given
the walker is supposed to be "you" in some way.
So now the internal pilot is hidden when the walker
is active outside the aircraft.
Fix provided by Benedikt Hallinger
Previously props.condition threw an error if any of the
properties in the condition were not defines. This is
contrary to the behaviour of SGCondition, which it seeks
to emulate, which considers such undefined properties as
having the value 0.0.
Now this is the case.
This function only appears to be used by tutorials.nas,
where this behaviour was seen as discrepancy between
the checklist <condition> behaviour and the tutorial
<condition> behaviour.
See https://sourceforge.net/p/flightgear/codetickets/2394/?page=1
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.
Canvas displays stop working with a technique index of 1000. There is no apparent reason for this, but changing it to 0 or a lower value fixes the issue. There doesn't seem to be any negative consequences from doing this.
- Remove all Compositor Effects and Shaders.
- Unify the low-spec and ALS pipelines in a single pipeline called 'Classic'.
- Readd shadow mapping.
- Move the WS30 Effect and fragment shader out of the Compositor-specific directories.
Use (!passive) instead of (passive == 0), so that passive == nil is treated as
0.
E.g. this allows keyboard control of autopilot target speed, heading and
altitude in harrier-gr3.
