Context:
MSFS2024 is rejecting model XML that is ok in MSFS2020 due to different constraints on Node ID’s permitted characters, i.e. Node ID’s containing ’ ’ (space) or ‘.’ (period) cause the model XML to fail for that component in MSFS2024 where it’s ok in MSFS2020.
I searched but couldn’t find any SDK docs that actually specify the allowed characters in the Node ID, although I did find a previous post where Asobo (I think) had erroneously used a ‘/’ (forward slash)
Similar MSFS 2020 issue: MSFS2020 does have some (undocumented?) constraints on Node ID characters e.g. ‘/’ is not permitted, but those constraints are different than 2024.
Bug description: as above
Repro steps:
If you have a working model XML component with a Node ID acceptable to MSFS2024, edit that Node ID to include a ‘.’ (period) in both the model XML and the GLTF file and the component will cease to function in MSFS2024. The same combined changes in MSFS2020 has no effect.
Can you elaborate on what you mean by “cause the model XML to fail”?
Do you have an error in the console?
I checked by modifying the WasmAircraft sample Gauges component and introduced a period in the node name but did not see any issue.
If you are able to provide a package that demonstrate the issue, I’ll have a look.
Sure, I’ll dig out an example from model XML that broke (I have hundreds). I’m not a modeller but I suspect Blender can add e.g. “.001” to the end of a node name if you copy it, because there are so many examples I see in gltf files from modellers I’ve partnered with.
The issues occur at least when using the Asobo templates for clickable buttons, rotating knobs, and draggable levers. The unwanted characters mean those interaction elements cease to be clickable/draggable.
TBH I’ve been cleaning up both Node names and Animation names, so I’m not entirely clear which of those causes which issue. I’m replacing non-alphanumeric chars (typically ‘space’ or ‘period’) with ‘underscore’ - hopefully that will meet some future spec.
In the meantime, a glitch I missed & had to fix yesterday in a plane I updated for MSFS2024 (LS4 glider) had a node name “Trim Handle” (containing a space) for the trim lever in the cockpit, this caused the lever to be non-draggable using the Asobo “ASOBO_GT_Interaction_WheelLeftDrag_Axis” template (I think, not the more specific trim lever template).
Well this is interesting. I suspect some change has already occurred in MSFS2024.
In the MSFS2020 plane (the K7 glider) we had the following ASOBO_GT_MouseRect template with the ‘period’ in the Node name, and that was definitely NOT clickable in MSFS2024.
Editting the Node name to “Tow_Release_001” in the model XML and the .gltf fixed the issue.
Today in MSFS2024 (1.2.8.0 ?) this code is now WORKING in both 2020 and 2024.
(pls note I editted the CALLBACK CODE to just write the L:var for the purposes of testing this today)
FWIW this was the accumulated checklist of changes for that plane. Having plowed through and tested a lot of these changes in multiple planes after feedback from multiple users I don’t think there’s much chance I had some fundamental confusion, but it’s always possible.
Possibly, this has already been fixed through another Devsupport or internal bug report.
Let me know, if the issue still occurs in some other context or if we can consider it fixed.
–