Do you have the same issue if you follow the OP’s steps to reproduce it?
Yes
Provide extra information to complete the original description of the issue:
I have the same issue and have something similar that just started. I select an airport and regardless of parking selected as a starting point, it goes to airborne, and does not let me change it. Tried switching aircraft and restarting sim and computer.
Are you using DX11 or DX12?
Are you using DLSS?
If relevant, provide additional screenshots/video:
Yes I’d have similarly saved time if I had the source to fix it myself! There are quite a lot of these bugs with easy fixes that linger for ever but really ruin the user’s experience. Another one is that blocking bandwidth popup.
Here’s another simple resetting to runway bug that’s been reported for over a year:
Rounding out my top three is a VR end of flight bug where your head gets smashed into instrument panel and roof when shutting down an airplane. It’s quite violent.
Yes, pretty sad to see not even AAU2 was used to fix it. Frustrating how they break working things and take forever to fix it again
Guess everyone is working on FS2024 now!
Absolutely! There are so many small fixes that could make, those of which cause serious annoyance to users and really take the shine off the game. This is a clear example, a recent regression, easy to fix, but no we have to live with it.
I was bitten by this again today, ‘just’ wasted 5 minutes of my time again.
The white dot is another classic example of this same pattern of not responding to regressions in a timely manner. But at least we now know why, nearly everyone is busy on the next big ticket release.
It’s disappointing this wasn’t rectified on time. The change was made during the Beta, but for some reason couldn’t be changed back. The change was presumably documented, so undoing it probably takes a few minutes?
I’m going to add this here as it may be relevant to the fixing of this bug.
Another thing that happens is if you choose a SID the flight reverts to starting on the runway, and you can’t change it back unless you select automatic departure.
The workaround is, of course, is to add the departure to your flightplan once you’re in the plane.
You can do this, it does reset to runway but if you go and select a parking spot on the map then the drop-down will still show the runway with the departure but the map will show the parking, and as long as you don’t do any anything else that’s were you’ll start. I’ve done this procedure many many times.
Of course it would be better to not reset the already chosen parking, but this is really a separate bug as this is a long existing behaviour not a recent regression like the livery change.
Do you have the same issue if you follow the OP’s steps to reproduce it?
YES
Provide extra information to complete the original description of the issue:
This exceptionally easy to reproduce. No further notes needed. Changing aircraft or livery after selecting a parking spot resets your aircraft to a random runway.
If relevant, provide additional screenshots/video:
Just here to report that they still didn’t fix it with SIm Update 13… just tested again.
But it’s only about 8 months since they introduced the bug, so we will continue with the workaround for a few more months I assume.
I’ve been saying for years that a QoL update, with absolutely zero new features, and just fixes for existing ones that don’t work properly, would be very welcome.
Today I have detected another side effect or variation of this old bug. Changing aircraft once you have selected an airborne start position does not initialize aircraft variables correctly, leading to some cockpit buttons not being clickable at all in the worst case, while those actions can be still responding to keyboard or joystick shortcuts (if mapped to those actions).
The content that can potentially drop this result is that one including any custom variables/initialization states in the preset files (cockpit.cfg or *.flt files) existing in the addon Simobjects/Aircraft folder. This happens with current SU13 at least.
I thought yesterday’s Dev Q&A was very good - more in depth than usual, more detailed questions and more detailed answers.
I know that there are large teams, and many bugs, and even if a bug like this is acknowledged with “bug-logged” Sebastian and Martial may not be aware of all of them… However, I am still surprised that they seemed entirely unaware of this bug when it was asked in the live stream, and had not come across it themselves just in the course of test flying? Sebastian’s expression says it all.
I thought that several times during the stream. Is there a “really?” emote that is suitable I wonder.
All we can do is continue to provide solid evidence, incontrovertible proof of any issue, and hope they are true to their word, read the forum posts, and see what we have found.
This one is trivial to demonstrate, as is the patchwork terrain issue.
