# Default Templates<no value>
The easiest way to plug in an instrument or switch using Model Behaviors is to use one or more existing template (either from the default ones or from the templates that you yourself have previously created). In the best case scenario, that means that you could implement your yoke with only the following code in the XML file:

``` xml
<UseTemplate Name="ASOBO_IT_HANDLING_Single_Yoke_Template">
</UseTemplate>
```

 

This will call the code defined in the following template that contains all the required logic to implement the Yoke:

``` codeblock
..\Asobo_EX1\Common\Interior\Templates\Handling.xml
```

 

That template contains a call to another template called `ASOBO_IT_HANDLING_Yoke_SubTemplate`, which defines a number of *default* parameters:

``` xml
<Template Name="ASOBO_IT_HANDLING_Yoke_SubTemplate">
    <Parameters Type="Override">
        <UseParametersFn Name="ASOBO_Get_Common_Parameters_Helper"/>
    </Parameters>
    <Parameters Type="Override">
        <Condition Valid="PART_ID_ONLY">
            <False>
                <UseParametersFn Name="ASOBO_PFN_Call_Overridable_ParametersFn_Helper">
                    <PFN_PARAM_DEFAULT>ASOBO_Yoke_Animation_Parameters</PFN_PARAM_DEFAULT>
                    <PFN_PARAM_NAME>HANDLING_YOKE_ANIMATION_PARAMETERS_FN</PFN_PARAM_NAME>
                </UseParametersFn>
            </False>
        </Condition>
    </Parameters>

</Template>
```

In the example above, the default parameters are not overridden because the animation name and node ID defined by the artists match the values that are being defined by default.

{{< callout context="note" title="NOTE" icon="outline/bulb" >}}

Default parameters are defined inside of the [`<Parameters Type="Default">`](../../general-template-xml-properties/#Parameters) tags. Previously the templates used `<DefaultTempateParameters>` however this has been depricated, and `<Parameters Type="Default">` should be used as they can be chained multiple times in a row, while `<DefaultTemplateParameters>` can only be used once by template/component.

{{< /callout >}}

 

If the animations and/or nodes are *not* named the same as the default parameters, then they can be overridden by setting their values Inside of the [`<UseTemplate>`](../../general-template-xml-properties/#UseTemplate) tag, for example:

``` xml
<UseTemplate Name="ASOBO_IT_HANDLING_Single_Yoke_Template">
    <ANIM_NAME_YOKE_X>Yoke_Anim_LR</ANIM_NAME_YOKE_X>
    <ANIM_NAME_YOKE_Y>Yoke_Anim_UD</ANIM_NAME_YOKE_Y>
    <NODE_ID>Yoke</NODE_ID>
</UseTemplate>
```

The default parameters of this template also contain a [`<Condition>`](../../program-template-xml-properties/#Condition) tag, which allows the template to have different behaviors depending on the value of a parameter. Here this is used to define an extra `NODE_ID` - if the yokes are in separate nodes, but it can also be used inside of the logic of the template itself. The `ASOBO_HANDLING_Yoke_SubTemplate` template then uses the same condition in its logic to define an extra component when this condition is true:

``` xml
<Condition Check="CREATE_TWO_NODES">
    <UseTemplate Name="ASOBO_GT_ComponentWith_PART_ID">
        <NODE_ID>#NODE_ID2#</NODE_ID>
    </UseTemplate>
</Condition>
```

This `<Condition>` can then be triggered by setting `<CREATE_TWO_NODES>` as follows:

``` xml
<UseTemplate Name="ASOBO_HANDLING_Yoke_Template">
    <CREATE_TWO_NODES>True</CREATE_TWO_NODES>
</UseTemplate>
```

It is also important to note that all the parameters defined are **inherited**:

``` xml
<Component ID="MyParentComponent">
    <UseTemplate Name="ASOBO_HANDLING_Yoke_Template">
        
    </UseTemplate>
    <Component ID="MyComponent">
        <Parameters Type="Default">
            <CREATE_TWO_NODES>True</CREATE_TWO_NODES>
        </Parameters>
        <UseTemplate Name="ASOBO_HANDLING_Yoke_Template">
            
        </UseTemplate>
        <UseTemplate Name="ASOBO_HANDLING_Yoke_Template">
            
        </UseTemplate>
        <Component ID="MyFirstChildComponent">
            <Parameters Type="Override">
                <CREATE_TWO_NODES>False</CREATE_TWO_NODES>
            </Parameters>
            <UseTemplate Name="ASOBO_HANDLING_Yoke_Template">
                
            </UseTemplate>
        </Component>
        <Component ID="MySecondChildComponent">
            <Parameters Type="Default">
                
                <CREATE_TWO_NODES>False</CREATE_TWO_NODES>
            </Parameters>
            <UseTemplate Name="ASOBO_HANDLING_Yoke_Template">
                
            </UseTemplate>
        </Component>
    </Component>
</Component>
```

Note that, once defined, a parameter cannot be "undefined". It can only be overridden by giving it a new value inside a [`<Parameters Type="Override">`](../../general-template-xml-properties/#Parameters), or directly inside of a `<UseTemplate>` tag.

 

As a rule of thumb, when using the default templates, you should try to avoid using templates that include "**Subtemplates**" in their names, as those are meant to be called by going though another template. They can be called directly, but doing so will often mean that you are missing some default parameters that would have been set by that template, which can cause the template not to work. In addition, you should note that templates stored in the [Generic](../../templateexplorer/asobo/generic/index-page/) subfolder are generally building blocks templates that are meant to be used to create other templates. They do not implement any specific instrument on their own.

 

 

### Text In Default Templates

Many of the templates will require you to include some text as part of the input elements for the template. For example, the [ASOBO\_CT\_Switch\_Template](../../templateexplorer/asobo-ex1/common/shared/utils/interaction/interaction-templates/#ASOBO_CT_Switch_Template) has the element `<TOOLTIPS_TITLE>` which gives a tooltip string to be displayed when the user interacts with the switch. This would be used something like as follows:

``` xml
<UseTemplate Name="ASOBO_IT_Switch_Template">
    <IN_BASE_NAME>SWITCH_ADJUSTMENT_R</IN_BASE_NAME>
    <IE_NAME>RIGHT_PEDAL_ADJUSTEMENT</IE_NAME>
    <GET_SETTINGS>BACK_NEUTRAL_FRONT_Settings</GET_SETTINGS>
    <TOOLTIPS_TITLE>@TT_Package.RIGHT_PEDAL_SWITCH</TOOLTIPS_TITLE>              
</UseTemplate>
```

Now, if you are using *localised* text, then you need do nothing more, and this will work perfectly fine. However, if you wish to use **plain text** then you will have to do things slightly differently, depending on whether you are using the legacy *[Asobo](../../templateexplorer/template-explorer/#h2)* templates, or the MSFS 2024 *[Asobo\_EX1](../../templateexplorer/template-explorer/#h1)* templates.

 

For **legacy** templates, you can simply include the text in single quotes `''`, for example:

``` xml
<UseTemplate Name="ASOBO_LIGHTING_Switch_Light_Cabin_Template">
    <NODE_ID>LIGHTING_Switch_Light_Cabin_1</NODE_ID>
    <ANIM_NAME>LIGHTING_Switch_Light_Cabin_1</ANIM_NAME>
    <SIMVAR_INDEX>3</SIMVAR_INDEX>
    <SIMVAR_INDEX_2>4</SIMVAR_INDEX_2>
    <TYPE>ToggleSimvars</TYPE>
    <TT_STATE_1ST>(R:1:@TT_Package.GT_STATE_LEFT)</TT_STATE_1ST>
    <TT_STATE_2ND>(R:1:@TT_Package.GT_STATE_RIGHT)</TT_STATE_2ND>
    <TT_DESCRIPTION_ID>@TT_Package.LIGHTING_SWITCH_CABIN_ACTION_SET</TT_DESCRIPTION_ID>
    <TOOLTIP_TITLE>'Cabin Light Left'</TOOLTIP_TITLE>
</UseTemplate>
```

 

For the current **EX1** templates, not only must you include the text in single quotes `''`, you must also wrap the text element(s) in the `<SaveParameters>` parent element, as shown in the example below:

``` xml
<UseTemplate Name="ASOBO_IT_Switch_Template">
    <IN_BASE_NAME>SWITCH_ADJUSTMENT_R</IN_BASE_NAME>
    <IE_NAME>RIGHT_PEDAL_ADJUSTEMENT</IE_NAME>
    <GET_SETTINGS>BACK_NEUTRAL_FRONT_Settings</GET_SETTINGS>
    <SaveParameters ID="Interaction_Parameters">
        <TOOLTIPS_TITLE>'RIGHT PEDAL ADJUSTEMENT'</TOOLTIPS_TITLE>
        <TOOLTIPS_TITLE_IS_DYNAMIC>True</TOOLTIPS_TITLE_IS_DYNAMIC>
    </SaveParameters>    
</UseTemplate>
```