Fritz,
In general, you can load ANY aircraft in ANY state that you want for ANY feature; meaning it's in the state you prefer after a flight/aircraft is loaded and ready to fly.
By means of an initialisation gauge.
But there's a lot a things you need to understand about initialisation of a flight/aircraft ...
1. You need to make a distinction beween features controlled by a custom event/var or standard FSX events/vars.
A feature controlled by an (non-standard) Lvar always starts up with the Lvar set to 0; Lvars are NOT stored in saved flight files, so (if other then 0) you need to initialise them to a specific value. See also Tom's reply.
The rest below applies to the standard FSX features (events/vars).
2. The state of some standard FSX features are saved in a saved (or default) flight file, some others are not.
Examples:
- The state of ParkingBrakes IS saved in a saved flight; so if you load an aircraft (in a current flight), or load a previously saved flight, the actual (c.q. saved) state is set.
- Features like NoSmoke, Seatbelt, Exit, etc have NO saved state; meaning that after flight/aircraft load their state is always 0 (Closed, Off, etc).
But in all cases you can initialise them as you like, by means of using the proper FSX events/vars in an initialisation gauge.
3. If you are using an initialisation gauge to force a feature in a certain state, be aware that some standard FSX features have _ON and _OFF event variations, some only have a _Toggle event (meaning you first have to test the current state before issueing a _Toggle event.).
AND: realise that some events only exist in FSX_Accell, NOT in FSX-SP2 or earlier. You need to check the SDK for that and for their existance at all (like (>K:NO_SMOKING_ON) is simply a non-existing event, as you already stated)
4. If the above is clear:
There's an initialisation-timing problem in FSX, causing events issued from an initialisation gauge NOT to be acted upon by FSX.
See this thread ....
http://www.fsdeveloper.com/forum/threads/fsx-ignores-events-at-flight-loading.429672/
Meaning that FSX may simply ignore an event issued from an already initialised and running gauge during initialisation of the aircraft/flight.
Now, to give you an example how to force the ParkingBrakes ON at aircraft/flight load, irrespective how you start FSX and which flight/aircraft you load (provided ParkingBrakes are enabled in the aircraft.cfg of course), add this gauge to the panel.cfg for all aircraft you want:
Code:
<Gauge Name="Initialisation" Version="1.0">
<Update Frequency="6"/>
<Element>
<Select>
<Value>
(* Uses the SeatBelt feature, always 0 at load, to detect if FSX is ready to receive events *)
(L:FSXReadyToReceiveEvents,bool) !
if{
(>K:CABIN_SEATBELTS_ALERT_SWITCH_TOGGLE)
(A:CABIN SEATBELTS ALERT SWITCH,bool)
if{ 1 (>L:FSXReadyToReceiveEvents,bool) }
}
els{
(* aircraft initialisation, executed once only *)
(L:AircraftInitialisation,bool) !
if{
(A:BRAKE PARKING POSITION,bool) ! if{ (>K:PARKING_BRAKES) }
(* other things to initialise *)
1 (>L:AircraftInitialisation,bool)
}
}
</Value>
</Select>
</Element>
</Gauge>
You can now use Lvar (L:AircraftInitialisation,bool) in any gauge (code) in the panel.cfg, to make sure that all aircraft features (under your control) are in a defined state after load....
No matter in what situation the flight/aircraft is loaded ....
Rob
ARKBRAKE_SET), (>K:SIGNS_ON), (>K:NO_SMOKING_ON) (>K:SEATBELT_ON) etc. does not exist and therefore doesn't work. I tried (>K:CABIN_SEATBELTS_ALERT_SWITCH_TOGGLE) and (>K:CABIN_NO_SMOKING_ALERT_SWITCH_TOGGLE) with no success.
