Title says it. I have tried numerous mice in VR and none of them nmove around consistently allow me to put the cursor where I want and click something. I will be trying to move the cursor and it will freeze and then jump, over and over.

I do not have any VR controllers on. In fact in Pimax Play I have controllerless clicked on.

What are you folks using for a mouse that just works?

Thanks.

MSFS has long since suffered from a controller conflict with the mouse in VR, as Asobo are essentially rubbish at coding for this most basic peripheral you have to add a Dead Zone to all your controller inputs then the mouse should be just fine. 

I say should as for some people that just hasn't worked, but give it a try.

I'm using a simple (simplest?) wireless mouse from "Logicool" with just two buttons and a scroolwheel, and I don't have issue.

Sometimes, I do face the cursor not reacting, jumping around, lagging etc.... but that's only when the mouse is getting too far from its blutooth dongle while the mouse battery is getting low. Once I replace/recharge the battery, all comes back to normal.

I’m using a Logi trackball; very convenient. Besides, I assigned as many functions as possible to VoiceAttack speech phrases.

I think it’s an FS issue. I’ve tried several mice, Bluetooth and wired, and get the “sticky mouse” issue toward the end of flights. Exiting VR and restarting it clears it up (not possible in 2024 since exiting VR crashes the sim)

47 minutes ago, haskell said:

I think it’s an FS issue. I’ve tried several mice, Bluetooth and wired, and get the “sticky mouse” issue toward the end of flights. Exiting VR and restarting it clears it up (not possible in 2024 since exiting VR crashes the sim)

I hardly ever experienced a sim crash on exiting VR and I use VR exclusively. The only occasion I had a crash was when I used the Open XR Toolkit. It is not compatible with the latest 2024 version any longer.

2 hours ago, Flyfox said:

I hardly ever experienced a sim crash on exiting VR and I use VR exclusively. The only occasion I had a crash was when I used the Open XR Toolkit. It is not compatible with the latest 2024 version any longer.

If you google there are a LOT of people experiencing it. It happens 100% of the time for me. CTRL-TAB = bye bye MSFS. 

I tried disabling OpenXR and it made no difference.

https://forums.flightsimulator.com/t/ctd-every-time-when-leaving-vr/757679

12 hours ago, Flyfox said:

The only occasion I had a crash was when I used the Open XR Toolkit. It is not compatible with the latest 2024 version any longer.

That is incorrect, I and others are using it perfectly fine with MSFS2024.

I confirm OpenXR Toolkit works 100% fine with MSFS2024. It's just "not supported" in a sense that it won't receive any new updates from its author, that's all. But the current version works just fine.

If the CTRL+TAB (enter/exit VR mode) causes a crash, I would simply suspect one of these two:

1- the OpenXR runtime installation (NOT the toolkit) and related setup (i.e. to get rid of SteamVR and such)

2- the video drivers, eventually.

 

 

Back to the mouse question, @Rob G , I use an old-fashioned wired mouse...I think I've had it around 10 years!  The reason is that with all of my wireless mice/roller-ball/etc, there are occasions where I get stutters and delays between moving the mouse and the cursor moving even though the overall MSFS2024 VR experience is smooth and stutter free in all other aspects.  

I find that the wired mouse is much more consistent...although if I have ALL of my various addons running AND am silly enough to try flying on a 'popular' evening (think Friday Public Holidays, etc) or when there has been a recent rolling update, there still can be the occasional lag - but that is nowhere near as often as with my other wireless mice 

lI want to thank everyone for their willingness to respond to my question. I added a dead zone to all my axis settings and now my mouse is working perfectly. Hopefully it wiull stay that way.

On 4/28/2026 at 1:32 AM, Daube said:

I confirm OpenXR Toolkit works 100% fine with MSFS2024. It's just "not supported" in a sense that it won't receive any new updates from its author, that's all. But the current version works just fine.

If the CTRL+TAB (enter/exit VR mode) causes a crash, I would simply suspect one of these two:

1- the OpenXR runtime installation (NOT the toolkit) and related setup (i.e. to get rid of SteamVR and such)

2- the video drivers, eventually.

 

 

Interesting update: I have a 30 day XBOX Ultimate trial and was using that version. Steam is having a sale and I have 2020 on Steam so prefer it for 2024. I figured why not and bought it. No crashes on the Steam version popping in and out of VR. WOOT! So it must be something unique to XBOX. At any rate, I am a very happy 2024 camper! 

On 4/28/2026 at 6:38 PM, Rob G said:

lI want to thank everyone for their willingness to respond to my question. I added a dead zone to all my axis settings and now my mouse is working perfectly. Hopefully it wiull stay that way.

Mouse has no dead zone setting, so I wonder why a dead zone to all axis have influence at mouse behaviour, 

2 hours ago, solito said:

Mouse has no dead zone setting, so I wonder why a dead zone to all axis have influence at mouse behaviour, 

Because any input from those devices caused a lag in the mouse pointer, it's an old MSFS2020 issue that still lingers on to this day. So setting a small dead zone to other controls can help, as proven.

To me the mouse lag almost seems like a resources issue.  It's usually for the first part of my flight it's fine but later it can get really laggy.

I also have old noisy axises on my devices so I guess it's a factor too