Altitude offset ignored if altitudeIsAgl="FALSE"

Version: 1.2.7.0

Frequency: Consistently

Severity: High
(Low - quality of life, workflow optimization, rare enough to not impact production, etc…
High - critical but workarounds are available, important feature not working as expected, frequent enough to impact production
Blocker - prevents from working on the project, prevents from releasing the product)

Marketplace package name: ENSH Svolvaer by Wombii

Context: 2020 project converted to 2024 and edited using 2024 project editor.

Similar MSFS 2020 issue: insert url here if applicable

Bug description:
Altitude offset of scenery object is ignored when altitudeIsAgl=“FALSE”. I have many objects, for example approach light masts, that need to stay at a fixed elevation because they need to match their lightsupports and lightrows, since lightsupports use sealevel-referenced altitude. If the scenery object does not also use sealevel-referenced altitude, the light might not match the scenery object at different graphics settings.
This worked fine in 2020, but in 2024 the scenery object will snap back to sealevel, even though the offset altitude is set.

Repro steps:
1: Like in 2020, place object in scenery editor. Give it a recognizable name. Save. Close project. Open the xml, search for the object and change altitudeIsAgl=“TRUE” to altitudeIsAgl=“FALSE”. Save xml file.
2: Open project in scenery editor. Change elevation of the object. Notice it seems to work fine. Save and close the project. Notice in xml file that the altitude of the object has been correctly saved.
3: Open project in scenery. Notice the object is now visually back at sealevel.

Attachments:



Private attachments: Send a PM to @PrivateContent with the link to this topic and the link to download your content

2 Likes

Hello,

This has been fixed in the SU5 flighting (1.7.10.0).
Can you confirm ?

Regards,
Boris

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.