For a developer and publisher who is so pushy about accessibility features, surely this should be one of them??? It’s genuinely uncomfortable to play at times.
3 Likes
Yeah, it’s just another one of those ‘one dev-hour at most’ bugs which would have a significant impact on experience that Asobo can’t seem to squeeze in to YET ANOTHER SU.
3 Likes
Because they don’t know about it. The three beleaguered forum mods who are in charge of logging feedback haven’t seen this thread. Because it hasn’t garnered their interest, it’s a dead item.
1 Like
FYI:
-
The Volunteer Moderators - who are just regular users and not Microsoft or Asobo employees - are not in charge of logging feedback. We have no ability to input feedback of any type into Microsoft internal tracking systems.
-
The folks at Microsoft who make decisions about requested new features can and do read topics in this category.
-
The choice of which features to include are not determined by the Community Managers (they are Microsoft Employees). They read the topics in this category, and can refer topics directly to the right folks within the development teams when needed. They (not the Volunteer Moderators) also add the feedback-logged tag when it is appropriate to do so.
So, saying “Because it hasn’t garnered their interest” is not correct - either when applied to Volunteer Moderators or Community Managers.
No item is “dead” until there is a notification by a Community Manager that indicates that a wish will not be implemented. For example, this wish, which was tagged as by-design
I hope this clears up any confusion on this matter! 
It does - and it’s actually worse than I initially thought. From what you’re saying, there’s a good chance an employee (or several?) at Microsoft has seen this thread at some point from when it was made in November 2024 and have deliberately chosen not to pass along the feedback.
Thanks for taking the time to clarify.
3 Likes
No, that’s not what I’m saying at all.
Anyone within Microsoft or Asobo can read these topics at any time, so there is no point in the CMs “pass (ing) along the feedback” on every topic, since the dev teams can read them anyway.
(which, by the way, is why tagging a topic correctly is so important - see this topic for details.)
Just because a topic is not feedback-logged does not mean it has not been read by someone at Microsoft or Asobo.
My Personal Comment & Observation
Taking off my Volunteer Moderator hat for a moment, and just speaking as a regular user of the forums who reads a lot of posts / topics, I suspect that there is a reluctance to add the feedback-logged tag too early in the development cycle to avoid setting false expectations within the user community. There are many reasons why a feature planned for release in SU “X” could get pushed back or delayed, so the development teams are (IMO) rightly cautious about adding this tag.
For example,
- The wish does not fall within the vision that the Executive team (Jorg et. al) has for MSFS at this time.
- The wish requires work that might only be planned for a future version of MSFS
- The wish is a good idea, but the there are no resources currently available to work on it
- Etc. etc. - I’m sure everyone can come up with other reasons too.
Anecdotally, I’ve noticed that the feedback-logged tag is added only once a feature gets close to being released in an update such as a SU. For example this wish was feedback-logged a few months before the announcement of the new apron & other lighting additions in SU6 was announced at FSExpo.
But again, I stress that the above are my Personal Observations and should not be taken as some sort of “official” statement about the matter, which I have no authority to make.
And it only took 5 years to implement! Rapid.
1 Like
The part that bothers me is it’s a feature regression, not something new being requested. These settings were available in MSFS 2020.
6 Likes