An important post-script to my last post above.  A member of the MSFS forum posted this reply to my identical post on that forum:

"I experienced throttle bugs/issues after SU8 with my HOTAS One using my previous custom profile. Every aircraft I tried after SU8 had a throttle that behaved differently. Some needed reverse some non reverse axis and the CJ4 even had left throttle being increased while simultaneously causing right throttle to be decreased! Absolutely no reason for this as settings in my previous profile hadn’t changed. Only SU8 installed.

Solution:
Like you, I reverted to ‘default’ profile for the HOTAS One and hey presto they all worked again. This despite all throttle settings appearing to be identical in both the default profile and my old custom profile.

I’d really recommend anyone with input device issues post SU8 to go back to default profile for that device first then add back in any customisations.
The good thing for me is that my custom sensitivity settings for the HOTAS didn’t revert to ‘default’ by doing this.

All aircraft now behaving the same now from a throttle perspective."

 

So there you go!  SU8 has inadvertently messed with the HOTAS settings...and that has messed with a number of other things. 

I love these forums 🙂

 

 

Update on my end; the Mouse Lagging is (was fingers crossed!) much worse after SU8, before it was very random and only happened once so often, with SU8 it's practically every flight. So I went into the Controllers Menu and added 5% Deadzone to every single USB Device/Controller in there that had a Sensitivity Option - That appears to of done the trick.
Originally I thought it was Rudder Pedals as posted in the pervious page, but they were already at 5% deadzone, so I think it may of been my Xbox Controller, either way I just added 5% to every single one as I don't have the patience to go through them all individually to find out exactly which one could've been the issue (I have a lot of USB devices plugged in).

Thanks, @MarcG  The issue definitely somewhere in this kind of area.  My solution didn't need a change in deadzone but maybe that's because I changed all the bindings, deadzones and all 😄

If I find any more clashes, I'll try your solution first and see if it does the trick 🙂

 

Since SU8 using the menu bar has become a real nuisance. Sometimes it works but often the menus don‘t respond and when I press TAB the one I opened the last time pops up. Especially the radio and Navigraph menus often don‘t respond. Does anybody know how this can be solved? 

On 2/28/2022 at 8:46 PM, 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 have the exact same problem! Surprised not more people reported this problem. Seemed to have started after SU8. I can barely move the mouse and it stops the moment I set the start selector back to NORM.

Edited March 26, 20224 yr by theother1

9 hours ago, theother1 said:

I have the exact same problem! Surprised not more people reported this problem. Seemed to have started after SU8. I can barely move the mouse and it stops the moment I set the start selector back to NORM.

Interesting.  I've recently bitten the bullet and bought a Honeycomb Alpha yoke system - that also has a magneto/start switch.  Next time I fly I'll see if I can replicate the problem.

There is a theme coming through, though.  I can't figure why these issues 'arrived' with SU8, but many, if not most, examples I've seen is when there are - often unknown and unintentional - multiple commands existing for the same action.

So one command is saying 'move' and the duplicate command is saying 'stop'.  Sometimes you can actually see it happening - the control surface, or pedal, or switch judders visibly without responding to the intended movement as the two commands act and counteract each other.  And while this is happening, the CPU is pulled into a loop and everything else starts lagging.  

I have found that going into the control bindings and searching by name - and sometimes you have to do multiple searches if the duplication is across multiple bits of HOTAS kit - usually reveals that there are duplicates dotted about.  Delete the unwanted duplicate often/usually sorts the problem.

As I say - why this wasn't a widespread issue pre SU8 is beyond me...but I suspect that it's something to do with new 'default' bindings set for the myriad of HOTAS options we tend to bolt on and/or the treatment of the carried-forward custom bindings from earlier updates.

I am tempted to junk all of my custom bindings and see if starting from scratch with all bits of kit starting at 'default' and rebuilding them does the trick...but that's a big job and the duplications might well be (probably) in the 'default' assignments.

Edited March 26, 20224 yr by AJZip