theoldtannery

Had a response from Just Flight, very interesting. Implemented their solution and it works. The answer regarding which product is "at fault" is, unfortunately, "neither" - it's just because of different altitudes for the airports and the only solution is to remove one or the other. Because the Real Taxiways products are designed to work specifically with the base scenery included with the sim, if an add-on airport changes the altitude of, or the ground profile of (e.g. adding slopes, or "lumps and bumps") the airport, then what you see as a result will happen. There is, however, a solution that is less drastic than removing the entire product, but it requires you to disable just the airport you are having problems with in Real Taxiways and then rebuild the index file for it: If you go to [MSFS2024]\Community\bksq-scenery-realtaxiwayseuro\scenery\global\scenery, locate EGSS.bgl and rename it to EGSS.bgl.bak, then agree that the name change will stop it working (that's the plan!) then this will disable just the airport that has the clash when the third party scenery, while leaving the rest of the product intact. This will work for any other airport that has a similar issue. Unfortunately, there is another stage which you have to carry out to keep the product functional, because of the way MSFS2024 works. - Go to https://github.com/HughesMDflyer4/MSFSLayoutGenerator/releases/tag/v1.1.1 and download MSFSLayoutGenerator.exe by clicking on its name. You do not need either of the Source File links. - Copy, or Move, MSFSLayoutGenerator.exe to somewhere you can easily access it, such as your desktop. You do not need to run the tool directly. - Browse to [MSFS2024]\Community\bksq-scenery-realtaxiwayseuro\, where you will find the file "layout.json". - Left click and hold on layout.json, then drag and drop it on top of the icon for MSFSLayoutGenerator.exe and release it. A Command Line window ("DOS Box") should briefly appear, then close, after which layout.json will have been updated to reflect the name change you made. Once this has been done, the product should work as before, but the clash with Stansted should have been resolved.

Have just done a flight from EGHI to EGSS using BeyondATC. All went well but when I landed I was allocated a parking ramp of 601. This does not exist on any charts from Lido or Navigraph. Initially I thought BATC was probably at fault but then I returned to the world map and zoomed in to the airport and sure enough that stand is shown as available which is why BATC was able to choose it. I have also seen this on another airport from a different supplier. Can anyone confirm whether the stand is right as shown in MSFS 2024 and that the charts are out of date for things like parking stands or if EGSS is wrong in showing them.

Have just done a flight from EGHI to EGSS using BeyondATC. All went well but when I landed I was allocated a parking ramp of 601. This does not exist on any charts from Lido or Navigraph. Initially I thought BATC was probably at fault but then I returned to the world map and zoomed in to the airport and sure enough that stand is shown as available which is why BATC was able to choose it. I have also seen this on another airport from a different supplier. Can anyone confirm whether the stand is right as shown in MSFS 2024 and that the charts are out of date for things like parking stands or if EGSS is wrong in showing them.

Bought EGSS the other day from the marketplace in fs 2024 and as has been previously noted in another thread there is this huge step right across the runway. In my case I have disabled the other WU version of EGSS but the issue is still there. Photogrammetry makes no difference. This issue seems to date back to 2022/23/24. One thread happened to mention that Black Square Real Taxiways was the culprit which I do have, so I removed that and sure enough the problem went. However, many other people have the issue and don't have the Taxiways. I have logged a ticket with Just Flight about this. Another thread said they had converted the .bgl file for EGSS to XML and then edited out a line that had something to do with Flattening which solved the problem. This suggests the problem is with EGSS data. My question is has anyone come to a definitive answer as to whether the issue is withing the EGSS airport or within Taxiways. No doubt one will blame the other but I am surprised that both have been around for a long time now so if one was at fault surely an update should have fixed it by now. Can anyone clarify the situation on this. Thanks