Context: Any airport modification in Developer Mode
Similar MSFS 2020 issue: unknown
Bug Description and Repro steps: Open Developer Mode. Open an airport in free flight. In the Scenery Editor, click the Airport entry, then Properties, then Generate Taxiway Signs. Taxi signs are generated in the proper locations but the signs for taxiways leading to a runway will inconsistently refer to that runway if more than one intersecting runway is present. In other words, one runway’s signs will be correct, but the other runway’s signs will refer to that first runway. For example, KGEG (Spokane WA) default airport has 8-26 and 3-21. All automatically generated taxiway signs will read 8, 8-26, 26-8 and 26. No signs will reference 3-21, but rather 8-26. All taxiway signs that refer to taxiway-taxiway intersections are correct.
I’m not sure I understand the issue. Could you please share a few screenshots (or a video) and point out where the 3-21 taxiway signs are expected to be displayed?
Thanks. Will do and get back to you. This is happening with generating signs for an existing MSFS 2020 project in 2024. Do you think that having some taxi signs already is the cause? I’m going to also test deleting all existing signs before generating new ones.
Attached is a zip file for KOKC that was converted to MSFS 2024 from an MSFS 2020 project. Included, there is a screenshot of a runway-taxiway intersection, a folder with the MSFS 2024 project files and a folder with the compiled MSFS 2024 airport package.
These files were originally created from the default MSFS 2020 airport. I’ve checked the originals and they are okay. I haven’t had a chance yet to experiment with generating signs with either a previous delete of existing signs or without.
Did you use a tool other than the Project Editor to create your airport in MSFS2020 and generate the taxiway paths?
I can reproduce the issue, but only with your project.
When I create an airport from scratch in MSFS2020 and import it into MSFS2024, I don’t see the issue. So I’m not sure yet what’s causing it.
Some were created with Airport Design Editor for MS2020, some with the SDK to airport app:
and even some with the short-lived 2020 World Hub to produce the initial XML. All editing was done in MSFS 2020 after that. The final 2020 package and project was created with MSFS 2020 then opened and edited in MSFS 2024 to create the new package and project.
It’s been a few years since most of the original 2020 projects were created, so I do know how each was produced from the 2020 default airport BGL file.
It’s somewhat of an obscure issue and looking through the individual 2020 XML files, I don’t see anything that jumps out as odd. I guess that I can either avoid the Generate Taxiways option.
Also, did you try deleting all existing taxiway signs in my KOKC project in 2024 and then generating new signs? I didn’t see a difference, but maybe you will.
Thanks for the response. I just uncovered the behavior almost by accident, since most of my old MSFS 2020 projects have a complete set of correct taxiway signs. However a a few MSFS 2024 projects needed signs to match taxiway updates that have occurred in real world airports, so I tried the Generate Signs option. At first I only audited the taxiway-taxiway intersection signs and they all were correct. But the I checked the runway-taxiway intersection signs.
I’ll keep poking around to see whether I can see a pattern in the occurrence of this issue.
