Hi I think what you are seeing is not the cursor but only the trail of the cursor when you move it.
Probably caused by a switch on your stick of throttle that emits a constant signal (like the red T1-T4 buttons on a Virpil throttle.
Option one: just switch that button to “Off”
Option two: Go into your mouse settings and unmark " “Hide cursor while typing”
Both worked for me.
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:
My cursor kept blinking whilst playing, totally fine in the menu’s. I use the alpha bravo peripherals and unplugged the alpha and my cursor is back to normal. Switch controller profile on alpha unit to default and everything seems ok. Must be a conflicting setting i had which is strange as i have not adjusted anything for a long time.
If relevant, provide additional screenshots/video:
I can reproduce by flipping my (virpil mongoose) T2 button back to “on” but there is a complication:
\the other T buttons are fine. The one that causes the mouse to disappear is “paired” to a slider that
moves either the airbrakes (when “off”) or the RPM (when “on”) in a propellor aircraft.
So the problem seems to be either in the pairing of 2 commands , in this case a constant repeating “on”
plus a slider value. It does recreate the disappearing cursor and also the white ball on the right mouse click
when I set them this way.
I’ve tried disconnecting all controllers except for mouse and keyboard but still getting the intermittent mouse curser. Also tried chnging mouse setting to ‘hide curser while typing’ and also still getting the flashing curser. Any other suggestions to remedy the situation?
Today I counted. It took exactly 100 mouse clicks to turn off my magnetos! Buttons and toggle switches can usually be activated after 30-40 attempts, but levers and dials are impossible. This is bad enough on the ground, but in the air — disaster. I tried switching fuel tanks in flight - no cigar. Emergency landing.
So, has anyone heard a peep from Asobo even acknowledging this issue? The cynic in me wants to think that they hope people will get so aggravated by bugs in MSFS 2020 that they will be desperate to buy 2024.
1 Like
I had the same problem.
The issue with me was a sticky Shift key on my keyboard.
I lifted off the key from the keyboard. As soon as I did, the mouse stopped flickering and returned to normal.
Seems from reading other posts here others are also experiencing issues with joysticks and other input devices.
Maybe it has something to do with other devices not returning to neutral after use.
Perhaps check all your input devices to make sure they are sticking???
Having the same problem. It’s so annoying
unplugging all my peripherals seems to have fixed the problem. Only thing that still isn’t working is manual control of the A320 cockpit, but that was broken before this last update. Thanks for sharing your solution, it worked for me.
1 Like
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:
so this white dot started hapenning when i was recording my flights with geforce experience and to stop it i would have to reboot . Now it does it all the time more since the last update . Also the last update has made geforce experience unusable.when i press alt z to open it up i cant click on anything!! Im using i9 , rtx 3070,32 g ram , please fix its impossible to fly because the dot flashes and disables the mouse clicks!!
Started PC and unplugging all peripherals except mouse and keyboard. Launched MSFS - checked that only mouse and keyboard recognised in MSFS Controls section. Launched a flight and mouse worked perfectly. Plugged in yoke - mouse still working perfectly. Plugged in Honeycomb Bravo - mouse still working correctly. Plugged in rudder pedals and checked and the Cessna trim and checked and finally Saitek throttle quadrant and checked - mouse working perfectly throughout a 15 minute flight with all peripherals connected.
Closed MSFS and shut down PC. Restarted PC and launched MSFS and setup same flight as before. Intermittent mouse there again.
Disconnected and reconnected keyboard - intermittent mouse.
Disconnected bluetooth mouse and replaced it with a different, newer mouse - mouse now working correctly again - throughout another 15 minute flight.
Closed MSFS and shut down PC again. Restarted PC and launched MSFS and setup the same flight again…….intermittent mouse still there.
Next I want to try throwing simulator out the window - not sure if I’ll put it back together again to see if that worked….
4 Likes
Yes, it is definitely very frustrating. I have read all these posts above and somehow fixed the problem changing my mouse profile to something and it just started working.
I know that there are thousands of different options and configurations but clicking mouse button to select switch should never be a problem as it is the most used interaction.
Anyway, let’s hope it will stay…
Thanks for that suggestion about changing mouse profile……standby….testing…but looking effective so far…fingers crossed. Will report back when tested more.
1 Like
Looks like putting in a 2% dead zone on my yoke and rudder pedals solved the problem. Was set at 0. Not sure why.
1 Like
So yes same exact problem I am having. The white edges + flickering mouse. But what I did was isolate it down to something to do with the Bravo Honeycomb Throttle Quadrant. Every time I plug it in within a flight it start flickering again. Super annoying
Bother, after more testing, flickering mouse has returned. So, changing mouse profile hadn’t worked for me. Also tried adding some dead zones to controllers - still getting flickering….
So after 4 days guess what……It’s back 
Appeared today ■■■■■■■■■■■.
What I did, out of frustration, was flick around quickly through the cockpit and outside camera views using the POV hat on the joystick.
Don’t ask me how but the flickering stopped and stayed normal for the rest of the flight.
Probably just lucky. It’s got to be some sort of conflict with the input devices.
Definitely needs a hot fix to it 
Same here, Problem persist. Tried everything to solve the problem without success No way to fly with this problem. Please give us a hot fix to bring back normal flights!!!
Greetings -
the intermittent mouse interaction with ‘flickering’ pointer and white dot appeared to me today
Upon reading this thread I realized one reason being ‘flickering’ of signals from other controllers connected via USB
I am using two CH Products USB controllers, one Fighterstick and one Throttle Pro
I know that, from time to time, with the throttle is set in full back position, the setting (that should be zero) ‘jerks’ randomly to higher values and then settles
Suspecting this was the case for today issue, I entered CH Calibration software and applied a higher ‘null’ zone on the throttle, both at minimum and maximum positions (the ‘null’ zones being one ‘square’ of the calibration scale at its bottom and top)
This seems to have solved the issue for me, posting here so that could be useful for other simmers
2 Likes
Hey thanks for that. I have the Logitech X56 very similar to yours.
Tried what you suggested with the throttle.
Seems to have worked. Good pickup, Thankyou
1 Like
I’ve gone two days without the flickering but today got it again. What I did today when I got the flickering was to go to the controls menu and change the dead zone of my (new) Velocity rudders to 5, saved that then changed it back again to original 0 and saved that and returned to the flight - flickering gone. Thinking back, before ever flight the last couple of days, I had gone to the controls option and changed something and never had any flickering. So, it seems to me at this stage that the controls, including mouse, need to ‘be reminded’ that they are in a PC by just changing something in the controls menu and save and can put it back again and save.
Anyway, that’s my theory and experience at this stage - hope it continues to sort the flickering until MS fixes the problem permanently.