The online racing simulator
Screen lag glitch and FFB steering wheel disables
I have a weird glitch. I have a Moza direct drive wheel and I have everything set up and working. The game will play fine and play for some random amount of time with zero issues.

Then at some random point I will get a screen glitch like the whole game lags briefly, and then it continues on. When it lags like this is dropps the wheel. The FFB stops completely and the wheel is loose. It stops reading steering inputs entirely, and the axis is locked at whatever position it was during the glitch. All other controls remain normal, all other axis work without issue. It's just the steering wheel.

In windows the Moza Pit House apps shows the wheel and the current angle fine. The wheel is lit up, and everything seems ok.

I can also do nothing besides close LFS and restart LFS touching nothing else, and LFS picks up the wheel axis again and the FFB is on again.

I don't know what the game is doing during this event or why it seems to lose and not be able to recover the steering axis or regain FFB. I also don't know why it's only that.

I haven't played LFS for a number of years, but I used to run an old Logitech G37 wheel for a few years with zero issues.

It acts like a communication problem, but it shows in Windows fine, including real time angle changes while LFS sees nothing until I restart the game.

Is this a known issue?

Any feedback on what I'm experiencing?
resetting controllers (shift+c i think) doesn't work?
I had the same issue. The wheel kept disconnecting at random times during gameplay.

I fixed it by completely closing the Moza Pit House software before playing LFS. I only open it if I want to adjust some settings.

Some people also suggest disabling power saving for the USB device of the wheel.
Didn't know about the reset, so I'll check that.

I certainly don't need the pit software running (I don't think) to have stuff work, so I'll try that too.
** Best answer **
I figured out the issue. It was power options USB sleep settings. I recently upgraded to Windows 11, and I guess it just assumes a desktop PC needs battery saving features enabled???

The dumb thing is they hide the setting by default, so step one is enabling access to it in the first place, restarting, and then disabling the power option setting.

There's a bunch of Microsoft posts about it and some Youtube videos I found to enable actually seeing the setting and making the change.

I've done a bunch of laps and no issue at all.

What originally pointed me to the issue was Moza Pit House closed did nothing, and I was running BeamNG and constantly getting both the steering wheel and the handbrake (but oddly nothing else) disconnecting and resetting. I pulled the handbrake maybe thinking it was doing something goofy, but the steering wheel alone was still doing it. So multiple games, multiple components. I dug into it more, and it seems like USB constantly disconnecting is a common issue.

So all is fixed, and it's Microsoft's fault! lol.
Happy that you found the solution. I had the same issue and for a moment I thought that my Moza was about to yeet itself. In the end I also disabled all power saving options (one by one) and suddenly the issue was entirely gone. I even contacted Moza about the issue and they sent me out a new USB cable as they believe it would be an usb cable issue. Fortunately just OS side issue.
Happy racing!
I have USB sleep disabled and MOZA Pit House not running and yet it happened again during a race today Frown
Well, it still happens, just less. This was a part of it, but there's still some issue. I can do a lot of laps without issue now which is must better. But now it seems more to revolve around loading/timing of things. It will happen often at the beginning of the race, if I load new cars, etc. If I play with AI it happens a LOT more. It mostly seems to be a syncing problem of some sort, but I have no clue what or why. I'm no longer getting actual full disconnects like with the sleep issue, but I am still getting force feedback and dead wheel issues, just now with out the actual full on disconnects. So it's better but still...something.

I'm not lacking on computer either, modern system built a year ago, 14900K, 4070 Ti, not short on performance. It could be something goofy like a USB power issue or USB 2.0, 3.0, etc. For example, if my Quest 3 is plugged into the wrong port, it doesn't work. Maybe the wheel is sensitive also to specific USB ports. I'll start moving it around to see if I can put it on one that is more stable? I'll need to play around a little bit. I might also look into maybe a powered USB hub or something since it could be a power issue? I have no idea.

Again, much better, no actual disconnects now. I'm not actually dropping the wheel or anything now which is good. But it still has random hick-ups that just seem to throw away steering. It just seems to lose that axis. When it happens there's always a slight pause in the gameplay. It studders briefly every time it happen. It seems if the studder is short enough, nothing happens. But if it's too long, something times out or gets dropped.

This also happens with the Pit House program closed, so it's not that. I also have no other Windows notifications or popups during it. I could see something pulling focus away as a possible fault mode, but there's nothing.

I'll keep fiddling around and see if there's something critical that's happening. So far I can move the USB location, and this does have an effect. Different ports do seem to be more or less stable. I'll keep playing with that and see if the wheelbase just isn't happen with certain USB generations???
#9 - cuni
Boy I cant wait for October.....

If the power plan affected the frequency of the error, maybe look into the ultimate power plan
This may be an issue of the wheel itself. In DIY community when people make their own DD wheel, a lot of times similair problems happen because of electromagnetic interferrence. To run the motor a high current is passing at a high frequency through the motor coils. If the wiring is not done with extreme care to shield and ground everything the interferrence is strong enough to dissrupt usb comms. Ground loops are also a thing, so as correct earthing.

You can check if this is the case simply by setting the FFB to zero. If you don't get any disconnects without ffb, then I would say it's clear where the issue is. The usb suspend is very fishy, because this is only active if the computer is sleeping or if the usb device is not being actively used (this is very unlikely to trigger durring normal operation of a wheel).

I don't want to say that guys at moza didn't do their electrical homework correctly, just that it may be possible. Or particulair user issue where improper earthing or ground loops where accidentaly created.

FGED GREDG RDFGDR GSFDG