When using BeyondATC to taxi to 08R, I get strange instructions saying to cross 08L at G but to hold short runway 08L. And then it mentions taxiway T even though I haven't used it.

Their support says "Prob a scenery issue"

 

Edited August 21, 2025Aug 21 by srce

Is there an update in planning?
There are a lot of wrong stop markings around both runways and taxiways, so BATC is not useable.
If you need more screenshots, no problem. Ask me.

Edited October 12, 2025Oct 12 by village1111

Agreed, this one is strange with stop markings with BATC.

On 10/12/2025 at 2:48 PM, village1111 said:

There are a lot of wrong stop markings around both runways and taxiways, so BATC is not useable.

I have no idea how these things should work, but it seems somewhat similar to this:

 

Doesn't look like there's any changes in 1.0.2 for this.

Same issue reported by several people on Discord.

Hi, I don't think there's anything we can do on our end to fix the issue here, as we can only define start and endpoints for taxiways and runways. All logic regarding routing is handled by BATC's AI.

On 2/2/2026 at 4:20 PM, iniSteven said:

Hi, I don't think there's anything we can do on our end to fix the issue here, as we can only define start and endpoints for taxiways and runways. All logic regarding routing is handled by BATC's AI.

Steve, can you confirm what the purpose of this setting is in the installer?

I understand it switches .bgl files but what is that achieving? 

The issue BATC has in part that aircraft cannot cross 08L/26R without being given permission which, when I saw this option appearing, presumed would remove 08L/26R as a valid runway at Gatwick and thus allowing aircraft to instead see the runway as a taxiway only. BATC makes the assumption that a defined runway is an active runway, but of course that is not the case at EGKK for the second runway on routine operations. I've asked before on Discord and you said it toggles what the 'active' runway as which is what I presumed, and that you would confirm with the scenery developers in June 2025, but I never heard anything further. Did you discover anything further?

Kind Regards,
Jason

On 2/2/2026 at 4:20 PM, iniSteven said:

Hi, I don't think there's anything we can do on our end to fix the issue here, as we can only define start and endpoints for taxiways and runways. All logic regarding routing is handled by BATC's AI.

Further, have managed to identify the issue with help from BATC's team.

Red boxes are the issue, green box is fine. You'll see the holding point nodes for 08R are correct in the middle, but are listed for 08L for the top and bottom one in the screenshot. Changing those holding point notes leading onto 08R to specify 08R, not 08L, should resolve the issues.

Edited February 9Feb 9 by JasonO

I'll pass this on to the scenery team. Thanks for the insight

Hi @IniSteve - this seems like a relatively easy fix to swap these nodes. Do we know if it's likely to happen soon? AI trying to route via the above taxiways doesn't make it, making 08R departures a bit of a mess.

Did we also work out what is actually changed with the BGL's switched with the 'North Runway Active?'

The BeyondATC Discord is frequently seeing people raise issues with AI and debugging confirms these nodes not linking to the right runway (or that the runway in the nodes isn't correct!) is playing up. Seems to be quite a bit of disapointment with the quality of the ini product if something quite simple as renaming the runway in the node data is still left to be fixed over 2 months later from when I demonstrated the issue.

Edited April 23Apr 23 by JasonO