Version: 1.6.18.0
Frequency: Once/Rarely/Frequently/Consistently
Severity: Blocker
Context: Any aircraft
Bug description: Starting with 1.6.18.0, any aircraft will return “ON ANY RUNWAY” false preventing proper initialization for when aircraft start on runway.
Repro steps: Start the sim, select any aircraft, select a runway on any airport, start SimVarWatcher and add “ON ANY RUNWAY” as Bool.
Hello @simfan ,
I tried with the 1.6.18.0 and couldn’t reproduce the issue.
What’s the airport ICAO in your screenshoot?
Did you try with another airport and the DA62 just to compare ?
Regards,
Boris
Hello @Boris
I tried with multiple airports and any aircraft…
This is SimVarWatcher from MSFS2020, if that makes any difference. Did anything change with SimConnect lib versions?
It’s also working when I use the SimvarWatcher from the 2020 SDK.
Can you try with the release one from the 2024 SDK ?
Did you try to restart the game ? (just in case)
Regards,
Boris
Hi @Boris
I tried with latest 1.5.4 installer (needed Samples) and the release version of SimVarWatcher as well.
It doesn’t matter which airport or which runway, I always come up with 0.
I am assuming it doesn’t matter that I have DevMode enabled.
We were able to reproduce the issue and I have logged a bug in our backlog.
I will let you know when I have more news to share.
Regards,
Boris
Note that this bug also affects in-game play. The options available in the ATC panel when spawning an aircraft on the runway are now incorrect and only relevant to the aircraft being parked up (rather than being ready to take off).
We think this is related to an issue with the aircraft not being spawned on the selected runway.
For example, selecting LFPG 26L leads to the aircraft being spawned on 27L.
Can you confirm this is also the case for you when the issue occurs?
Regards,
Sylvain
I should have stated that I’m testing on su4 beta 1.6.18.0. Apologies if that makes a difference to my previous post and your request for further info from me.
I’ve just tested a number of different airports (these are used by the 5 or 6 test flights I always run with a sim update: EGNC, EGNT and EGCB) both with “ATC enforce flight plan” on and off. I also used the defaulted runway (i .e. I didn’t specify in my FP which runway to use) and also overrode that default to manually choose a runway. In all cases, spawning on the runway just left me with ATC options which were valid only for a parking place spawn.
Additional info which may be of benefit: whenever I’ve run my test flight in versions prior to 1.6.18.0 when I’ve spawned on the runway the preflight sequence that runs (after the “swoop in” effect has completed) had an (automatic) audible interchange between pilot and controller. This is now missing which would again suggest the sim thinks I’m parked?
@Boris -
this looks fixed in 1.6.21.0 that just dropped… (even though it wasn’t in the readme notes).
Thank you for taking care of it!
It looks as if my hypothesis that this issue has also caused the incorrect ATC options to be displayed to the user when starting a flight on the runway was incorrect; the issue I’m referring to is still present in .21 despite simfan correctly reporting the simconnect issue is fixed.
Unfortunately ATC bugs seem to get few votes on the beta forum (this simple to reproduce issue has only 6) but I’m hoping this won’t prevent further investigation into why the incorrect options are being displayed since .18 was released.
Thank you for the feedback.
Sorry, I didn’t have time to update the topic in time.
Regards,
Boris
This topic has been automatically closed after 60 days of inactivity since it was marked as fixed.
If there is important new information about this same report, you can use the “Request reopen” button below to ask the moderation team to review it again.
For other issues or broader discussion, please open a new topic in the appropriate category.
