-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Unresponsive cursor in osu!lazer. Inability to move cursor or press MB1 or MB2. #11929
Comments
I can get this same effect reasonably consistently by first: clicking on any other window after clicking the osu!lazer shortcut, and then mashing both mouse buttons while moving it fairly quickly. I tried to get the same effect with multiple different setups; not clicking out of the window, clicking out of the window, tabbing in and let it sit, clicking out of the window, tabbing back and moving the mouse, none of these gave the same effect. My theory (and it's not a good one at that) is that there's some kind of input buffer that gets overloaded from too many inputs at once. No clue how that affects windows other than osu though. Edit: this works for Windows. What OS are you running the game on? |
Windows 10. It happens just after updating to that version and occured 3 times after starting it up with no mashing MB1 or MB2. However now when opening it up, it doesn't happen but I can recreate the same way you have. |
I'm fairly certain this has been happening for a while now, not just limited to this version. I'll edit when I can get on my pc and check older versions, cuz I can't really connect a mouse to my phone now, can I? |
@bdach If I recall correctly, it's been happening to me since December, but not as bad as it is now.
@xzCobra If you have an OTG adapter, you could, but YMMV because not all phones support a mouse. |
As always, we can't do anything unless you provide which settings you are using and which settings it actually occurs on. Please test with raw input on and off, at very least. |
It occured with both
I just managed to get it to occur without raw input, initially I had raw input on |
How did you manage to get it to work without raw input? With the setup I posted yesterday, I couldn't get that to work (although I didn't test it the amount I normally world because I am kinda stuck working around school stuff so I don't have a lot of time on my hands) |
Spamming alt-tab, moving my mouse and clicking and the same with my tablet. It seems to occur more consistently when doing it at start up. |
Interesting. Can't seem to get that to work. (although I might also be off with something) |
yes actually, I was |
Maybe I've overlooked something because I'm having trouble recreating it now with raw input off |
Could you send a screenshot with your settings? Might help when trying to recreate it. |
I also got this bug to happen while visual-testing. The cursor moves if the osu window is not focused, stops responding when focused. I do have raw input on. (the whole visual test does this, not just the embedded osu game) |
@Flutterish If you have raw input on, and can't reproduce it while raw input is off, then that is basically #3364 or falls within it at least. |
Closing as a duplicate of #3364. If you are managing to make this happen with raw input turned off, please re-report against osu-framework with a video showing this happening. |
Describe the bug:
Cursor in osu!lazer is unresponsive to both tablet and mouse. The cursor does not move at all nor does it allow presses to be registered. When focusing the osu!lazer window, the cursor will be placed at the cursor before focusing the window.
Screenshots or videos showing encountered issue:
![image](https://user-images.githubusercontent.com/68469008/109503996-df979800-7a92-11eb-9e74-a73a9ba42f9f.png)
Video of issue here
osu!lazer version: 2021.226.0
Logs:
performance.log
runtime.log
updater.log
network.log
database.log
The text was updated successfully, but these errors were encountered: