I generated a taxi sign at an airport, but it doesn’t appear in the sim.
I’ve used version 1.0.1 and the latest version of the FS2024 SDK, and I’ve noticed it happening in both versions. The Scenery Editor window shows no errors.
Has anyone else experienced this? I’m going to try building a test project somewhere else (e.g. maybe an airport in the Caribbean or Europe) to see if there’s a chance taxi signs can’t be added in certain regions.
Mods / experienced forum navigators: my apologies in advance if I missed anything or asked a question I shouldn’t have. I welcome corrections and constructive criticism.
UPDATE
Spun up a random project and WAS able to add and see a new taxi sign. Will probably try a random project in the same geo region (my airport’s in the US), will see if small airports have taxi sign rendering issues.
This seems to be a problem when trying to add a taxi sign at default airports which have none. I might be wrong?
I’ve had this happen to me before (in 2020, not 2024), and for me, what fixed it was deleting the taxi sign and adding it back. I have no idea why it wouldn’t show up sometimes.
I’ve moved the topic to [MSFS 2024] Bug Reports and logged the issue, as I was able to replicate this behavior on fictional airports or airports without default taxiway signs.
I’ve encountered this as well. I started an msfs 2024 airport project to load on top of (and thereby edit my view of) an existing 3rd party msfs 2020 airport, in msfs 2024. If I have the msfs 2020 airport active in the sim, then load the 2024 project into the scenery editor the taxisigns in my project display and I can edit them. However, if I open my project on top of the stock msfs 2024 airport (msfs 2020 version not loaded) only the wireframes appear. All of the taxisign info in my xml shows up in Properties for each sign, but only the wireframes are visible. If I open just the 2024 stock version of the airport by itself, the stock taxisigns are visible. In both the stock msfs 2024 airport, and the 2020 3rd party airport, the visible signs show as coming from the same path to asobo_props.bgl (which is now streamed vs local). Using the latest 1.2.2 SDK.
The SDK itself has nothing to do with the issue - it is related to the EXE.
Can you please confirm if you are using SU1 1.3.13.0 and still seeing this problem?
