Context: There are no issues when in Scenery Editor, only when package is built and placed in Community folder and a flight is started.
Bug description: I created custom lights for my runway and taxiways for my airport project. They both use the same exact model, but have a different color lens. I am using Light Rows for the taxiway lights (runway lights as well). I attached my custom light as the mesh and they show up fine when in Dev mode/Scenery Editor but when package is built and placed in Community folder, they only show up intermittently at start of flight (about 25% of time). The runway lights always show up fine. If the taxiway light mesh does not show up, I found that if I drone away from airport maybe 1/4 to 1/2 mile, they are visible when I drone back to the airport.
*This was also happening in SU2 but I waited until SU3 Beta to see if it was associated with a similar issue reported about mesh lights not being visible.
Repro steps:
Load in my airport, if taxiway lights are not showing up, drone away from airport 1/4-1/2 mile and return. They should then show up again. They might show up at the start of flight intermittently.
Attachments:
Shot of runway and taxiway lights (all visible):
Hi! I have the same issue. When i start a flight at first time taxiway center light objects, PAPI lights objects etc. not showing up, but their lights are visible. After i hit ESC and End Flight, and start a new flight the objects come back. I have experienced this in SU2 and in SU3 as well.
This is still an issue in the latest SU3 Beta and I was wondering whether this would still make Su3 or if at least SU4
I reported this in November and it is still an issue 8 months later…
At first I didn’t know that this also affected custom native 2024 lightrows. I thought it was a backwards comp issue and only default items where affected. However, now that we are trying to start working with 2024 and doing native projects, I was quite puzzled to find out that not even fully custom lightrows work, although they work prefectly fine in the 2024 editor. Quite frustrating to be honest. I can live with default PAPIs not showing up as a backwards comp issue. But not having taxiway lights is quite an issue and not of high priority as this threads states but, in our opinion, a severe blocker…
This still does NOT work in SU4 Beta 2. I find that spawning at the gate - the light meshes do not render - just floating orbs. If you spawn on the runway, the light fixture meshes render most of the time, but not always.
Also there is a an irregularity of the use of the fitting at runway end lights. Placing a standard runway, and enabling end lights will mix flush mount fixtures with raised pedestal fixtures. Why does that happen?. It is so annoying. I cannot get a consistent type of fixture to work
Are you talking about default taxi light mesh or custom (gltf made by you) taxi light mesh ?
There is another issue about default lights meshes (runway end light / VASI etc) not showing up → here.
Happens with default 2024 light meshes. They only start showing up when i load a saved project into the scene, if i just spawn into a normal fight at the ramp /gate , the light meshes are missing. Sometimes if i spawn on the runway itself it also renders the light meshes, but even there its sometimes hit and miss.
If i fly away from the airport and return after some time , the light meshes have rendered (taxi , runway, approach and vasi )
its like some lod bug that fixes itself on a reload of the airport or something .
Then there is the issue of the types of meshes I’ve shown you in my screenshot. I’m not sure why end lights renders in a mix of flush mounted meshes and ones with pedestals..
PS.I’m not a proff airport developer. Just trying to customize my own in my spare time.
Another example : Just spawned on the runway. Meshes shows up, but look at the inconsistency of the type, there are two meshes that are not consistent with the flush mounted meshes. Not sure what causes this. These are all default Asobo assets.
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.
