Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@dani211e
Copy link
Contributor

This is a feature I personally would enjoy, but I haven't really seen (or found) any related discussions. I thought a direct PR would be fine since it's not a big feature, so if the devs don't see it fitting in the game feel free to close.

out_reencoded.mp4

I wasn't sure whether to remove the ShowMovingAverage toggle and have a None style instead, since I don't know how lazer would handle/migrate that for existing skins, or importing previously exported skins prior to the removal.

@bdach
Copy link
Collaborator

bdach commented Nov 27, 2025

@peppy pinging to gauge if we even want this before I even consider review

@DarkStoorM
Copy link

I'd like to leave an idle comment why some people might want this, but it's mostly from my own perspective, feel free to ignore/nuke.

Since we have an automatic offset adjustment anyway and we don't have to pay attention to the hit error, sometimes I like being able to take a peek at a very specific part of the map, if I was unstable during x or y or just see what happened but with actual timing values, not only where the hit events landed on the graph.

Yes, the visual representation is enough to tell you if you are doing bad just by reaching green section or if your play is all over the place, but on high accuracy settings I assume you'd want to see those numbers as low as possible, even if scattered.

It might sound silly, but some people just like numbers. Might be a personal preference, replay analysis, live preview when livestreaming, and so on. I do that with other components on osu!taiko too, e.g. splitting HitError/UR into Rim/Centre, having 6 of them on screen, as silly/useless as it sounds for others.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants