Getting back to the Bug Report Topic and having spent a couple of hours in both the 45/145 after installing the update mentioned here, I can no no longer recreate this issue.
Thanks for the fix!
Getting back to the Bug Report Topic and having spent a couple of hours in both the 45/145 after installing the update mentioned here, I can no no longer recreate this issue.
Thanks for the fix!
Thanks @ccrbc but we still need it confirmed officially otherwise if/when it does turn up againâŠAH, Microsoft or Asobo can just turn round and sayâŠwell we never said it was fixed or an issue in the first place
If itâs been fixed, how come the âfeedback-loggedâ rather than âbug-loggedâ tag is still on this post? (@SteveX77 comments apply in that instance though, maybe the community team havenât got round to doing it)
Wonât be buying it until then
Sorry for my inaccuracy - by internal and external teams I meant MSFS development teams (of course) - Asobo itself and their all development partners.
Itâs vital for them to stay in sync and share all the relevant info with community managers.
EDIT: To stay on topic, Iâm just asking asobo whether this specific issue has been fixed within latest Ae-45/Ae-145 update or not. And Iâm asking because my own observations say PROBABLY YES, where update release notes says NO.
I uderstand that sometimes itâs nearly impossible to mention every single fix in changelog, but at least these that was openly identified, reported and discussed should be there.