Version: 1.0.88.0
Frequency: Consistently
Severity: Low
Bug description:
Enum inputs as documented in the SDK are not accepted anymore:
Original code within airport in XML:
SDK documentation still mentioning this as a valid input:
https://docs.flightsimulator.com/msfs2024/html/5_Content_Configuration/Environment/Airports_And_Facilities/Airport_XML_Properties.htm#Start
Hello @Sasa
This was an issue on our end where helipad starts were following the same rules as runway starts for number field (1-36 and cardinal positions North/North-West/etc).
It has been addressed and now helipad starts number only accept numerical values, as it should. The documentation should be updated pretty soon.
I am not sure how you got this XML as the Scenery Editor doesn’t write such start number anyway, did you perhaps edited it by hand ? Please let me know so we can fix any remaining issue about this.
Regards,
Melvin
Hi Melvin! It’s from an older build so not sure anymore where is actually originates from. What I can say is for let’s say 50% certainty is that the Scenery Editor didn’t update these entries when re-saving the airport in MSFS2024.
Hello again @Sasa,
In fact, the start numbers that are not numerical are not supported and not read in the Scenery Editor, so if you try to load your airport those helipads should not have a start anymore.
Just to be clear, we never did support such start numbers, but we now we do print an error during build.
Could you please test to open your airport in the Scenery Editor with the latest patch and confirm that after saving again you no longer have invalid start number ?
Regards,
Melvin
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.
