After updating Nvidia driver I noticed now that when flaps are set, every time I move the throttle the flaps move to the full retracted position. This occurs regardless of what airplane I am flying. I have remapped both flaps and throttles but the problem still persists.  I am assuming that the Nvidia driver update has something to do with it, but before I rollback the driver was wondering if anyone might have any other ideas as to how to fix the problem.  Thanks

Rodger

It’s not impossible but highly unlikely this has anything to do with a video driver. I would recheck your control bindings first. 

3 minutes ago, snglecoil said:

It’s not impossible but highly unlikely this has anything to do with a video driver. I would recheck your control bindings first. 

Already have.  No change.

I observe this occasionally, too. My guess it's related to one of the more recent sim updates. I am sure this never happened before SU7. Then, at a point, flaps went through the full range nearly every time when I shifted them one notch only (mostly C172). Later, I think after a certain beta, this was mitigated and only happens now and then since.

I was hesitant to report this to Zendesk as I operate flaps virtually alway using the Saitek Multi Panel, even under VR where I find the flaps lever blindly. Plus, the Saitek Panels are driven via SPAD.neXt. There are just too many variables involved in my system to trace what's going on.

Thus I am very grateful for your report. I will keep a closer look upon this now.

To supplement. When I (rarely) operate the flaps lever using the mouse under VR, it always shifts one notch only as it should.

As Chris @snglecoil states I find it unlikely to be caused by a Nvidia driver update.

Kind regards, Michael 

Ok, just an update.  I forgot to mention after updating the Nvidia driver, every time I went to start MSFS, I would have to start it a second time as it would freeze.  The second time it would load, however the flap problem was still there.  After trying everything I could think of I finally rolled back the Nvidia driver and now everything is back to normal.  

That’s a head scratcher for sure. Glad that resolved it for you.

Just now, snglecoil said:

That’s a head scratcher for sure. Glad that resolved it for you.

Yep.  I don't get either.  But it worked so glad to be back in business.  Thanks.

Which driver are you on now? I'm on 511.23. Installed Jan 15.

Kind regards, Michael

7 minutes ago, pmb said:

Which driver are you on now? I'm on 511.23. Installed Jan 15.

Kind regards, Michael

472.12.  Rolled back from 511.23.

Edited February 26, 20224 yr by RodgerC

Thanks. I think I had this for quite some time, too, and this was before the flaps issue started. 

Not sure if I should roll back, though. This is a mystery.

Kind regards, Michael

Edit: I think I had one more driver in-between.

Edited February 26, 20224 yr by pmb

1 minute ago, pmb said:

Thanks. I think I had this for quite some time, too, and this was before the flaps issue started. 

Not sure if I should roll back, though. This is a mystery.

Kind regards, Michael

Edit: I think I had one more driver in-between.

My problems started immediately after I upgraded the driver.

This is why I never upgrade a driver that is working perfectly. \. If it isn't broken, I don't fix it. 

The 472 driver is for Win 10. I use these. They never change.

ns

Edited February 26, 20224 yr by bean_sprout

1 hour ago, Bobsk8 said:

This is why I never upgrade a driver that is working perfectly. \. If it isn't broken, I don't fix it. 

Good point.  I hesitated to upgrade.  A month or so because everything was working well.  Learned my lesson.