After a few months of really pleasing VR flying, just installed update 8

The great news is that the HOTAS now works even if the mouse arrow is over the ATC/etc boxes.

The bad news is that I am finding it impossible to operate the mouse in VR.  The aircraft is flying great - but once the aircraft is flying the mouse is taking up to a minute to get from one side of the cockpit to the other in a stuttery, juddery manner.  I double checked that nothing was uploading at the same time, but it isn't.  And - because I've had latency problems in the past with wireless mice - it's a wired mouse!

Anyone else having this problem?  

At the moment for me it's unflyable which is, as a bit of an understatement, disappointing...

 

I'll put a log in but would be grateful if you let me know if you are seeing the same issue.

I have this same issue using the beta version.  Starts out fine, then suddenly the mouse gets very slow and stuttery (using VR). Both times it had cleared up after takeoff and worked fine after that. Not sure what's causing it. I have not had much time see if it happens with other aircraft. I was using the experimental version on FBW A320 with FS2Crew when it happened. 

 

I've had this problem since VR released.

It only does that behavior for me every now and then though.

Yes I am having this exact same issue, horrible mouse lag in VR. It was absolutely fine until SU8 😞

58 minutes ago, rickjake said:

I have this same issue using the beta version.  Starts out fine, then suddenly the mouse gets very slow and stuttery (using VR). Both times it had cleared up after takeoff and worked fine after that. Not sure what's causing it. I have not had much time see if it happens with other aircraft. I was using the experimental version on FBW A320 with FS2Crew when it happened. 

 

I think we all need to report it, then.  Clearly it's not just me... 

I'm flying the stock Cessna 172 from stock airport EGBB.  As an example: One flight just couldn't get off the ground.   Next flight was pretty dire on the ground (ATC getting really mad that I couldn't get to the dialogue box to answer) then in the air suddenly OK, including ATC dialogue, and for most of the flight. Then on finals gone again.

I've double checked nothing was running or downloading in the background.  Have never had this issue until SU8

It's a bit maddening!

Thanks for the input, folks

Do you have the Thrustmaster TCA Airbus throttle? I have just been playing around. The engine start selector switch if set to “IGN/START” causes the mouse to lag really badly. When switched to “NORM MODE” the lagging stops. Can anyone else confirm this?

 

I've just logged a bug on the MSFS forum here if you want to add your votes:

SU8 Mouse problems - Bugs & Issues / Virtual Reality (VR) - Microsoft Flight Simulator Forums

23 minutes ago, rocketlaunch said:

Do you have the Thrustmaster TCA Airbus throttle? I have just been playing around. The engine start selector switch if set to “IGN/START” causes the mouse to lag really badly. When switched to “NORM MODE” the lagging stops. Can anyone else confirm this?

 

I'm using a Honeycomb throttle block and have been using only throttle, flaps and mixture on the flights which have been affected by this problem.  Ailerons and elevator only on a Thrustmaster T16000M and rudder and brakes only on a Thrustmaster rudder.  All other control manipulation was (attempting to be) with my wired mouse in the VR cockpit

 

Old Bug that was reported long ago but still not fixed:
https://forums.flightsimulator.com/t/mouse-problems-in-vr/438179/29

It has only become apparent in SU8 though? You must be talking about the beta.  

never had issue with lagging mouse here.  su8 fixed rain/snow in VC while in VR.  all working good so far.

22 hours ago, rocketlaunch said:

Do you have the Thrustmaster TCA Airbus throttle? I have just been playing around. The engine start selector switch if set to “IGN/START” causes the mouse to lag really badly. When switched to “NORM MODE” the lagging stops. Can anyone else confirm this?

 

Yes, come to think of it, That's when the mouse lag disappeared on my last flight. When I switched back to "Norm Mode". 

I think I may have got somewhere!

On the MSFS Forum where I have logged the bug, one poster said this:

"I’ve had this problem after previous updates and have managed to fix it by increasing the dead zone of my rudder pedals as it turns out msfs couldn’t cope with a slight input from a controller as well as move the mouse in VR at the same time!"

This triggered a thought and may have led to a solution to my mouse problem.

The link is that my other problem since SU8 was related to the rudder response. It seemed to be much less effective than previously.
What I did was, while running up the engine at the airport, was to take an external view of the aircraft and then touch the HOTAS rudder pedal - the Cessna rudder immediately started to judder very fast and at a very small deflection and would not travel to anywhere near its normal travel. It looked to me like there were possibly two control bindings operating - one trying to deflect it and one trying to centre it at the same time.

I checked my rudder bindings and couldn’t find anything wrong and nor could I find any duplicate HOTAS bindings. However, I reverted to ‘Default’ bindings and hey presto - the rudder started to act normally.

I then had the thought that the times when the mouse was causing grief previously was probably also when I was using rudder…I’m a lazy flyer and tend to take my feet off the pedals during AP cruise.

So I did some repeat flights with both Cessna’s - and the mouse is now behaving perfectly. For completeness, I will go back to my custom rudder binding tomorrow and see if I can replicate both the problem and the solution.

So - I am not saying that the rudder is the problem in all cases. But I am suggesting that it may be similar clashes of other control manipulations that is affecting the VR mouse response.

If I can replicate both the problem and the solution in my case, I’ll let you know

Edited March 1, 20224 yr by AJZip

@AJZip I noticed similar juddering with most control surfaces from time to time, turned out my HOTAS joystick was conflicting with (then) new Yoke. Increasing the dead zone slightly has helped this issue, so I'll check the rudder pedals and mouse movement soon to see if that causes the mouse lagging (I use VR). I'd read that thread yesterday but forgot about it until you mentioned it again, so this post is more a reminder to myself 😁

16 hours ago, AJZip said:

I think I may have got somewhere!

On the MSFS Forum where I have logged the bug, one poster said this:

"I’ve had this problem after previous updates and have managed to fix it by increasing the dead zone of my rudder pedals as it turns out msfs couldn’t cope with a slight input from a controller as well as move the mouse in VR at the same time!"

I can confirm this. I had the very same happening with my Saitek yoke (Even before SU8). There was a very small spike in the center of the aileron axis. This minor spike caused the mouse to lag badly. After I increased the dead zone a little on this axis the mouse lag was gone.

Well, sorting out the (new!?) binding clashes on the HOTAS controls has, I think, sorted the VR mouse issues for me.  I have now done a number of flights in a number of aircraft - ASOBO and 3rd Party - flying from and to stock ASOBO airports and 3rd Party-enhanced airports.  In all cases the VR mouse is now fully behaving itself both in the air and on the ground and is now better for me (see below) than it was in SU7  

I am pretty certain that some of those bindings had changed with SU8, which is odd, but certainly all flights now are back to the VR mouse being stutter-free.

That has meant that I could at last investigate two of the improvements that SU8 was supposed to have introduced:

- the HOTAS controls becoming non-operable when the VR mouse arrow was on a dialogue or menu box.  Yes - that issue does indeed appear to be fixed 🙂

- the VR Controllers becoming usable.  Yes - even the infamous Reverb controllers.  Now very usable 🙂

 

So - has anyone else who has had the same issues with the VR mouse had chance to track down some similar control binding clashes?  And has it fixed the issue?  If so, then I will update both this and the MSFS threads to flag this as a possible/probable solution.  If not, I'll leave them to run as an ongoing issue.