When spawning at a runway, the options in the ATC menu are only those for spawning at the gate (request taxi etc) - there are no options to get take off clearance from the tower.
Note - this is similar to another bug report (ATC Takeoff Options Blank . . .) but is not necessarily the same core problem, so it is probably worth this separate bug report.
FREQUENCY OF ISSUE
Every time since 1.6.19 released.
REPRODUCTION STEPS
Please list clear steps you took in order to help our test team reproduce the same issue:
Start any flight, spawning at any runway
YOUR SETTINGS
If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.
What peripherals are you using:
Joystick
[PC Only] Are you using Developer Mode or have you made any changes to it?
No
[PC Only] What GPU (Graphics Card) do you use?
GTX1080Ti
[PC Only] What other relevant PC specs can you share?
Yes I see the same behaviour in that all ATC options would indicate that the sim thinks you are parked at a gate and not ready at the runway. Also note another side affect of this bug is that prior to 1.6.19.0 the “start on runway” preflight sequence would have an automatic audible dialog between pilot and controller just before you start the flight proper; this is no longer the case as the sim regards you as still parked up.
I believe the root cause of this is the same bug as being reported on the dev forum and manifesting itself as always returning false when a simconnect call is made to enquire on whether the current aircraft state is “on the runway”. (Can be observed using the SDK SimVarWatcher utility).
My suggestion that the bug reported in this thread has the same root cause as the dev forum simconnect bug turns out to be incorrect. The simconnect bug is fixed in .21 while the incorrect ATC options when starting on the runway still remains.
This is an easily reproduced bug regressed in this beta which due to low number of votes won’t (yet) have been reported to the dev team (if I understand the forum tagging system correctly). Thus if it’s not already known to the devs it will make it to the release version.
Isn’t the voting system in beta tests flawed? By all means use the vote number for the devs to prioritise when a bug should be fixed but to not report a consistently reproducible bug due to low votes seems incorrect to me.
FS2024 has lots of “minor” bugs, which don’t get many votes. These are the ones which are only apparent in certain circumstances - in this case, only those simmers trying to start a full flight (including ATC interaction) from the runway. However, it is annoying when things which are working regress for no reason whatsoever. (Another one I’ve reported also with the ATC is when the list scrolls to the top and won’t come back down - again, this eventually corrects itself.)
Just like you I really don’t follow the logic of their many fixes - so often they are for “problems” I have never seen reported, while many bugs/regressions are ignored, even those getting large numbers of votes. They’ve only just got around to fixing the windscreen reflections bug, which has been present (and reported by many) since launch.
We have created an internal ticket to see if our team already has this logged, and if not they will attempt to reproduce the issue and create a new bug report. This item is now marked as feedback-logged. If there is an existing bug report or one is created, we will move this thread to bug-logged.
this bug still not fixed in SU4 1.6.23.0 also, see below video what diffrence between SU4 beta and SU3 product 1.5.27
Su3 1.5.27.0
SU4 Beta 1.6.23.0
the Diffrence between SU3, SU4, SU3 Automatically obtain clearnce of take off, but SU4 not automatically function happend., then appered taxing option in ATC.
Although the ATC is now showing properly when lined on the runway, the history is still missing. The first text after scrolling to the top of the panel is the taxi clearance, so all the flight clearance text is no longer present. This means that I still do not know what altitude I am cleared to after take-off - I still have to take a guess, then correct the altitude when ATC refers to it.
I was hoping that it would just return to what it was originally (as in the current stable version), before it was changed for no obvious reason.
For me it seems to work as before the issue started. I have created an IFR FP from KMCO to KMNI, send it to ATC/Avionics and when spawned on the runway, the 1 messages were related to the IFR FP, so doesn’t seem something is missing:
It looks like this is related to a separate problem I have.
I can get the full clearance if I enter the EFB, select airports by typing in the airport codes, find a route etc. However, as I really only use VR, I much prefer to select the airports on the map, then enter the EFB, find the route etc. (This is easier than having to remember the codes for both airports, and also avoids having to remove my headset each time I need to type things in.) This method should work in theory, as the airport codes are present in the EFB when I select it. This gives a proper route etc, but after “sending”, this doesn’t always get accurately communicated to the ATC, or even the aircraft. I often have to resend the data to both once I am in the airplane on the runway, by which time of course the preflight ATC communications have already been logged in the ATC panel.
So I accept the original regression has been solved.
I tried to reproduce using your steps and ATC IFR clearance was loaded successfully upon spawning.
Using KMCO to KMNI airport, ICAO were pre-filled in the EFB, selected IFR, create FP and send to the ATC/Avionics:
