Thrustmaster Airbus trim switch hides mouse cursor

Please tag your post with #pc and/or #xbox.
PC
Are you on Xbox, Steam or Microsoft Store version?
MS Store
Are you using Developer Mode or made changes in it?
No
Brief description of the issue:
Using trim down (and sometimes trim up), which I have bound to the hat up/down on the Thrustmaster Airbus stick instantly hides the mouse cursor.
The cursor reappears when the mouse is moved.
If I hold down the hat switch for a longer trim, the mouse cursor disappears permanently until the hat switch is moved up again.
This has been repeatable since SU7 for me.

Provide Screenshot(s)/video(s) of the issue encountered:
Unfortunately the mouse cursor doesn’t appear in screenshots

Detailed steps to reproduce the issue encountered:
Load in any aircraft
Bind elevator trim to hat switch up and down
Move the mouse so that the cursor is visible in front of you
Click the hat up direction and note that the cursor disappears
Move the mouse and note that it reappears
Now hold the hat up direction for a few seconds - note that the mouse cursor disappears
Move the mouse and note that it does not return
Click or hold the hat up direction and note that the mouse cursor reappears.

PC specs and/or peripheral set up if relevant:
Gigabyte Aero 15 x9 2070 gaming laptop
Thrustmaster Airbus stick
Logitech G402 wired mouse

Build Version # when you first started experiencing this issue:
SU7 beta from memory started it.
SU7 still occurring
SU8 beta no change
SU8 release still occurring 1.23.12.0

It’s been like that for a while, and I don’t think it’s specific to the Thrustmaster. It seems like the mouse cursor will become “disabled” as soon as the sim receives input from the other hardware. And only when it thinks that the mouse is being used, it then displays it again.

It’s been behaving this way since SU5, I think.

1 Like

I didn’t have this issue with my old Logitech 3d Extreme Pro. However, I got this new joystick about the same time SU6 came out, so probably then I guess.

Either way, it needs to be logged as a bug.