Which you can view in the editor
or something like this
This will make custom offsetting much easier.
here's a related feature request of mine, show how many slider breaks you've got: http://osu.ppy.sh/forum/t/99368
forum
[result screen] Display average mistimed hits
posted
Total Posts
35
Topic Starter
Which you can view in the editor
or something like this
This will make custom offsetting much easier.
here's a related feature request of mine, show how many slider breaks you've got: http://osu.ppy.sh/forum/t/99368
YES PLEASE.
It's pretty helpful in osu! stream. This would also help us figure out which old maps suffered from incorrect offsets after a single playthrough. And help newbies figure out their preferred universal offset.
It's pretty helpful in osu! stream. This would also help us figure out which old maps suffered from incorrect offsets after a single playthrough. And help newbies figure out their preferred universal offset.
Allowing toggle display between scores and hit error when you watching your replay may appear to be more helpful.
I'd actually like this to show during actual play too.
Yeah, agree with this. In osu! droid there is a feature like this, and it's very useful in customizing custom offset. 
And like xsrsbsns said, show it during actual play too >.<
And like xsrsbsns said, show it during actual play too >.<
Topic Starter
That'd be cool.woc2006 wrote:
Allowing toggle display between scores and hit error when you watching your replay may appear to be more helpful.
Meh, that'd be better than nothing, but I'm not sure if I'd want to wait a whole 3 minutes or whatever just to see the final results... Watching replays always seemed like such a chore to me.
Supporting this.
Any form of showing how off you are would be very useful, even though most times I can determine if a map is off by listening to the slider ends...
Any form of showing how off you are would be very useful, even though most times I can determine if a map is off by listening to the slider ends...
brilliant +1
Last Remnant_old
Topic Starter
not while they play. after they played. >:Last Remnant wrote:
Definetely helpful, but if it can come with a toggle, it will be better (some players may not like bunch of infos and numbers while they play)
after they played.
after they've played.
Edit: Yeah, I saw that. I was correcting Yoda, so would love if I wasn't told to f-off.
Edit: Yeah, I saw that. I was correcting Yoda, so would love if I wasn't told to f-off.
Topic Starter
I'm going to bamp this.
Topic Starter
maybe I should just bump this. I would find this extremely useful.
no, i dont want that. i just dont think its a good idea, probably it will just frustrate more than what it will be useful.
Yes, I would find it useful for changing offsets more accurately and efficiently.
I guess this should just be added to the *advanced* result screen planned for the future. I'm sure I saw that somewhere in here, I'm just too lazy to search for it.
Topic Starter
whatArmandoR wrote:
no, i dont want that. i just dont think its a good idea, probably it will just frustrate more than what it will be useful.
Topic Starter
thanks a lot!KaosFR wrote:
Supported
be nicer if it was easier to find. plus i can't see the average mistimed hit. only the hit range(if that makes sense)
What's "Unstable Rate?"
Topic Starter
I never fully understood that either.Oinari-sama wrote:
What's "Unstable Rate?"
While we're at it, having a percentage for hit accuracy, not score accuracy (100s, 50's, etc), would be nice.
For unstable rate, I heard from someone that it's your mistimed hits added together (so having a 0 would be perfect), however they were unsure themselves.
For unstable rate, I heard from someone that it's your mistimed hits added together (so having a 0 would be perfect), however they were unsure themselves.
Getting a bit osustream up in here aren't we 
I'm beginning to suspect that the "Unstable Rate" is either:
- Sum of {Absolute Value of [Hit Error of each Beat]} in ms
- or something similar to the Standard Deviation in statistical term, maybe with a few simplifications...
The lower the unstable rate the better the timing accuracy you played~
The unstable rate is just that - how unstable you are. Hitting 10ms early and 10ms late alternatingly will make your unstable rate swell, while constantly clicking 20ms early and 15ms early will keep it low. That's basically how it works, but where the actual number comes from is a mystery.
Basically this. Which means if you hit 20ms early and 20ms early again will result in 0 Unstable Rate.MillhioreF wrote:
The unstable rate is just that - how unstable you are. Hitting 10ms early and 10ms late alternatingly will make your unstable rate swell, while constantly clicking 20ms early and 15ms early will keep it low. That's basically how it works, but where the actual number comes from is a mystery.
I actually don't like how current "Hit Error" works. There should be a "Peak Hit Error" or something.
L33T post count is L33T
I recently checked what a "mistimed hit" in the editor actually is. With the map set to OD9 you can get a 300 but still get a mistimed hit, and with OD10 you can get a 100 but a correct hit. Therefore, a mistimed hit is somewhere between OD9 and 10 accuracy (12-18ms).
So you want pretty much "what accuracy would I get if i had OD9.5".
So you want pretty much "what accuracy would I get if i had OD9.5".
I like this one, so we can adjust offsets accurately...
And I also prefer if we could have a graph or something, aside from just values.
And I also prefer if we could have a graph or something, aside from just values.
Yup, clicking on the accuracy could open a graph or something. Would be pretty handy.