-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Output queue full in kmesg/dmesg #10
Comments
This is the game sending more effect updates than the device can handle. Limiting the frame rate can help with the issue. It happens with other wheels too. |
I decided to hack a bit and changed the |
Might not be placebo, as you've essentially increased the effect's resolution. That being said I'm not really comfortable lowering the timer period down to 2 ms, because I experienced some issues with my wheel when I set the timer that low. The wheel itself would occasionally freeze up, and I'd have to unplug the wheel and plug it back in. Though that was before the resolution we found in #6, so the timing issue might've been also been affected by the changes. |
I've now played with the 2ms setting for quite some time and it didn't occur anymore. Neither with ETS2 nor Project CARS 2 under Steam/Proton. |
That sounds promising. I'd still like to test it out on my own wheel. I could also just set the timer to be a module parameter, so users could set their own timers, if I find out that different wheels have different tolerances. |
So i've played Assetto Corsa Competizione, and this might give you a hint: |
Yep, thanks, I'll try it out on my wheel as soon as possible. Not 100% confident in pushing such a change without some testing by myself. |
Hello again, sorry for the long delay. I added in functionality for setting the timer period when loading the module, either by Check that everything is alright and we can close this issue. |
I would do the opposite: set it to 2ms and add an adnotation in the readme
that the previous default was 8ms, and that in case it's unstable for
someone, they should tune it up higher. As i've stated in both issues (the
one about missing/invalid effects) the 2ms seems to be the more stable and
less problematic setting overall.
|
I'm sort of on the fence about it. You're absolutely right that changing the timer has cleaned up the console spam on your setup, and the increased resolution is definitely a plus. But I'm not really comfortable with the thought that some people's wheels MIGHT crash the first time they're trying it out, and then have to go back and see if there's something they can do about it. I'd prefer to make sure that the wheel works out of the box, and if the user feels the need to tune the wheel then they can do so. The output you showed in this thread admittedly does speak for the 2 ms setting, but I don't have ETS2 and no other game has had similar issues. That I own, at least. |
lgtm to me |
After game launch, this starts spamming the console:
Game: ETS2 on Steam (running the windows version via Proton Experimental)
The text was updated successfully, but these errors were encountered: