### Example GUID Usage in cameras.cfg Source: https://docs.flightsimulator.com/msfs2024/html/1_Introduction/Using_The_SDK.htm?agt=index This example shows how a unique GUID is used to identify a camera definition within the cameras.cfg file. Ensure all GUIDs are unique. ```ini Guid = "{195EAB58-9E4A-1E2A-A34C-A8D9D948F078}" ; Camera definition unique identifier. This GUID must be unique. ``` -------------------------------- ### SimConnect.cfg Example Configurations Source: https://docs.flightsimulator.com/msfs2024/html/6_Programming_APIs/SimConnect/SimConnect_CFG_Definition.htm This example shows two different configurations for the SimConnect.cfg file, demonstrating the use of different protocols and settings for client connections. ```cfg [SimConnect.0] Protocol=Pipe Port=Custom/SimConnect Address=127.0.0.1 [SimConnect.1] Protocol=Ipv6 Port=501 Address=127.0.0.1 ; Further connections here if required ``` -------------------------------- ### Get Procedure Auto Start/Shutdown Parameters Source: https://docs.flightsimulator.com/msfs2024/html/5_Content_Configuration/Models/ModelBehaviors/TemplateExplorer/Asobo_EX1/Common/Shared/Utils/Procedures/Common/Utils.html Defines parameters for engine auto start and shutdown procedures. Use 'Default' for basic setup, 'Override' for conditional logic, and 'AUTO_START_SHUTDOWN_CODE' for combined logic. ```XML #AUTO_START_CODE# (>K:ENGINE_AUTO_START) #AUTO_SHUTDOWN_CODE# (>K:ENGINE_AUTO_SHUTDOWN) p0 if{ #AUTO_START_CODE# } els{ #AUTO_SHUTDOWN_CODE# } #AUTO_START_SHUTDOWN_CODE# 1 p0 Float True ENGINE_AUTO_START 1 False ENGINE_AUTO_SHUTDOWN 0 False ``` -------------------------------- ### Starter Configuration Source: https://docs.flightsimulator.com/msfs2024/html/5_Content_Configuration/Models/ModelBehaviors/TemplateExplorer/Asobo/Common/Inputs/Electrical_Inputs.html Defines the behavior for starter toggling, activation, and setting. Includes bindings for direct control and toggling all starters. ```XML #ON_BEFORE_SET# #SET_EVENT# #ON_AFTER_SET# #ON_STATE_CHANGED# p0 1 (>O:ForceNotHeld) (#INPUTEVENT_VAR_TYPE#:#INPUTEVENT_VAR_NAME#) ! 1 (>O:ForceNotHeld) 1 1 (>O:ForceNotHeld) 0 1 (>O:ForceNotHeld) p1 1 (>O:ForceNotHeld) (B:ELECTRICAL_Starter_#STARTER_ID#) ! 1 (>O:ForceHeld) p1 1 (>O:ForceNotHeld) p1 1 (>O:ForceHeld) p1 ``` -------------------------------- ### SimPropContainer GUID Element Example Source: https://docs.flightsimulator.com/msfs2024/html/5_Content_Configuration/Environment/SimProp_Containers/SimPropContainer_XML_Properties.htm Provides a GUID for the SimPropContainer object, used as a reference in other files. ```xml {FDE1EC0B-7021-45E9-AC3B-066E307B4979} ``` -------------------------------- ### Acquire Camera - SimConnect_CameraAcquire Source: https://docs.flightsimulator.com/msfs2024/html/6_Programming_APIs/SimConnect/API_Reference/Camera/SimConnect_CameraAcquire.htm This example demonstrates how to acquire the add-on camera. Note that the camera may not be immediately usable on acquisition. ```C++ HANDLE hSimConnect = NULL; SimConnect_CameraAcquire(hSimConnect) ``` -------------------------------- ### Light Definition Example Source: https://docs.flightsimulator.com/msfs2024/html/5_Content_Configuration/CFG_Files/systems_cfg.htm This is an example of how to define a light in the configuration file. It includes parameters like name, type, index, local position, rotation, effect file, and potentiometer index. ```cfg lightdef.18 = Name:light_strobe Type:4 #Index:0 #LocalPosition:-1.2,0.65,14.0 #LocalRotation:0,0,0 #EffectFile:fx_cockpit_small_yellow, #PotentiometerIndex:2 ``` -------------------------------- ### RTCSequencer with InstanceId GUID Source: https://docs.flightsimulator.com/msfs2024/html/5_Content_Configuration/Cameras/RTC/Using_RTCs.htm This example shows an RTCSequencer with a valid GUID assigned to the InstanceId field. The GUID must be enclosed in curly braces and be in uppercase. ```xml RTC_Airport_Intro ``` -------------------------------- ### Example Services.xml Configuration Source: https://docs.flightsimulator.com/msfs2024/html/5_Content_Configuration/Navigation_Services/Services_XML_Properties.htm An example of a Services.xml file with multiple registered services, including passenger, boarding, skydive, medic, and hoist services. ```xml ``` -------------------------------- ### Reference Interaction GUIDs Source: https://docs.flightsimulator.com/msfs2024/html/5_Content_Configuration/CFG_Files/navigation_graph.htm?agt=index Add one or more GUID references to `` elements, numbered sequentially starting from 0. ```cfg interactionGUID.n = ``` -------------------------------- ### Get SimVar Value Examples Source: https://docs.flightsimulator.com/msfs2024/html/6_Programming_APIs/JavaScript/Simvar.htm Examples demonstrating how to retrieve different SimVar values based on instrument state. ```javascript switch (this.mapRotationMode) { case EMapRotationMode.DTKUp: compass = SimVar.GetSimVarValue("GPS WP DESIRED TRACK", "degrees"); break; case EMapRotationMode.HDGUp: compass = Simplane.getHeadingTrue(); break; case EMapRotationMode.TrackUp: compass = SimVar.GetSimVarValue("GPS GROUND TRUE TRACK", "degrees"); break; default: compass = 0; break; } ``` -------------------------------- ### Combined 'While' and 'Do' Loop Source: https://docs.flightsimulator.com/msfs2024/html/5_Content_Configuration/Models/ModelBehaviors/Program_Template_XML_Properties.htm Demonstrates using a 'while' loop for setup and a 'do' loop for execution. This allows 'while' to configure parameters used in the 'do' loop. ```xml ID 1 1 VALVE_ID_#ID# ``` -------------------------------- ### Example Material Definition in material.lbl Source: https://docs.flightsimulator.com/msfs2024/html/5_Content_Configuration/LBL_Files/material_lbl.htm This example shows a single material definition within the material.lbl file, including its name, GUID, and associated labels for filtering. ```json { "LabeledMaterials": [ { "Name": "Dynamic_Material_1", "MaterialGUID": "{F519090D-FF85-4C30-A6BB-8AECBD126541}", "Labels": [ { "Key": "Activity", "Values": [ "CAR" ] }, { "Key": "Continent", "Values": [ "Europe" ] } ] } ] } ``` -------------------------------- ### Complete WASM System Configuration Example Source: https://docs.flightsimulator.com/msfs2024/html/6_Programming_APIs/WASM/Creating_WASM_Systems.htm Provides a comprehensive example of configuring multiple WASM systems, including different module paths and system names, within the systems.cfg file. ```cfg [WASM_SYSTEM.0] ModulePath=SimObjects/Airplane/MyCompanyWasm_Aircraft/common/wasm/myModule.wasm SystemName=mySystem ParameterString=AircraftVariationName, 1 [WASM_SYSTEM.1] ModulePath=SimObjects/Airplane/MyCompanyWasm_Aircraft/common/wasm/myModule.wasm SystemName=mySecondSystem [WASM_SYSTEM.2] ModulePath=SimObjects/Airplane/MyCompanyWasm_Aircraft/presets/mycompany/presetName/wasm/myModuleInPreset.wasm SystemName=presetSystem ``` -------------------------------- ### Starter Template - Switch Interaction Source: https://docs.flightsimulator.com/msfs2024/html/5_Content_Configuration/Models/ModelBehaviors/TemplateExplorer/Asobo/Common/Subtemplates/Electrical_Subtemplates.html Configures a starter for 'SWITCH' interaction type. Includes conditions for cover states and uses ASOBO_GT_Switch_Covered for handling switch logic and animations. ```XML