Interesting. Support from me.
It's kind of interesting, but why are you interested in adding this if there is already a xx combo written to determine your amount of combos or the max?The problem is you can only see your max combo if you dont want to watch the whole replay. But what if you have, say one combo of 254 and another of 230? The result screen would only show that you had a 254x combo eventhough you had another cobmo that came really close to that.
Ohhh. Now I get it. Support :33Diceycle wrote:
It's kind of interesting, but why are you interested in adding this if there is already a xx combo written to determine your amount of combos or the max?The problem is you can only see your max combo if you dont want to watch the whole replay. But what if you have, say one combo of 254 and another of 230? The result screen would only show that you had a 254x combo eventhough you had another cobmo that came really close to that.
With a graph you could see all the combos you had.
My thoughts exactly. The Combo Graph was merely the idea that seemed most helpful to me at my skill level.-GN wrote:
but yeah, statistics are nice. we could use some more of it, in my opinion.
This actually got me to think...Diceycle wrote:
Is there even enough space in the result screen?
While thinking about this i thought of a system to make the user able to switch between different graphs like switching tabs in your browser.
I approve.VeilStar wrote:
UR - Unstable rate graph, with the middle being perfect hits, and the highest point on the graph being the earliest hit out of all hits, and the lowest being the latest point of all hits. (Kind of like a waveform is structured.)
I think max RPM is enough.VeilStar wrote:
SP - Spinner graph that shows the RPM you spun at at what time, with both a 'text' and 'graph' UR of it.
Thats a great idea. It reduces the load on the interface and is a lot more readableabraker wrote:
And the combo graph. Let's think how that will look like: A reapeating zig zaggy triangle that drops to 0 if you miss. I think a combo graph isn't really needed, but a better way to show that stat would be to put points on the current graph indicating where you missed and make it so if you hover over it, it would show the combo achieved before the said miss. Something like this:
Well, without going too offtopic nor turning this into a whole different feature request...abraker wrote:
<stuff>
i think that would be needlessly complicated - my vision of it was just a simple extra graph overlayed in the window already there. it shouldn't really cause extra clutter except in certain edge cases, and what they represent should be pretty obvious.abraker wrote:
Maybe add tabs to the graph to change between view?