Skip to content
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

Auto-clicking the slider when hovering with the cursor #486

Open
SayoriArt24 opened this issue Feb 20, 2025 · 7 comments
Open

Auto-clicking the slider when hovering with the cursor #486

SayoriArt24 opened this issue Feb 20, 2025 · 7 comments

Comments

@SayoriArt24
Copy link

The problem is -
With the classic three-finger game (two makeshift click buttons and one cursor) when you hover the cursor over the slider, it spontaneously triggers without pressing with two other fingers, and there is a noticeable delay between the map and the sound (shifting the offset does not help)
I've already tried to tweak the sound synchronization, what is possible and what is not, but nothing helps
On the old phone everything was fine, but only at 60Hz
Phone - Xiaomi redmi note 13 4g
Android 15/Hiper OS 2.0.5.0
Screen refresh rate 120Hz

@Rian8337
Copy link
Member

"It spontaneously triggers" - what is "it"? Tracking state? Hitsounds? Anything?

The desynchronization between game (beatmap) time and audio time is expected - this is aimed to be improved in the next version. It is not an easy task though, so it will take a while.

@SayoriArt24
Copy link
Author

SayoriArt24 commented Feb 21, 2025

"It spontaneously triggers" - what is "it"?"
"It" - Slider
When you simply hover over the with the cursor and do not press anything else, it is triggered automatically, which is confirmed by the sound of the hitsound (if you do not press anything else, then there is no sound at the end There will be no and there will be a combo failure.
The delay and this problem really hinders playing fast maps.
I am very grateful to everyone for answering and working on the problems, thank you very much in advance)

@Rian8337
Copy link
Member

It sounds like you are not aware of how sliders work. It wasn't triggered automatically. You were entering what is called the "tracking" state. The hitsound that was played was from the slider's body (either sliderslide or sliderwhistle) because you were in a tracking state.

There were no judgements that were done, because you did not press the slider head until its judgement time window had passed, which caused you to lose combo.

@SayoriArt24
Copy link
Author

I recorded a replay for clarity, where you can see self-triggering in places where I don't specifically click anything other than the cursor.
It is not possible to attach a video here, so I will attach a link to Google Drive, If it doesn't open, then write where you can send the screen recording.
https://drive.google.com/file/d/11QV2gdsgJYaIVQsL7ysi_SrgtGEd55l8/view?usp=drivesdk

@Rian8337
Copy link
Member

Yes, that is how slider judgement works. Slider ticks, repeats, and end rely solely on your tracking state (denoted by the follow circle). You do not need to tap anything. However, they will remain unjudged as long as the slider head has not been judged yet.

@SayoriArt24
Copy link
Author

thanks a lot for the explanation.
and what kind of delays can we expect to solve the problem in future updates?

@Rian8337
Copy link
Member

If plans stay, the following changes will be made in version 1.8.3:

  • Game (beatmap) time will be entirely based on audio time, making the low latency synchronization setting irrelevant.
  • In version 1.8.2.1, inputs are registered in the next frame, which causes delays. This is aimed to be improved in version 1.8.3 by registering input directly, but this will be pretty involved, so there is a chance that this may not make it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants