I’d prefer the tag stay as I originally tagged it.
It serves as a record for just-how-long-we-have-been-putting-up-with-this.
It would sure be nice that bugs introduced in betas were fixed before betas become public releases.
I’d prefer the tag stay as I originally tagged it.
It serves as a record for just-how-long-we-have-been-putting-up-with-this.
It would sure be nice that bugs introduced in betas were fixed before betas become public releases.
i know what you are saying - its still present in the current beta.
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:
It also happens when changing plane’s livery
So… I can confirm that the bug is still present with Sim Update 15 !
This is getting ridiculous. They even were pointed to it during one of the recent livestreams if I remember correctly…
One of many, many annoyances left in 2020, and I fear permanently with the advent of 2024. But it’s hardly game breaking, just frustrating if you forget yourself.
I know we are going to get in trouble for having a discussion in a bug thread, but I really want to know what the actual reason is that so many bugs like this do not get fixed.
Take that blasted DX12 bleed through bug. We bring it up in the last Q&A, make a real push to explain it and BAM! like that it is fixed in the very next build of the SU15 beta. We put up with it forever and it was fixed so quickly when they just sat down and did it.
I swear, I bet most of these bugs are the same way — they either don’t know about them, understand our reports and/or realize how much of an impact they have on our “quality of life” in the sim.
What I want to know is why is this the case? Why don’t these just get knocked off the list? Why do they get discovered during a beta and don’t get fixed during the beta? Why do we end up with them indefinitely in the final releases?
Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
No
Have you disabled/removed all your mods and addons? 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.
Yes
Brief description of the issue:
Planes are spawning on the runway instead of atthe gates as selected on the world map. You have to quit back out to the world map totry again.
Provide Screenshot(s)/video(s) of the issue encountered:
ICAO or coordinates (DevMode > Debug > Display position)
Any airport.
Detailed steps to reproduce the issue encountered:
Click on a gate on the world map. It should turn green when selected.
PC specs and/or peripheral set up if relevant:
Build Version # when you first started experiencing this issue:
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
Yep, can confirm, bug is still present and still 100% reproducable. Just accidently did it again recently. But it’s only 1,5 years ago when it was introduced, so we will keep on waiting patiently.
Same here, bug still exists
Not just exists, happens in MSFS2024 as well.
Really?!
Please say it isn’t so.
This is the one FS20 bug that I tested in FS24 that I found was actually fixed.
But I did only test it once in one scenario, maybe I missed something. Will have to try this one some more (although I usually catch it at least a couple of times per month without even trying).
This one is actually fixed in FS24, in so far as I can tell. If it has happened to anyone it would be interesting to get the details on how.
I’ve changed aircraft, livery, and even aircraft type (eg. from hot air balloon to plane) and it hasn’t reset my parking space yet.
It has seemingly reset my livery to a default one, I’m not sure of the circumstances yet and anyway that would be a different bug altogether.
Definitely fixed in 2024. I’ve tested it multiple times now.