Support!
I don't mind seeing 2 decimal points like osu!tploldcraft wrote:
But its not always a round number. For example dt ar9 is NOT ar10
(Unless you want to put decimals...)
And that's fine. Most people use the convention AR10.3 for instance, and that would describe that it is a bit faster than AR10. Do you know off the top of your head that OD7+HR is OD9.6? Showing that would describe that it's not as hard as OD10, but is Harder than OD9. Decimals to one or two places would be appropriate IMO.loldcraft wrote:
But its not always a round number. For example dt ar9 is NOT ar10
(Unless you want to put decimals...)
But it's 9.8 :cNvirjskly wrote:
Do you know off the top of your head that OD7+HR is OD9.6?
See this is why we need this feature.Luna wrote:
But it's 9.8 :cNvirjskly wrote:
Do you know off the top of your head that OD7+HR is OD9.6?
Imo having hit windows display will be an improvement over current system. Now people will know exactly what the time scale is on the hit error bar (without looking things up)Tom94 wrote:
Since the upcoming new stars are planned to adjust to chosen mods, it'd only make sense to have this display adjust, too. There's nothing speaking against implementing this.
One tricky thing, though, is, that OD is not only the hitwindow, so there is no sensible way to adjust it when DoubleTime / HalfTime is applied. A possible solution would be to show the HitWindow(s) instead. That could also overcome the misunderstandings rising from having different OD scales for each mode.
I think it could be done with one of these:Tom94 wrote:
I made HardRock and Easy change the values displayed. However I am not sure how to go about changing these values with DoubleTime and HalfTime, since these mods just make the map play faster rather than actually changing these values. This means, that displaying different values as OD and Drain is plain wrong. There would be different results when basing on 300s vs 100s etc. Any suggestions?
DT could be treated exactly the same as ar, for example. Where od=7 , with dt is od=9 . Or where od 8 , with dt is od=9.6 .according to this chart. (And i did the math to be sure, realizing the values are slightly approximated)Tom94 wrote:
I made HardRock and Easy change the values displayed. However I am not sure how to go about changing these values with DoubleTime and HalfTime, since these mods just make the map play faster rather than actually changing these values. This means, that displaying different values as OD and Drain is plain wrong. There would be different results when basing on 300s vs 100s etc. Any suggestions?
OD7 with DT has the same timing window for 300s than OD9, but the timing windows for OD7+DT for 100s and 50s are stricter than for OD9.xasuma wrote:
Im not sure what you mean by basing on 300s vs 100s.
I'm leaning towards showing base OD with an indicator (eg OD7*, OD7+ or Option A).Full Tablet wrote:
For example, OD7+DT has the same timing window for 100s than OD10.4167 (10.5 if rounding down to the nearest millisecond)
Comparing with 50s instead, OD7+DT would be OD11.267 (11.3 when rounding)
(Extrapolating linearly the timing values from the tables for values over 10).
I would just like to point out that OD7^ (like it is now) is more or less ... meaningless to me. Unless I only play or play tons of DT (in which case its still meaningless because I can just look at the base AR/OD/HP). Similarly AR7^ is useless. I know its base is AR7 before even putting on DT because I can look at the base, and I know I have DT on cause i selected it.Full Tablet wrote:
I think it could be done with one of these:
Display OD7+DT as either:
A) "OD7↑"
B) "OD9↑"
Option A is more accurate (the arrow just shows that the timing windows are tighter than normal OD7, while still being technically OD7, since it doesn't change other things affected by OD), but B would show a more relevant value for most players (the timing window for 300 in that case is the same as OD9, the arrow shows that the other timing windows are tighter than normal OD9).
DT/HF support is planned, but it's just a matter of how at this point from what i know.kurufu wrote:
Who knows if this will be seen as it was already marked Completed but that's the end of my rant.
maybe because dt isn't supported yet :pxasuma wrote:
Im not sure if anyone will read this. But when you apply hr and dt at the same time, the ar is not updated correctly.