Come on Asobo get this sorted, should take someone 10 minutes to correct this.
1 Like
I guess Asobo not even looks into this topic until hat has at least 5000 votes! 
Another 8 months went by and nothing happened.
Isn’t there any way for the forum mods to put this on the bug list?
I’m sure an Asobo developer will need 5 Minutes to get this fixed!
And WE NEED THIS!
Hi @Breenild,
My Personal Comments and Observations:
Looking at this wish, in the two years+ that it has been open, it has gathered 73 votes. Compare this to the top 48 Wishlist items reported in the June 13th Development Update that range from 2,695 to 351 votes.
That number (73) suggests to me that developers working on Wishlist items (if any) and if guided by the community’s votes, would be working on items higher up the list.
However, IMO, at this point with MSFS 2024 releasing in November, I suspect that virtually every developer is working to complete the worklist items for their part of the 2024 code base, and any who have done so are helping others complete theirs, or reviewing and fixing any issues identified by the internal test teams.
So I’d not expect to see any resolution to this wish this year, irrespective of how long it might take to make the change & test for potential problems caused by the change in the code.
W.r.t. putting this on the bug list - no, we volunteers don’t handle that. The MSFS team make those sorts of decisions, and as has been noted previously in this thread, the current functionality is by design:
1 Like
@SmotheryVase665
Thank you very much for your detailed answer.
I understand that all the developers are on the msfs2024 release.
I will wait for it and maybe hopefully this problem is fixed there.
But I’m pretty sure, this behavior IS a bug:
It is nice, that the mouse pointer gets hidden after some seconds of not using it.
But they implemented only one trigger, which prevents the pointer from disappearing: you need to MOVE the mouse.
But in the planes we have lots of buttons, where you have to press many times:
Checklist or STEPPING thru a flight plan for example.
There i hold the mouse in place, but i have to click the left button several times.
And the developer FORGOT to add the mouse buttons to the trigger, which prevents the pointer from disappearing.
Please try it by yourself:
Take the A320, load a longer flightplan and activate the PLN mode in the EFIS.
Then try to click through the flightplan and you will understand immediately, why this behavior is so annoying.
1 Like
Hi @Breenild. W.r.t.
My Personal Comments and Observations:
If the code tells the mouse to fade out after 3 seconds of no-mouse movement, and the code ignores any mouse clicks, then, by definition, this functionality is “by design”.
A “bug” is defined as something that is not working as designed.
The design itself may be good or bad or something in-between, but poor functionality does not make a bug. Furthermore, we don’t know if the developer forgot to add this functionality or not. Perhaps there were other reasons it was not included - again, we just don’t know.
I’m sure what you are reporting with the A320 is correct. I’ve hardly flown the A320 or used its electronic systems, so actually am the last person you should be asking to repro what you are seeing, as any non-repro would not be because what you are doing or seeing is incorrect, but because I failed to follow the right procedures!! 
It doesn’t have to be that specific example. Try clicking any aircraft button or knob multiple times and you’ll find the mouse times out and stops responding.
Hey @SmotheryVase665
the definition of a bug from my point of view as a user includes coding bugs and also “design bugs”. I cannot differentiate whats the reason, why something not works like I (and all the other users) expect.
A mouse hiding feature is nice, when it is designed and programmed properly.
But this also includes to watch the mouse buttons and prevent the mouse from hiding, when I only press buttons without any move.
As we now talk for months about that, an Asobo developer had maybe needed 10 minutes to fix that problem, IF they would be aware of it!
Hey,
Searched a bit but couldn’t find this mentioned anywhere else. If duplicate, very sorry.
Request: can i please make a request that’s been driving me crazy for years and would probably take a dev 30 minutes to fix ?
Current behavior:
- If mouse has no movement - cursor disappears after 3 seconds from screen (good)
- If mouse has no movement but it’s being used via clicking (e.g. when rotating knobs, clicking MCDU buttons, etc. ) - cursor disappears after 3 seconds (not good)
This just leads to choppy usage and i’ve been trying to compensate by gently moving the cursor all the time while adjusting something, but coupled with the movement of camera, cursor goes off clickable button/knob, and then it starts zooming in / out.
I think it just makes sense for the UX to also detect when the user is actively clicking, therefore using the mouse and keeping the cursor on-screen until no activity is detected – after which we can hide the cursor.
Thank you in advance 
1 Like
Agreed, also really bothers me and makes typing into MCDUs, etc. really frustrating.