-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Raw input fails to initialise correctly occasionally #3364
Comments
The same happens to me with a normal wireless mouse, but in a different way: when I launch osu!lazer with the raw input, the mouse works perfectly, but for no reason, it disconnects. When I reconnect it, your same problem happens, and I have to relaunch osu!lazer / disable Raw Input |
What host operating system are you both on? |
Windows 10 Home (64bit) |
Windows 10 |
Similar issue here; on Manjaro (64x) and using a mouse; turning on raw input just keeps moving the cursor to the corners of the window |
Same here, Manjaro (64x) with mouse |
This is still being reported after switching to SDL2, so there must be something more to it. |
Going to move this into the march milestone since it is still being actively reported. Would appreciate anyone that can reproduce this issue (and is able to debug it) to provide more details. Currently I'm not sure at all how this is happening. |
It's kind of weird because sometimes raw input seems to work for me, but sometimes it doesn't (as you can see from the video below): raw-input.mp4Not sure how to 100% reproduce this but I noticed something strange when the raw input doesn't work (you can also see this from the video above):
|
I've had this issue come up a few times for me aswell. The steps below manage to reproduce it 90% of the time for me.
Above was done in windowed and local debug but I've managed to reproduce with both fullscreen and master. Windows 10 The whole window grabbing stuff is probably a bit excessive, I'm guessing you just need to have the osu-lazer window not be in focus on startup but this was the easiest way i could consistently reproduce it. |
Reproduced, will investigate through this and see if I can nail something down. |
I've repurposed this issue to track the more specific case of OsuTK initialisation failure. |
Closing and unpinning as osuTK's "raw mouse input" handler has been removed osu!framework-side, leaving this issue stale as it should no longer be the case, with the alternative "high precision" mode which relies on SDL2's relative mouse input. If it does really matter, this could be tracked at |
When starting the game with raw input initialised, there is a chance it will not work.
Note: this issue thread has been repurposed to track a more specific issue. for tablet related issues, see #3911
The text was updated successfully, but these errors were encountered: