scarymovie

Hi Wayne, I believe you're wlbragg from the FG forum, with whom I previously discussed the Ramp Marshall. It's a pleasure to connect with you again here. I was eager to share this information in the forum thread, knowing you're actively developing enhancements for the addon, But I thought it might be valuable to first gain some insight into the scripts. Please let me know if there's anything I can assist with in your testing efforts. I'd be happy to help in any way possible. Just one more thing!...

Hi Wayne, I believe you're wlbragg from the FG forum, with whom I previously discussed the ["Ramp Marshall"]{https://forum.flightgear.org/viewtopic.php?f=30&t=20572&sid=764d573de5567a04d69501f2669983c5&start=75). It's a pleasure to connect with you again here. I was eager to share this information in the forum thread, knowing you're actively developing enhancements for the addon, But I thought it might be valuable to first gain some insight into the scripts. Please let me know if there's anything...

I am keen to find answer to those questions too, wKitty.

Hello wKitty, I believe I've identified the source of the error: the Nasal files associated with the Ramp Marshall add-on. Disabling the add-on didn't resolve the issue as we need to add 2 Nasal files manually to the data folder during the installation. I've not took a closer examination of the Nasal scripts to see what exactly caused the error but it revealed frequent mentions of "ICAO," which might be the trigger. It's a shame that the add-on requires modifying the data folder, as add-on installation...

Hi wKitty, I sincerely appreciate you taking the time to test this on your end. Your feedback is invaluable in helping me to determine the scope of this issue. I will try to clear the default and custom scenery folders to see if that helps. I haven't delved into traceback debugging yet, especially after a fresh development environment setup. Are you able to guide me on how to acquire the build info please? On a positive note, knowing that not everyone is encountering this issue helps narrow things...

Replicating this issue is straightforward within US airspace. Specifically, when departing KIAD towards CYQB, the issue manifests shortly after takeoff. One of the ICAO is:- 3md4

Hi Gijs, launching FG with both "--airport=7622" and "--airport=6452" was successful. However, the underlying issue appears to be related to the designated coordinates rather than the selected airports. Thank you so much.

Hi James, You can start at LFBZ and fly on a heading of about 55 degs. It shouldn't take long until it hits the issue. I've attached a screenshot of the point when it happened. Coordinates: 43.603327, -1.313679 Thank you so much.