Sort of invalid/problematic XML in (at least) the 146-100 VC?

Laurreth

On line 15439 and following of justflight-aircraft-146\SimObjects\Airplanes\JF_146_100\model\JF_146_100_VC.xml, you have that content:

		<!-- <Component ID="OVHD_ELEC_DC_sel" Node="OVHD_ELEC_DC_sel"> 
			<UseTemplate Name="ASOBO_GT_Knob_Finite_Code">
				<ANIM_NAME>OVHD_ELEC_DC_sel</ANIM_NAME>
				<PART_ID>OVHD_ELEC_DC_sel</PART_ID>
				<ANIM_CODE>
					(L:OVHD_ELEC_DC_sel, bool) 10 *
				</ANIM_CODE>
				<ANTICLOCKWISE_CODE>
					(L:OVHD_ELEC_DC_sel, enum) 0 == if{ 7 (>L:OVHD_ELEC_DC_sel, enum) } els{ (L:OVHD_ELEC_DC_sel, enum) -- 0 max (&gt;L:OVHD_ELEC_DC_sel, enum) }
				</ANTICLOCKWISE_CODE>
				<CLOCKWISE_CODE>
					(L:OVHD_ELEC_DC_sel, enum) 7 == if{ 0 (>L:OVHD_ELEC_DC_sel, enum) } els{ (L:OVHD_ELEC_DC_sel, enum) ++ 7 min (&gt;L:OVHD_ELEC_DC_sel, enum) }
				</CLOCKWISE_CODE>
				<ANIM_LENGTH>70</ANIM_LENGTH>
				<WRAP>True</WRAP>
				<TOOLTIPID></TOOLTIPID>
				<WWISE_EVENT>selector_volt_amp_source</WWISE_EVENT>
			</UseTemplate>
		</Component>
		
		<Component ID="OVHD_ELEC_AC_sel" Node="OVHD_ELEC_AC_sel"> 
			<UseTemplate Name="ASOBO_GT_Knob_Finite_Code">
				<ANIM_NAME>OVHD_ELEC_AC_sel</ANIM_NAME>
				<PART_ID>OVHD_ELEC_AC_sel</PART_ID>
				<ANIM_CODE>
					(L:OVHD_ELEC_AC_sel, bool) 10 *
				</ANIM_CODE>
				<ANTICLOCKWISE_CODE>
					(L:OVHD_ELEC_AC_sel, enum) 0 == if{ 7 (>L:OVHD_ELEC_AC_sel, enum) } els{ (L:OVHD_ELEC_AC_sel, enum) -- 0 max (&gt;L:OVHD_ELEC_AC_sel, enum) }
				</ANTICLOCKWISE_CODE>
				<CLOCKWISE_CODE>
					(L:OVHD_ELEC_AC_sel, enum) 7 == if{ 0 (>L:OVHD_ELEC_AC_sel, enum) } els{ (L:OVHD_ELEC_AC_sel, enum) ++ 7 min (&gt;L:OVHD_ELEC_AC_sel, enum) }
				</CLOCKWISE_CODE>
				<ANIM_LENGTH>70</ANIM_LENGTH>
				<WRAP>True</WRAP>
				<TOOLTIPID></TOOLTIPID>
				<WWISE_EVENT>selector_volt_amp_source</WWISE_EVENT>
			</UseTemplate>
		</Component>		 -->

The problematic thing in there is the use of -- in the anticlockwise code which may or may not upset XML parsers because it potentially conflicts with XML comments. From all I know, you would need to wrap the code in CDATA to make it "proper".

Martyn

Thanks for reporting this. We've confirmed that it works fine within MSFS model behaviour XML.