LukeFF

Not to go too off-topic, but you're really better off disabling the crash options, as they are implemented very poorly by Aosobo.

The Hold Short markings are missing the western end of the taxiway:

Can confirm the taxiway sign issue as well here - with both Luton and Dubrovnik.

I'll also add that we should be able to remove static aircraft. I have AIG and BATC for that, so it's just needless clutter for me.

One other user confirms the same: https://discord.com/channels/535246634448191499/1466882084818653368/1466901105182118100

Unchecking all the POI options in the iniManager for 2024 results in this for SoFi:

SoFi Stadium and the surrounding area, as shown in CU13, conflict with this airport.

Hopefully these are the correct files, as it's pretty hard to attach anything else from the WASM folder. KONT to KIND, was cruising at altitude (about 330) when the plane went off course. All buttons became inop at that time. Work.zip

On the final approach to runway 26, Storchenstrasse has been modeled with a couple of hedgerows and sightseers, but not much else. In reality, there are numerous buildings there instead of the flat field in this version of the airport. What's more, it's all visible on Google Street View:

Some of the containers on the main apron are hovering:

This issue is still present, even though for some unknown reason the topic was locked last November: 🤔 It's not a GSX issue or an issue with the stock LOWI scenery. It has to be something else.

At a fairly short distance, the VDGS poles in the cargo parking areas disappear, making it look like the VDGS screens are floating in midair.

When configuring Stanstead, button for Nool doesn't respond correctly - it just renders some half transparent tooltip text that is unreadable. Also results in the airport having both Nool and GSX screens rendered on top of each other.

Also, to add: with the current configuration, it looks like the GSX VDGS screens conflict with the ones that come with the stock scenery. I experimented with this at gate 14, which gave me a purpleish looking number on the screen and info from what looks like the GSX screen. Scenery index clearing did nothing. Looks like there is some sort of issue with configuring this properly in the app.

You can also see the problem here on your store page, upper right-hand portion: