### Example of Wwise Event Naming Convention in XML

Source: https://docs.flightsimulator.com/html/Asset_Creation/Sounds/Using_Wwise

Illustrates how to set up an XML structure for a sound event in Wwise, which then translates into a specific event name following the defined convention. This example shows the setup for a wind sound.

```xml
<WindSounds>
    <Sound WwiseEvent="wind_sound" WwiseData="true" />
</WindSounds>

Resulting event name in Wwise: Play_MyAircraft_wind_sound
```

```xml
// For an AI aircraft sound:
// Resulting event name in Wwise: Play_MyAircraft_ai_wind_sound
```

--------------------------------

### Configure Engine Sound Transitions (XML)

Source: https://docs.flightsimulator.com/html/Content_Configuration/Sounds/Sound_Examples

This example demonstrates how to set a transition sound for an engine using the `<EngineSoundTransitions>` element. It specifies the sound to play when an engine transitions between states, such as from 'Start' to 'On', and targets a specific engine index.

```XML
<EngineSoundTransitions>
    <!-- sound will play on Engine 2, when the engine goes from Star to On -->
    <Sound WwiseEvent="MySound" WwiseData="true" StateFrom="Start" StateTo="On"  EngineIndex="2"/>
</EngineSoundTransitions>
```

--------------------------------

### Configure Engine Sound States (XML)

Source: https://docs.flightsimulator.com/html/Content_Configuration/Sounds/Sound_Examples

Example of linking sounds to specific engine states (Start, On) using the `<EngineSoundStates>` element. This configuration ensures sounds play only when the engine is in the defined states, with `StateOff`, `StateStart`, and `StateOn` attributes controlling playback.

```XML
<EngineSoundStates>
    <!-- sound will play on Engine 1 when the engine is in "Start" and "On" states -->
    <Sound WwiseEvent="MySound" WwiseData="true" EngineIndex="1"  StateOff="false" StateStart="true" StateOn="true" />
</EngineSoundStates>
```

--------------------------------

### Configure Acoustic Parameters (Reverberation) (XML)

Source: https://docs.flightsimulator.com/html/Content_Configuration/Sounds/Sound_Examples

Sets up acoustic parameters, specifically reverberation presets for inside and outside environments. This allows for distinct acoustic characteristics based on the listener's location relative to the sound source. Requires Wwise setup.

```xml
<AcousticParameters>
    <Parameter Name="ReverberationPreset" ShareSetInside="shareset_inside_name" ShareSetOutide="shareset_outside_name"/>
</AcousticParameters>
```

--------------------------------

### Programming SimConnect Clients using Managed Code

Source: https://docs.flightsimulator.com/html/Programming_Tools/SimConnect/API_Reference/Structures_And_Enumerations/SIMCONNECT_RECV_ENUMERATE_INPUT_EVENTS

Guides and examples for developing SimConnect clients using managed code languages like C# and VB.NET.

```APIDOC
## Programming SimConnect Clients using Managed Code

### Description
This section provides resources and examples for developers who want to create SimConnect clients using managed code environments such as .NET (C#, VB.NET). It covers setting up the development environment and interacting with SimConnect functionalities.

### Method
N/A (Documentation guide)

### Endpoint
N/A

### Parameters
N/A

### Request Example
N/A

### Response
N/A
```

--------------------------------

### Configure Miscellaneous Sounds (XML)

Source: https://docs.flightsimulator.com/html/Content_Configuration/Sounds/Sound_Examples

A simple example showing the use of the `<MiscellaneousSounds>` element to trigger various sounds, such as stall warnings, overspeed alerts, and pre-flight check confirmations. Each sound is defined by its Wwise event.

```XML
<MiscellaneousSounds>
    <Sound WwiseEvent="STALL_WARNING" WwiseData="true" />
    <Sound WwiseEvent="OVERSPEED_WARNING_SOUND" WwiseData="true" />
    <Sound WwiseEvent="AP_PREFLIGHT_CHECK_OVER" WwiseData="true" /> 
</MiscellaneousSounds>
```

--------------------------------

### Flight Simulator <Loop> Example

Source: https://docs.flightsimulator.com/html/Content_Configuration/Models/Model_Examples

This example demonstrates a <Loop> structure that iterates from a starting value to an ending value, incrementing by a specified amount each time. It sets up and modifies parameters within each iteration.

```XML
<Loop>
    <Setup>
        <Param>AP_ID</Param>
        <From>1</From>
        <Inc>1</Inc>
        <To>#AP_COUNT#</To>
    </Setup>
    <Do>
        <Parameters Type="Default" Lifetime="Loop">
            <RESET_CODE_T/>
        </Parameters>
        <Parameters Type="Override" Lifetime="Loop">
            <RESET_CODE_T>#RESET_CODE_T# #AP_ID# #ID# != if{ 0 (&gt;L:XMLVAR_Autopilot_#AP_ID#_Status) }</RESET_CODE_T>
        </Parameters>
    </Do>
    <Then>
        <RESET_CODE>#RESET_CODE_T#</RESET_CODE>
    </Then>
</Loop>
```

--------------------------------

### Example Contact Point Configuration

Source: https://docs.flightsimulator.com/html/Samples_And_Tutorials/Tutorials/Defining_A_Flight_Model

An example of a configured contact point using the specified format in `flight_model.cfg`. This line sets a specific wheel's properties, including its class, position, crash velocity, and wheel radius, among other parameters.

```plaintext
point.0 = 1, 1.1, 0, -3.44, 750, 0, 0.5, 10, 0.3185, 2, 0.75, 0, 0, 0, 0, 0
```

--------------------------------

### RTCCameraShot Example with Multiple Cameras (XML)

Source: https://docs.flightsimulator.com/html/Content_Configuration/Cameras/RTC/RTC_Definition_Examples

Demonstrates the configuration of an RTCCameraShot element with multiple RTCShotPoints. Each point defines a camera's GUID, name, and specific shot parameters like depth of field, duration, and interpolation. This allows for complex camera sequences within a simulation.

```xml
<SimMission.RTCCameraShot InstanceId="{1EEB0EBA-A259-43C4-B43E-13A9BA93B13E}">
    <Descr>CameraShot1</Descr>
    <RTCShotPoints>
        <RTCShotPoint>
            <CameraGUID>{8A1987D0-09B6-7E48-B4E1-62C5DBE2A720}</CameraGUID>
            <CameraName>FixedOnPlane_Belly</CameraName>
            <DepthOfField>
                <Activate>True</Activate>
                <Blur>0.2</Blur>
            </DepthOfField>
        </RTCShotPoint>
        <RTCShotPoint>
            <CameraGUID>{7a91803e-898b-435a-8391-725be6a48203}</CameraGUID>
            <CameraName>FixedOnPlane_LeftWing</CameraName>
            <ShotDuration>10</ShotDuration>
            <Interpolation>PushMid</Interpolation>
        </RTCShotPoint>
        <RTCShotPoint>
            <CameraGUID>{7a91803e-898b-435a-8391-725be6a48203}</CameraGUID>
            <CameraName>FixedOnPlane_LeftWing</CameraName>
            <ShotDuration>3</ShotDuration>
            <Interpolation>PushEdge</Interpolation>
        </RTCShotPoint>
    </RTCShotPoints>
</SimMission.RTCCameraShot>
```

--------------------------------

### Define Visual Effect Objects in XML

Source: https://docs.flightsimulator.com/html/Content_Configuration/Environment/Scenery_Objects/Scenery_Object_Example

XML elements for placing visual effect objects in the simulator environment. Demonstrates referencing effect files by name, path/name, and GUID, along with placement and scaling parameters.

```xml
<SceneryObject lat="12.95033281481212" lon="-73.98572144016812" alt="100.00000000000000" pitch="0.000000" bank="0.000000" heading="-45.119477" imageComplexity="VERY_SPARSE" altitudeIsAgl="TRUE" snapToGround="TRUE" snapToNormal="FALSE">
    <VisualEffectObject effectName="Smoke_SOS" scale="1.000000"/>
</SceneryObject>
<SceneryObject lat="40.85931289081295" lon="-119.33189593300625" alt="50.00000000000000" pitch="-105.000050" bank="-0.000057" heading="-105.503571" imageComplexity="VERY_SPARSE" altitudeIsAgl="TRUE" snapToGround="TRUE" snapToNormal="FALSE">
    <VisualEffectObject effectName="Base/Smoke_SOS" scale="2.500000"/>
</SceneryObject>
<SceneryObject lat="43.07744844570071" lon="-73.98572144016812" alt="0.00000000000000" pitch="0.000382" bank="-0.000382" heading="118.942758" imageComplexity="VERY_SPARSE" altitudeIsAgl="TRUE" snapToGround="TRUE" snapToNormal="FALSE">
    <VisualEffectObject name="{A04B772A-6BBF-4103-B263-D479BCCE71F5}" scale="-0.750000"/>
</SceneryObject>
```

--------------------------------

### Calculating Max Emergency Boost Time (engines.cfg Example)

Source: https://docs.flightsimulator.com/html/Content_Configuration/SimObjects/Aircraft_SimO/Additional_CFG_Information

Provides an example calculation for setting the 'max_emergency_boost_time' parameter in engines.cfg, considering manifold pressure limits and desired duration at maximum boost.

```text
max_emergency_boost_time = 315 * (67/61) = 315 * 1.098 = 346
```

--------------------------------

### Example Fuel System Trigger Definition

Source: https://docs.flightsimulator.com/html/Content_Configuration/SimObjects/Aircraft_SimO/flight_model/fuel_system

This example demonstrates a basic configuration for a single fuel system trigger. It specifies a condition ('Autostart_Enabled') and lists the effects to be triggered when the condition is true, such as opening valves and starting pumps.

```plaintext
Trigger.1 = Condition:Autostart_Enabled
#EffectTrue:OpenValve.LeftEngValve,
OpenValve.RightEngValve,
OpenValve.CrossFeedValve,
StartPump.LeftTankPump,
StartPump.RightTankPump
```

--------------------------------

### Configure SimVar Sounds with Ranges and Requirements (XML)

Source: https://docs.flightsimulator.com/html/Content_Configuration/Sounds/Sound_Examples

This advanced example demonstrates configuring sounds within `<SimVarSounds>` that depend on multiple conditions. It includes playing sounds based on SimVar value ranges and additional requirements defined by `<Requires>` elements, which can specify other SimVars or LocalVars with their own conditions.

```XML
<SimVarSounds>
    <!--This sound will play if :
        - SIMVAR TEST 1 value is between 10 and 15, and when it's over 25,
        - And if SIMVAR TEST 2 value is above 60, 
        - And if SIMVAR TEST 3 value changes. -->
    <Sound WwiseEvent="Sound_For_Test_2" WwiseData="true" SimVar="SIMVAR TEST 1" Units="PERCENT" Index="0">
        <Range LowerBound="10.0" UpperBound="15.0"/>
        <Range LowerBound="25.0" />
        <Requires SimVar="SIMVAR TEST 2" Units="PERCENT" Index="0">
            <Range LowerBound="60" />
        </Requires>
        <Requires SimVar="SIMVAR TEST 3" Units="PERCENT" Index="0"></Requires>
    </Sound>
</SimVarSounds>
```

--------------------------------

### Define Checkpoint Library XML

Source: https://docs.flightsimulator.com/html/Content_Configuration/Checklists/Checklist_Examples

This XML structure defines a checkpoint library for Flight Simulator. It includes two example checkpoints: 'Parking_Brake_Set' and 'Brakes_Released', each with associated clues, descriptions, test conditions, and actions.

```xml
<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="CheckpointLibrary" version="1,0">
    <Checklist.CheckpointLibrary>
        <Checkpoint Id="Parking_Brake_Set">
            <Clue name="TT:CLUE.PARKING_BRAKE_SET"/>
            <CheckpointDesc SubjectTT="TT:GAME.CHECKLIST_PARKING_BRAKE" ExpectationTT="TT:GAME.CHECKLIST_SET"/>
            <Test>
                <TestValue>
                    <Val SimVarName="BRAKE PARKING POSITION" Units="Boolean"/>
                </TestValue>
                <Action Copilot="True" Condition="TestValueFalse" Once="true" EventID="PARKING_BRAKES"/>
                <Instrument Id="LANDING_GEAR_Switch_ParkingBrake"/>
            </Test>
        </Checkpoint>
        <Checkpoint Id="Brakes_Released">
            <Clue name="TT:CLUE.BRAKES_RELEASED"/>
            <CheckpointDesc SubjectTT="TT:GAME.CHECKLIST_BRAKES" ExpectationTT="TT:GAME.CHECKLIST_RELEASED"/>
            <Sequence SeqType="Unordered">
                <Test>
                    <TestValue>
                        <Operator OpType="NOT">
                            <Val SimVarName="BRAKE PARKING POSITION" Units="Boolean"/>
                        </Operator>
                    </TestValue>
                    <Action Copilot="True" Condition="TestValueFalse" Once="true" EventID="PARKING_BRAKES"/>
                    <Instrument Id="LANDING_GEAR_Switch_ParkingBrake"/>
                </Test>
                <Test>
                    <Instrument Id="HANDLING_RudderPedals_Rudder"/>
                    <Instrument Id="HANDLING_RudderPedals"/>
                    <Instrument Id="HANDLING_RudderPedals1"/>
                    <Instrument Id="HANDLING_RudderPedals2"/>
                    <TestValue>
                        <Operator OpType="AND">
                            <Operator OpType="EQUAL">
                                <Val SimVarName="BRAKE LEFT POSITION" Units="percent"/>
                                <Val Value="0"/>
                            </Operator>
                            <Operator OpType="EQUAL">
                                <Val SimVarName="BRAKE RIGHT POSITION" Units="percent"/>
                                <Val Value="0"/>
                            </Operator>
                        </Operator>
                    </TestValue>
                    <Action Copilot="True" Condition="TestValueFalse" EventID="AXIS_LEFT_BRAKE_SET" EventParam="-16383"/>
                    <Action Copilot="True" Condition="TestValueFalse" EventID="AXIS_RIGHT_BRAKE_SET" EventParam="-16383"/>
                </Test>
            </Sequence>
        </Checkpoint>
    </Checklist.CheckpointLibrary>
</SimBase.Document>
```

--------------------------------

### Interaction Type Example

Source: https://docs.flightsimulator.com/html/Samples_And_Tutorials/Tutorials/Creating_Interactions_Using_InputEvents

Shows an example of setting the interaction type for an input event. The INTERACTION_TYPE parameter automatically configures templates, sound events, animations, and tooltips based on the selected type.

```xml
<INTERACTION_TYPE>Switch</INTERACTION_TYPE>
```

--------------------------------

### Looping Template Usage for Repetitive Elements (XML)

Source: https://docs.flightsimulator.com/html/mergedProjects/How_To_Make_An_Aircraft/Contents/Model_Behaviours/Templates

Shows how to use the `<Loop>` element to simplify repetitive `<UseTemplate>` calls. The `<Setup>` section defines values for a variable (e.g., MAP_MODE) and parameters, while the `<Do>` section contains the template usage that will be repeated for each setup value, creating multiple similar components efficiently.

```xml
<Loop>
    <Setup>
        <Value>MAP_MODE</Value>
        <Parameters>
            <1>WXR</1>
            <2>STA</2>
            <3>WPT</3>
            <4>ARPT</4>
            <5>DATA</5>
            <6>POS</6>
            <7>TERR</7>
        </Parameters>
    </Setup>
    <Do>
        <UseTemplate Name="My_Button_Template">
            <BASE_NAME>A_GLTF_NODE_PUSH_#MAP_MODE#</BASE_NAME>
            <ON_EVENT>(&gt;H:Plane_MFD_MAP_#MAP_MODE#)</ON_EVENT>
        </UseTemplate>
    </Do>
</Loop>
<!-- Create 7 buttons with an animation, a mouserect and an inputevent -->
```

--------------------------------

### RTCSequencer Calling an RTCShot (XML)

Source: https://docs.flightsimulator.com/html/Content_Configuration/Cameras/RTC/RTC_Definition_Examples

Shows how an RTCSequencer can invoke an RTCShot. This setup defines a sequence of actions, including a reference to a specific RTCShot that dictates camera position, orientation, and animation details for a particular scene.

```XML
<SimMission.RTCSequencer InstanceId="{18818CE1-18B4-4943-A8CC-D5362D943993}">
    <Descr>LandingChallengeIntroAirportID67</Descr>
    <Shuffle>True</Shuffle>
    <Actions>
        <SimMission.ObjectReference id="RunwayShowCaseSequence"   InstanceId="{0CA3070E-C18A-4894-8AFB-B322ECCC48F1}"/>
    </Actions>
</SimMission.RTCSequencer>
      
<SimMission.RTCShot InstanceId= "{0CA3070E-C18A-4894-8AFB-B322ECCC48F1}">
    <Descr>RunwayShowCaseSequenceID67</Descr>
    <WorldPosition>N44° 48' 36.212",W114° 48' 32.579",+004200</WorldPosition>
    <Orientation>0.000,0.000,174.000</Orientation>
    <FileGUID>{694C8754-5989-44D1-9DEA-BD706C719BA2}</FileGUID>
    <AnimationName>Move</AnimationName>
    <CameraNodeName>Camera</CameraNodeName>
    <TargetNodeName>Target</TargetNodeName>
</SimMission.RTCShot>
```

--------------------------------

### Legacy FSX SimObject Animation XML Setup

Source: https://docs.flightsimulator.com/html/Content_Configuration/Models/Model_Examples

Demonstrates the setup for legacy FSX SimObjects animations, requiring a PartInfo block alongside the Animation definition. It links an animation to a simulator variable.

```xml
<Animation name="c_gear" guid="E2E339A6-FCBF-43a9-A780-3473E03AB54B" length="200" type="Sim" typeparam2="c_gear" typeparam="AutoPlay" />
<PartInfo>
    <Name>c_gear</Name>
    <AnimLength>200</AnimLength>
    <Animation>
        <Parameter>
            <Sim>
                <Variable>GEAR ANIMATION POSITION:0</Variable>
                <Units>keyframe</Units>
            </Sim>
        </Parameter>
    </Animation>
</PartInfo>
```

--------------------------------

### While Loop Example

Source: https://docs.flightsimulator.com/html/Content_Configuration/Models/ModelBehaviors/Program_Template_Definitions

Demonstrates the structure of a 'while' loop in Flight Simulator XML. It sets up a parameter 'ID' starting from 1, increments it by 1 each iteration, and continues as long as the parameter 'MY_PARAM_#ID#' is valid. This loop has a default limit of 64 iterations unless a <To> element is also specified.

```xml
<Loop>
    <Setup>
        <Param>ID</Param>
        <From>1</From>
        <Inc>1</Inc>
        <While>
            <Arg Valid="MY_PARAM_#ID#"/>
        </While>
    </Setup>
    <Do>
        <!-- XML to be executed each iteration -->
    </Do>
</Loop>
```

--------------------------------

### Configure Engine Sound Presets (XML)

Source: https://docs.flightsimulator.com/html/Content_Configuration/Sounds/Sound_Examples

Examples of configuring sound presets for aircraft engines using the `<EngineSoundPresets>` element. This includes setting up sounds for combustion, shutdown, and custom suffixes, along with specific configurations for helicopter rotors. It uses Wwise events and specifies engine or rotor indices and RPM thresholds.

```XML
<EngineSoundPresets>
    <!-- sound will stop if the engine state goes to 'off' and if the 3rd engine is below the 675rpm threshold -->
    <Sound WwiseEvent="Combustion" ConeHeading="225" RPMMin="675" WwiseData="true" EngineIndex="3"/>
    <!-- sound will play if the engine state goes to off and if the 3rd engine rpm is below the 675rpm threshold --> 
    <Sound WwiseEvent="Shutdown" ConeHeading="225" RPMMin="675" WwiseData="true" EngineIndex="3"/>
    <!-- sound will play the wwise event "Play_SimObjectName_eng3_combustion_from_left" on the 3rd engine.-->
    <Sound WwiseEvent="Combustion" CustomSuffix="from_left" ConeHeading="225" RPMMin="675" WwiseData="true" EngineIndex="3"/>
    <!-- sound will play the wwise event "Play_SimObjectName_eng3_shutdown_from_left" on the 3rd engine.--> -->
    <Sound WwiseEvent="Shutdown" CustomSuffix="from_left" ConeHeading="225" RPMMin="675" WwiseData="true" EngineIndex="3"/>
</EngineSoundPresets>
```

```XML
<EngineSoundPresets>
    <!-- This sound will be linked to the First Rotor and will stop if that rotor RPM is below the 285rpm threshold. The wwise event will be "Play_SimObjectName_rotor1_rotor"  -->
    <Sound WwiseEvent="Rotor" FadeOutType="2" FadeOutTime="1" WwiseData="true" RPMMin="285" RotorIndex="1" EngineIndex="1"  />
    <!-- This sound will be linked to the Second Rotor and will stop if that rotor RPM is below the 2770rpm threshold. The wwise event will be "Play_SimObjectName_rotor2_rotor"  -->
    <Sound WwiseEvent="Rotor" ConeHeading="90"  FadeOutType="2" FadeOutTime="1" WwiseData="true" RPMMin="2770" RotorIndex="2" EngineIndex="1" />
</EngineSoundPresets>
```

--------------------------------

### Complete FLT Example for Flight Simulator

Source: https://docs.flightsimulator.com/html/Content_Configuration/Flights_And_Missions/Flight_Weather_Event_Examples

This code snippet represents a complete FLT file used in a flight simulator. It defines various parameters for a free flight mission, including mission type, location, aircraft configuration, weather settings, and system states. This file acts as a configuration script to load a specific flight scenario.

```ini
[Main]
MissionType=FreeFlight
MissionLocation=London
Title=London XO
Description=London
AppVersion=10.0.282174
FlightVersion=1

[Briefing]
BriefingText=$$:London Freeflight
BriefingImage0=./images/Briefing0.png

[Options]
Sound=True
Pause=True
Moonlight=True
Save=False
SaveOriginalFlightPlan=False
TextDisplayPage=0
SlewDisplayPage=1
AxisIndicator=Off
Titles=False

[Sim.0]
Sim=Cessna Skyhawk G1000 Asobo

[ResourcePath]
Path=Missions\Asobo\FreeFlights\FreeFlight\FreeFlight

[ObjectFile]
File=Missions\Asobo\FreeFlights\FreeFlight\FreeFlight

[Atc_Menu]
Visible=False

[FreeFlight]
FirstFlightState=PREFLIGHT_HOLDSHORT

[TrafficManager]
disable=False

[Multiplayer]
Status=False

[AirTraffic]
Status=False

[Weather]
UseWeatherFile=True
WeatherCanBeLive=True
WeatherType=0
DynamicWeatherOverride=1
CloudmapPosOverride=True
CloudmapInitialPosX=4692.740
CloudmapInitialPosY=-10913.52

[Departure]
ICAO=EGLC
RunwayNumber=27
RunwayDesignator=NONE
GateName=PARKING
GateNumber=1

[Loading]
ImageName=./images/Loading0.png
Tips0=TT:LOADING.TIPS.C172_004

[Panels]
Panel.On=True
HUD.On=False

[Window.1]
Order=255
Active=True
Undocked=False
Maximized=True
ScreenUniCoords=0, 0, 0, 0
UndocCoords=0, 0, 0, 0

[ATC_AgentManager]
NumberofAgents=0

[ATC_Aircraft.0]
ActiveFlightPlan=False
RequestedFlightPlan=False
AcState=ACSTATE_REQUEST_TAXI_CLEARANCE_OUT_VFR_ATIS
NumberofWaypoints=0
ClearanceFlags=82
CtCur=CLEARANCE_NONE
WaypointNext=0
AltCleared=-1
HdgAssigned=-1
SquawkAssigned=4608
LandingSequence=LANDING_NONE
DepartureRequest=DEPARTURE_VFR_REQUEST_NONE
ParkingRequest=PARKING_NAME_NONE
ParkingTypeRequest=PARKING_TYPE_NONE
PatternLeg=PATTERN_LEG_NONE
ApproachIndex=-1
ApproachTransitionIndex=-1
ApproachRequestIndex=-1
ApproachTransitionRequestIndex=-1
RunwayIndex=-1
RunwayRequestIndex=-1
ParkingIndex=-1
FlightFollowing=FLIGHT_FOLLOWING_NO
AirspaceTransition=AIRSPACE_TRANSITION_NONE
BVAirspaceTransition=BV_TYPE_NONE
BVAirspaceTransitionReq=BV_TYPE_NONE
TakeoffSequence=TAKEOFF_SEQUENCE_NONE
LandingSequenceNumber=-1
TaxiRouteCurrent=-1
CruisingAltitude=-1
RequestedCruisingAltitude=-1
ExpectedAltitude=-1
AircraftSignature=1,0

[ATC_AircraftManager]
NumberofAircraft=1

[ATC_MessageSystem]
FrequencyNodes=0

[DateTimeSeason]
Season=Summer
Year=2019
Day=327
Hours=16
Minutes=00
Seconds=00
UseZuluTime=False

[SimVars.0]
Latitude=N51° 30' 17.81"
Longitude=E0° 3' 51.71"
Altitude=+000019.00
Pitch=0
Bank=0
Heading=-87.106811609119191075
PVelBodyAxis=0
BVelBodyAxis=0
HVelBodyAxis=0
XVelBodyAxis=0
YVelBodyAxis=0
ZVelBodyAxis=0
SimOnGround=True
OnPlatformHeight=-9999999999

[Avionics.0]
Comm1Active=124.850
Comm1Standby=124.850
Comm2Active=124.850
Comm2Standby=124.850
Comm3Active=124.850
Comm3Standby=124.850
Nav1Active=110.50
Nav1Standby=113.90
OBS1=360
Nav2Active=110.50
Nav2Standby=113.90
OBS2=360
Transponder=1234
ADFActive=890
ADF2Active=890
DMESelected=1
ComTransmit=1
ComReceiveBoth=False
Com1Receive=True
Com2Receive=False
Com3Receive=False
AudioNav1Listen=False
AudioNav2Listen=False
AudioMarkerListen=True
AudioDmeListen=False
AudioAdfListen=False
AudioAdf2Listen=False
AvionicsSwitch=True

[Slew.0]
Active=False

[Freeze.0]
Location=False
Altitude=False
Attitude=False

[Engine Parameters.1.0]
ThrottleLeverPct=0
PropellerLeverPct=0.99993896484375
MixtureLeverPct=0.99993896484375
Pct Engine RPM=0.25
MaxReachedEngineRPM=2018.3370438323020153
LeftMagneto=True
RightMagneto=True
GeneratorSwitch=True
CowlFlapPct=0
FuelPumpSwitch=False
CarbHeat/DeiceSwitch=False
EngineMasterSwitch=True
GlowPlugTemperaturePct=1

[Propeller.1.0]
prop_beta=0.34906585039886589561
prop_max_rpm_percent=0

[Fuel.0]
TankSelector=All
TankSelector1=All
Center=100
LeftMain=90
RightMain=90
LeftAux=100
RightAux=100
LeftTip=100
RightTip=100
Center 2=100
Center 3=100
External 1=100
External 2=100

[Systems.0]
BatterySwitch=True
StructuralDeiceSwitch=False
PropDeiceSwitch=False
Autobrakes=0
StandbyVacuum=False
PropSync=False
AutoFeatherSwitch=False
FlightDirector=False
PanelLights=False
LaunchBarSwitch=False
LaunchBarState=0
TailhookHandle=False
TailhookState=0
FoldingWingsHandle=False
FoldingWingsState=0, 0

[Gauges.0]
KollsmanSetting=29.921342849731445313
[BleedAir.0]
BleedAirSource=0

[Switches.0]
PitotHeat=False
BeaconLights=True
LandingLights=False
LogoLights=False
NavLights=False
PanelLights=False
RecognitionLights=False
StrobeLights=False
TaxiLights=False
WingLights=False
CabinLights=False
GlareshieldLights=False
PedestalLights=False

[AutoPilot.0]
MasterSwitch=False
WingLeveler=False
Nav1Lock=False
HeadingLock=False
HeadingValue=0
AltitudeLock=False
AltitudeValue=0
AttitudeHold=False
AirspeedHold=False
AirspeedValue=0
MachHold=False
MachValue=0
VerticalSpeedHold=False
VerticalSpeedValue=0
RPMHold=False
RPMValue=0
GlideslopeHold=False
ApproachHold=False
BackCourseHold=False
YawDamper=False
ToGa=False
AutoThrottleArm=False

```

--------------------------------

### Flight Simulator <Condition> Example

Source: https://docs.flightsimulator.com/html/Content_Configuration/Models/Model_Examples

This example demonstrates a <Condition> block that checks if a parameter 'STATE0_TIMER' exists and is greater than 0. If true, it calls the 'ASOBO_GT_Update' template.

```XML
<Condition>
    <Test>
        <And>
            <Arg Check="STATE0_TEMPLATE"/>
            <Greater>
                <Value>STATE0_TIMER</Value>
                <Number>0</Number>
            </Greater>
        </And>
    </Test>
    <True>
        <UseTemplate Name="ASOBO_GT_Update">
            <UPDATE_ONCE>True</UPDATE_ONCE>
            <UPDATE_CODE>(#SWITCH_POSITION_TYPE#:#SWITCH_POSITION_VAR#) 0 == if{ 1 (&gt;#SWITCH_POSITION_TYPE#:#SWITCH_POSITION_VAR#) }</UPDATE_CODE>
        </UseTemplate>
    </True>
</Condition>
```

--------------------------------

### Sim.cfg Example for Living Thing Variations

Source: https://docs.flightsimulator.com/html/Content_Configuration/SimObjects/Living_Things/Living_Things_sim_cfg

This code snippet demonstrates the structure of the [fltsim.N] section in a sim.cfg file, showing how to define different variations for a living thing. It includes parameters for title, model, texture, animation, and sound, with examples of how to specify variations by appending text to default folder names.

```config
[fltsim.0]
title=MyCompany_Crab
model=""
texture=""

[fltsim.1]
title=MyCompany_Crab_Red
model="Red" ; folder would be "model.Red"
texture="Red" ; folder would be "texture.Red"
```

--------------------------------

### Calling an RTC in Mission Intro (XML)

Source: https://docs.flightsimulator.com/html/Content_Configuration/Cameras/RTC/RTC_Definition_Examples

Illustrates how to initiate an RTC sequence at the beginning of a mission. This example shows a FlowStateAction that sets up initial conditions and then calls a specific RTCSequencer. It references multiple object IDs for actions and states.

```XML
<SimMission.FlowStateAction InstanceId="{7C4FE0D9-0507-471A-86E0-14014AC56E40}">
    <Skippable>True</Skippable>
    <FlowStateName>INTRO</FlowStateName>
    <StartActions>
        <SimMission.ObjectReference id="Generic_CommercialFlight_Intro" InstanceId="{BCA1197A-5B8B-429E-87BB-DF82AC659519}"/>
        <SimMission.ObjectReference id="ActiveCameraCockpit" InstanceId="{2D16485D-2707-45A5-B353-3951C262BF83}"/>
        <SimMission.ObjectReference id="DisablePushback" InstanceId="{6EDA22B2-43F2-40C3-8DFB-74E064DAACA1}"/>
        <SimMission.ObjectReference id="DisableATC" InstanceId="{32CF1B49-EA22-454D-8D5C-EB71D8FD213C}"/>
        <SimMission.ObjectReference id="WiseAFSSet" InstanceId="{43071EAB-D106-41CC-88D6-B113CDAE289B}"/>
    </StartActions>
    <EndActions>
        <SimMission.ObjectReference id="PREFLIGHT_GATE" InstanceId="{6649EAEA-D484-4308-ABD1-A16A4E14190F}"/>
    </EndActions>
</SimMission.FlowStateAction>
      
<SimMission.RTCSequencer InstanceId="{BCA1197A-5B8B-429E-87BB-DF82AC659519}">
    <Descr>Generic_CommercialFlight_Intro</Descr>
    <Shuffle>False</Shuffle>
    <Skippable>True</Skippable>
    <Actions>
        <SimMission.ObjectReference id="Generic_Airport_Intro" InstanceId="{18818CE1-18B4-4943-A8CC-D5362D943993}"/>
        <SimMission.ObjectReference id="Generic_Ground_Aircraft_Intro" InstanceId="{C49DCA0B-9080-4CBB-9C4F-EC293C438957}"/>
    </Actions>
</SimMission.RTCSequencer>
```

--------------------------------

### C# SimConnect Client Setup (.NET)

Source: https://docs.flightsimulator.com/html/Programming_Tools/SimConnect/Programming_SimConnect_Clients_using_Managed_Code

Demonstrates the necessary using statements for a C# SimConnect client. Requires .NET Framework 4.7 and a reference to Microsoft.FlightSimulator.SimConnect.

```csharp
using Microsoft.FlightSimulator.SimConnect;
using System.Runtime.InteropServices;
```

--------------------------------

### XML: Allow Zero EntryWeight if Total Weight is Non-Zero

Source: https://docs.flightsimulator.com/html/Content_Configuration/Environment/Living_World/Living_World_Config/Living_World_Configuration_Examples

This XML example shows that an EntryWeight of 0 is permissible for a ContainerEntry, as long as the total accumulated weight of all entries in the list is not zero. This allows an object to be excluded from random selection while maintaining valid configuration.

```xml
<FuelTrucks>
    <ContainerEntry ContainerTitle="ASO_FuelTruck01_Black" EntryWeight="1"/>
    <ContainerEntry ContainerTitle="ASO_FuelTruck01_White" EntryWeight="0"/>
</FuelTrucks>
```

--------------------------------

### Flight Control PID Parameters Example

Source: https://docs.flightsimulator.com/html/Content_Configuration/SimObjects/Aircraft_SimO/AI_Config_Definition

Illustrates example PID values for controlling aircraft behavior during flight. These PIDs manage throttle, pitch, roll, heading, and vertical speed to maintain target parameters.

```plaintext
throttlePID = 20.0, 0.3, 20.0, 20.0, 500.0
pitchPID = 1.0, 0.01, 2.0, 0.6, 5.0
rollPID = 1.0, 0.001, 1.0, 0.5, 8.0
headingPID = 1.0, 0.01, 1.0, 1.0, 20.0
verticalSpeedPID = 0.5, 0.1, 0.5, 200.0, 5000.0
nav_ex1PID = 3.0, 0.01, 2.0, 0.035, 50.0
nav_yawPID = 0.02, 0.00006, 0.006, 0.3, 3.0
glideSlopePID = 5.52, 1.0, 3.0, 2.0, 60.0
flightLevelPID = 10.0, 1.0, 10.0, 100.0, 1000.0
```

--------------------------------

### Aircraft Configuration File Example (*.cfg)

Source: https://docs.flightsimulator.com/html/Additional_Information/File_Formats/CFG_Files

An excerpt from an aircraft.cfg file demonstrating the basic structure of sections and parameters.

```cfg
[VERSION]
major = 1
minor = 0
[GENERAL]
atc_type = "MyManufacturer"
atc_model = "Simple"
Category =  "airplane"
performance = ""


```

--------------------------------

### RTCSequencer with GUID InstanceId

Source: https://docs.flightsimulator.com/html/Content_Configuration/Cameras/RTC/Using_RTCs

This XML example shows an RTCSequencer with a GUID assigned to the InstanceId field. This is necessary when replacing an existing RTCSequencer to ensure proper overriding.

```xml
<SimMission.RTCSequencer InstanceId="{18818CE1-18B4-4943-A8CC-D5362D943993}">
    <Descr>RTC_Airport_Intro</Descr>
</SimMission.RTCSequencer>
```

--------------------------------

### soundai.xml Structure and Example

Source: https://docs.flightsimulator.com/html/mergedProjects/How_To_Make_An_Aircraft/Contents/Audio/Audio_For_AI_Aircraft

This XML snippet demonstrates the structure of a typical soundai.xml file for AI aircraft. It includes Wwise package information and engine sound presets, mapping SimVars to Wwise events and Real-Time Parameter Controls (RTPCs).

```xml
<?xml version="1.0" encoding="utf-8" ?>
<!-- Copyright (c) Asobo Studio, All rights reserved. www.asobostudio.com -->
<SoundInfo Version="0.1">
    <WwisePackages>
        <MainPackage Name="Asobo_C152_AI"/>
    </WwisePackages>
    <EngineSoundPresets>
        <Sound WwiseEvent="Combustion" ConeHeading="180" FadeOutType="2" FadeOutTime="0.2" RPMMin="200" WwiseData="true" EngineIndex="1" >
            <WwiseRTPC SimVar="GENERAL ENG COMBUSTION SOUND PERCENT" Units="PERCENT OVER 100" RTPCReleaseTime="0.5" Index="1" RTPCName="SIMVAR_GENERAL_ENG_COMBUSTION_SOUND_PERCENT" />
        </Sound>
        <Sound WwiseEvent="Starter" FadeOutType="2" FadeOutTime="0.1" WwiseData="true" EngineIndex="1" >
            <WwiseRTPC SimVar="GENERAL ENG COMBUSTION SOUND PERCENT" Units="PERCENT OVER 100" RTPCReleaseTime="0.5" Index="1" RTPCName="SIMVAR_GENERAL_ENG_COMBUSTION_SOUND_PERCENT" />
        </Sound>
        <Sound WwiseEvent="CombustionStart" ConeHeading="180" WwiseData="true" EngineIndex="1" > 
            <WwiseRTPC SimVar="GENERAL ENG COMBUSTION SOUND PERCENT" Units="PERCENT OVER 100" RTPCReleaseTime="0.5" Index="1" RTPCName="SIMVAR_GENERAL_ENG_COMBUSTION_SOUND_PERCENT" />
        </Sound>
        <Sound WwiseEvent="CombustionStart" CustomSuffix="Propeller" ConeHeading="0" WwiseData="true" EngineIndex="1" >
            <WwiseRTPC SimVar="GENERAL ENG COMBUSTION SOUND PERCENT" Units="PERCENT OVER 100" RTPCReleaseTime="0.5" Index="1" RTPCName="SIMVAR_GENERAL_ENG_COMBUSTION_SOUND_PERCENT" />
        </Sound>
        <Sound WwiseEvent="Shutdown" ConeHeading="180" RPMMin="200" WwiseData="true" EngineIndex="1" >
            <WwiseRTPC SimVar="GENERAL ENG COMBUSTION SOUND PERCENT" Units="PERCENT OVER 100" RTPCReleaseTime="0.5" Index="1" RTPCName="SIMVAR_GENERAL_ENG_COMBUSTION_SOUND_PERCENT" />
        </Sound>
        <Sound WwiseEvent="Shutdown" CustomSuffix="Propeller" ConeHeading="0" RPMMin="200" WwiseData="true" EngineIndex="1" >
            <WwiseRTPC SimVar="GENERAL ENG COMBUSTION SOUND PERCENT" Units="PERCENT OVER 100" RTPCReleaseTime="0.5" Index="1" RTPCName="SIMVAR_GENERAL_ENG_COMBUSTION_SOUND_PERCENT" />
        </Sound>
        <Sound WwiseEvent="Propeller" ConeHeading="0" FadeOutType="2" FadeOutTime="0.2" RPMMin="200" WwiseData="true" EngineIndex="1" >
            <WwiseRTPC SimVar="GENERAL ENG COMBUSTION SOUND PERCENT" Units="PERCENT OVER 100" RTPCReleaseTime="0.5" Index="1" RTPCName="SIMVAR_GENERAL_ENG_COMBUSTION_SOUND_PERCENT" />
        </Sound>
    </EngineSoundPresets>
    <GroundSounds>

```

--------------------------------

### Microsoft Flight Simulator XML Configuration Example

Source: https://docs.flightsimulator.com/html/Additional_Information/File_Formats/XML_Files

An example of an XML file used in Microsoft Flight Simulator, showcasing the structure with declarations, elements, attributes, and comments. This file defines a flight challenge with various actions.

```xml
<?xml version="1.0" encoding="UTF-8"?>
<SimBase.Document Type="RTC_Challenge" version="1.0">
    <WorldBase.Flight>
    <!-- START Intro -->
       <SimMission.RTCSequencer InstanceId="{F9B4BD6B-8E0B-434C-9876-D859069EDE0A}">
            <Descr>RTC_Challenge</Descr>
            <NeedPreload>True</NeedPreload>
            <Shuffle>False</Shuffle>
            <Actions>
                <ObjectReference id="RTC_Airport_Overview" InstanceId="{347FAB01-05E1-432E-8A23-396052B7B77D}}"/>
                <ObjectReference id="RTC_POI_Tower" InstanceId="{344EC464-2B26-4C8B-A6E9-6D89E8BDD609}"/>    
                <ObjectReference id="RTC_Aircraft_Intro" InstanceId="{7B45E0FC-F507-4AFB-99EE-53DBE8291374}"/>
            </Actions>
        </SimMission.RTCSequencer>
    <!-- END Intro -->
    </WorldBase.Flight>
</SimBase.Document>
```

--------------------------------

### Define Wwise Packages (XML)

Source: https://docs.flightsimulator.com/html/Content_Configuration/Sounds/Sound_Examples

Specifies the Wwise packages to be loaded. This includes a main package and potentially additional packages. If not defined, the package name is inferred from the sound.xml file path. This is a structural definition for Wwise integration.

```xml
<WwisePackages>
    <MainPackage Name="MyCompany_MyAircraft"/>
    <AdditionalPackage Name="MyCompany_MyAircraft_Additional1"/>
    <AdditionalPackage Name="MyCompany_MyAircraft_Additional2"/>
</WwisePackages>
```

--------------------------------

### Configure a Flight Sim Contact Point (Example)

Source: https://docs.flightsimulator.com/html/Content_Configuration/SimObjects/Aircraft_SimO/flight_model/contact_points

Example demonstrating how to define a single contact point using 17 comma-separated values. The first value specifies the contact point type (e.g., wheel, float), followed by positional data, physical properties, and operational parameters. Ensure the number of defined points matches `max_number_of_points` for aircraft validity.

```text
point.0 = 1, -13, 0, -0.65, 750, 0, 0.523, 90, 0.296, 2.5, 0.794, 0, 0, 0, 165, 165, 1
```

--------------------------------

### Configure SimVar Sounds with Ranges (XML)

Source: https://docs.flightsimulator.com/html/Content_Configuration/Sounds/Sound_Examples

This example illustrates how to use the `<SimVarSounds>` element to play sounds based on SimVar values. It shows how to trigger sounds when a SimVar changes, or when its value falls within specific ranges (e.g., between 10 and 15, or above 25).

```XML
<SimVarSounds>
    <!--This sound will play every time the simvar value changes -->
    <Sound WwiseEvent="Sound_For_Test_1" WwiseData="true" SimVar="SIMVAR TEST 1" Units="PERCENT" Index="0"/>
    <!--This sound will play whenever the simvar value is between 10 and 15, and when it's over 25. -->
    <Sound WwiseEvent="Sound_For_Test_2" WwiseData="true" SimVar="SIMVAR TEST 2" Units="PERCENT" Index="0">
        <Range LowerBound="10.0" UpperBound="15.0"/>
        <Range LowerBound="25.0" />
    </Sound>
</SimVarSounds>
```

--------------------------------

### Configure Loading Screen Images and Tips

Source: https://docs.flightsimulator.com/html/Content_Configuration/SimObjects/Aircraft_SimO/aircraft_cfg

Sets images and accompanying text tips displayed during free flight loading. Supports PNG or JPEG images and localizable, category-specific tips.

```config
Tips0=TT:LOADING.TIPS.AIRCRAFTNAME_000
Tips1=TT:LOADING.TIPS.AIRCRAFTNAME_001
Tips2=TT:LOADING.TIPS.AIRCRAFTNAME_002
```

--------------------------------

### Base Template for Lighting Interactions

Source: https://docs.flightsimulator.com/html/Content_Configuration/Models/ModelBehaviors/TemplateExplorer/Asobo/Common/Lighting

Provides a foundational template for setting up various lighting interactions within the simulator. It establishes common parameters such as input event IDs and WWise prefixes, leveraging a base interaction template for unified input handling.

```xml
<Template Name="ASOBO_LIGHTING_Base_Template">
 <Parameters Type="Default">
 <INPUT_EVENT_ID_SOURCE>LIGHTING</INPUT_EVENT_ID_SOURCE>
 <WWISE_PREFIX>LIGHTING</WWISE_PREFIX>
 </Parameters>
 <UseTemplate Name="ASOBO_Interaction_Base_Template">
 <USE_INPUT_EVENT_ID>LIGHTING</USE_INPUT_EVENT_ID>
 </UseTemplate>
</Template>
```

=== COMPLETE CONTENT === This response contains all available snippets from this library. No additional content exists. Do not make further requests.