-
-
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
Cursor ocassionally stops (input thread stutter) #27227
Comments
Tracked at ppy/osu-framework#6181 |
Keeping this issue open and pinning to give visibility for anyone else coming to report it, since it's been reported over 5 times in the span of few days. |
Tried both turning off and on this option, but the problem still shows up |
For my experience, I have a kind of 2 types of input lags: sudden stop and delayed movements, and luckily I am able to record them. For the type with sudden slow cursor movements, I have experienced for periods vary from a few hundreds of milliseconds to a few seconds. And sometimes coming with rendering lags, but it seems like it would be another problem.
2024-03-11.22-26-13.out.mp4
2024-03-11.23-00-00.out.mp4From #9283 (the case with rendering lag), it is mentioned that it might be GC-related, but for my recordings, no apparent relationships to GC can be found. In the mean time, I will still try to collect more information related to the lags and delays as useful as possible. |
This time. I have tracked on the logs and probably found that it might be related to the slow frames on the threads. 2024-03-13.00-51-08.out.mp4Here, I used 2880x1620 DSR for my 1920x1080 monitor, and 8 font size instead of 12 (default) for the terminals. |
Having the stats open probably does that, and is probably not related. Also having windows displayed above the game, and potentially the game not focused, will not help. ALso it's not running in fullscreen mode since windows are being displayed. @BenCheung0422 Please open a separate discussion for your issue (or better yet, self-troubleshoot), it's not the same issue as what is being tracked here. |
I am not sure if stats affect that. Also, in the video clip, I used OBS so that the console windows on the back can be rendered in front of the game window. Yesterday, I just captured the moments with cursor movement pauses. I will try to record with stats opened and see if I can capture the moments with slow movements. It is like there is frame loss in input threads in this case. I will open a new discussion (or issue) for this. |
I had this problem too and switching from Multi threaded rendering to Single threded fixed it for me |
i had a few input stutters in the last 2-3 weeks, and recorded one tonight here's the clip: the logs: specs (dunno if you have them in the logs but in case):
if you need further details don't hesitate to @ me edit 2: happened again, also have clip + logs if needed |
@iwa I think they are still working on it to fix this issue. |
ikik but as it seems to be kind of an awkward issue, the more logs / cases they can analyze, the merrier i guess? |
What i find interesting with this issue is that i'm playing lazer for years but it only started occuring around feburary this year. |
That sounds like conflating two issues with different causes unless prime95 is doing windows input hooks for whatever reason which I find unlikely. |
Not sure, could be some weird windows services, update or whatever program in the background causing this. Edit: |
In my opinion, I would think this might not be really related. In my observation, there are mainly 4 types of threads: input, audio, update, draw. Certainly, draw (rendering) would be mainly handled by GPU threads alone, either single or multi-thread, and both input, audio and update handled mainly by CPU process. Lagging in threads absolutely can have several causes, including but not limited to: background services, process bottlenecks, library/API (including Windows API) incompatibility, driver incompatibility, driver or service errors, incompatible BIOS configurations, etc. In my case, there is only a hanging in input thread is the cause of input lagging, as what handled by the coming changes. It seems like their believe is the issue related to some incompatibilities of Windows API input handling. Also, certainly, stressing CPU can cause all the threads (and processes) lagging as mostly they are handled by CPU, doubtlessly, so it might not be really related. |
something is definitely wrong on the rendering side I was having the freeze issue with Valorant so I disabled GPU Scheduling (windows 11), and my issue worsen drastically, to the point where my tablet would sometimes freeze and dont respond at all unless I restarted opentabletdriver I can retrieve clips & logs if needed |
@iwa unless you can produce a video with frame graph showing (ctrl-f11) any speculation that this issue has anything "to do with the rendering side" is unsubstantiated. i don't even know if you're trying to report the same issue which the OP is. |
fair enough, I should be able to provide a video proof sometime during this week |
For your information, this case we would have this kind of situation or otherwise it should be another issue. Here, you can see that in the graph (by clicking twice CTRL-F11), you can see there are tall lines in ticking thread graph but not any observable and obvious tall lines in rendering thread graph. If you case is different (like rendering lags), that should be another issue. EDIT: |
alright, thanks for your clarifications after reviewing the original clip i posted, i can understand that y'all feel like it's a different issue (clip is cutting during the stutter for whatever reasons), but i'm pretty confident that i get stutter like OP does, or at least it feels the same the only thing that makes me think it's rendering-related is that, strangely enough, input stutters totally stopped when i switched to Single thread rendering mode, but without any proofs my thinking is pointless, so i'll work on that edit: after re-reviewing my original clip but at 0.25x, seems like i'm wrong & we can clearly see the input stutter happening, but still no frame graph so still pointless edit 2 on 24/06: im not dead lol, still doing testings but i havent been able to replicate the issue since switching to single threaded rendering. even though i've set back to multi threaded for testings, no issues so far. strange. |
i might have an idea what is causing this. |
I have none of these software running, but seemingly it would interact with windows input and could cause delays in osu input handling, as osu at the moment is not handling with really raw input signals/events. Edit: By the way, why would people use input mapping apps when playing osu? Though I am not sure if tablet pen driver affects. |
i have never used this kind of software, always disabled steam input, and using a controller only when playing RL, controller is disconnected otherwise i don't fully exclude steam hypothesis tho, will try to test with steam opened and steam input enabled i was thinking about it but couldn't it be a regression with old lazer installations? something that maybe would "magically" get fixed in the local config by updating the single/multi threaded setting? |
Had the same issue, tried switching from multi thread rendering to single thread rendering and it seems to be fine now. |
@ni5arga if you switch back to multi threaded, does the issue reappears for you by any chance? |
It does not help anything for my case. Logically, rendering is tacked by renderer (either GPU or CPU), but input is tacked by CPU, so there seems to be no obvious intersection between them. However, changing max FPS value may change something, but the input thread would still be 1000Hz (for me). Edit: Actually, different computer configuration may give different results. |
For me this can be easily replicated if you switch between full screen and windowed mode on windows 11 multiple times, the cursor lag will getting more noticeable (especially with high precision mouse on). The easy fix is just quit the game and reopen it. |
Also facing this issue - on macOS. Have been for a long time. |
The poor performance on windowed mode would be expected as it is not as optimized as full screen mode. This includes rendering and also other window-related events (as well as input events). However the situation should be optimized, especially on full screen mode. |
@MEMORIEmusic I have the same issue since I started playing on macOS. I have a video (recorded a replay with OBS, to not affect performance) in this discussion #29782. Tried with playing borderless, fullscreen and windowed, all to the same effect. |
I was playing a bit now while warming up and got 2 replays in the same map recorded from when it happens, different places and different amounts of times it happens: First try (happened once): video2024-09-10.16-48-24.mp4Second try (happened twice: videos2024-09-10.16-45-28.mp42024-09-10.16-46-16.mp4 |
I have also been facing this issue on the macOS version. It happens practically, and it usually kills my SS runs. I have tried everything suggested in the thread, and nothing has worked. |
Type
Game behaviour
Bug description
After updating lazer I've discovered a really annoying thing: when playing STD (may also happen in Song Select menu) cursor ocassionaly stops while dragging tablet pen and after some time just "teleports" to the point where the pen is currently located. It happens anytime during gameplay and it is especially irritating when it happens at the end of a song.
Screenshots or videos
issue.mp4
Version
2024.131.0
Logs
compressed-logs.zip
The text was updated successfully, but these errors were encountered: