Build fails when SceneryObject has "SnapToBuilding" and "NoSnow" elements

[MSFS 2024] Bug Reports SDK: Tools/Samples/Documentation
1

Version: 1.1.9.0

Frequency: Consistently

Severity: High

Marketplace package name: if applicable

Context:
Building a project containing a scenery package with a SceneryObject that has the “SnapToBuilding” and “NoSnow” properties.

Similar MSFS 2020 issue:
n.a.

Bug description:
Build fails with error:

ERROR: #C2033 XML Parse Error (line, column, error)
ERROR: line=102, col=11, Element 'NoSnow' is unexpected according to content model of parent element 'SceneryObject'.
Expecting: Beacon, Effect, GenericBuilding, LibraryObject, VisualEffectObject, Trigger, Windsock, SimObject, WorldScript, CarParking, SimPropContainer, Decal, AttachedObject.

ERROR: #C2606 Schema errors detected, compilation failed!
ERROR: #C2034 XML Parse Fatal Error (line, column, error)
ERROR: line=151, col=0, Validate failed.

ERROR: #C2430 Unrecoverable error parsing XML!
ERROR: #C2006 Parse failed  (0x80004005)
BGLCompiler | CompileMemory failed
PackageBuilder | Package 'test' have encountered errors during _EndTreatCommands. See attached
PackageBuilder | EndExecuteCommandsForPackage : Failed to build package test

Example of an offending SceneryObject element:

	<SceneryObject parentGroupID="3" groupIndex="1" lat="46.69701011545040" lon="9.43650767532583" alt="14.88019778635612" pitch="0.001544" bank="-0.001837" heading="27.830910" imageComplexity="VERY_SPARSE" altitudeIsAgl="TRUE" snapToGround="FALSE" snapToNormal="FALSE">
		<SnapToBuilding/>
		<NoSnow/>
		<LibraryObject name="{E10E6A89-1D17-4ABF-A1B4-6A8674B085AA}" scale="1.000000"/>
	</SceneryObject>

Repro steps:

  1. Create scenery project containing a scenery object where properties “Snap to building” and “No Snow” are selected
  2. Build the project

Attachments:
bug

2

Also, it looks like the “Snap to Building” property is undocumented:

https://docs.flightsimulator.com/msfs2024/html/2_DevMode/Scenery_Editor/Objects/Scenery_Objects.htm

3

Hello,

We fixed this in the current flighting SU1 update (1.3.10.0)
Can you confirm me that it’s fixed for you as well?

Regards,
Boris

4

Cannot test with 1.3.10 atm as I’m on the latest beta. And it looks like this is still broken for me with 1.3.13.0 and SDK 1.2.3.

5

Hello,
Can you try cleaning your package using the “Clean All” option in the Project Editor?

Before saving, be sure to uncheck those options, build your scenery, and then try enabling them again.

If the issue persists, we will need your project for further investigation.
See 3) Provide Private Content for instructions.

Regards,
Boris

6

After some more testing it looks like it works, but only if the <NoSnow/> element is defined before the <SnapToBuilding/> element.

E.g. this will throw a compile error just like the one described:

	<SceneryObject groupIndex="8" lat="47.38875863951765" lon="8.05860933629778" alt="0.00000000000000" pitch="0.000027" bank="-0.000027" heading="-179.999991" imageComplexity="VERY_SPARSE" altitudeIsAgl="TRUE" snapToGround="FALSE" snapToNormal="FALSE">
		<SnapToBuilding/>
		<NoSnow/>
		<LibraryObject name="{177FD0FB-0F55-4483-7E2D-87270EC97DCF}" scale="0.100000"/>
	</SceneryObject>

But this won’t:

	<SceneryObject groupIndex="8" lat="47.38875863951765" lon="8.05860933629778" alt="0.00000000000000" pitch="0.000027" bank="-0.000027" heading="-179.999991" imageComplexity="VERY_SPARSE" altitudeIsAgl="TRUE" snapToGround="FALSE" snapToNormal="FALSE">
		<NoSnow/>
		<SnapToBuilding/>
		<LibraryObject name="{177FD0FB-0F55-4483-7E2D-87270EC97DCF}" scale="0.100000"/>
	</SceneryObject>

It’s not an issue when using the Scenery Editor as it will insert the elements in the expected order. But for people that want to manipulate the XML directly this is very relevant and unfortunately there is zero info in the documentation about any mandatory order to be followed for these two elements (and “SnapToBuilding” is still completely undocumented btw).

1 Like
7

Hello,

You’re right!
I have logged an issue for this.

Thank you

Regards,
Boris

1 Like
8

Hello,

This should be fixed in SU2 (currently in flighting).

Can you confirm if the issue is resolved?

Regards,
Boris

9

This topic has been automatically closed after 60 days of inactivity since it was marked as fixed.

If there is important new information about this same report, you can use the “Request reopen” button below to ask the moderation team to review it again.
For other issues or broader discussion, please open a new topic in the appropriate category.