In this example the beacon light is buried below the tower base inside the procedural building, and I could only see it by clipping through the building walls in VR + walkaround mode:
This was the result after a direct flight from LSMD. On approach I could spot the beacon from very far already but then at around 2 miles it suddenly vanished and when I arrived at the destination the tower was not yet rendered and only appeared after a while…
Here’s the custom airport (hospital helipad) package to reproduce:
I have mirrored the graphics settings you mentioned and flew from distance to the scenery but can’t yet replicate.
This sounds more like an issue with Object LOD switch, like the node the light affect is supposed to be attached to is missing in one LOD, leading the light to be placed at (0,0,0).
Can you please record a video of the issue occurring?
Ideally, record as you approach the beacon, with dusk/sunset lighting so the beacon is clearly visible.
And please have the Debug LODs debug open, with the Model name filter set to “RotatingBeacon_Tower”, so we can track what LOD is used when you see the beacon disappear.
If it’s related to an object LOD of the stock beacon tower that’s missing the attach point I imagine it should be easy for you to verify this from looking at the model source itself, no?
Anyway, I will try to record a video with the requested debug info the next time I get a chance.
One thing I also notice is a consistent, late rendering of the objects contained in the package I attached earlier. In fact, the main objects (beacon tower and rooftop helipad SPC) only pop into view after I’ve arrived at the location and wait for another 10-20 seconds - this is after flying a relatively slow approach at 100-120kt from ~40nm out. Could this be related? And do you know what could be causing such an extremely delayed rendering? I sometimes see this happen also with other custom scenery objects but this is an extreme case for some reason.
FYI I think I managed to narrow down the root cause: VR Graphics → Dynamic Settings.
If I disable that option the LOD0 tower object is rendered much earlier and the beacon is attached correctly.
PS: I use a target FPS of 45 in my dynamic settings - maybe that triggers some overly aggressive LOD bias which derails the correct beacon attachment to the mesh. In any case, something seems wrong with that logic.
