If you get so many 300's that your client rounds 99.995% acc to 100%, does it still show SS?Endaris wrote:
No.
Definition of SS is not getting 100% but getting no 100s and no 50s and no misses.
A miss is different from a 100. Have you tried that?Yuudachi-kun wrote:
I've tested this with 1 miss and 15,000 notes.
It stayed at 99.99%
F1r3tar wrote:
A miss is different from a 100. Have you tried that?Yuudachi-kun wrote:
I've tested this with 1 miss and 15,000 notes.
It stayed at 99.99%
something something overlap sliders and hitcircles in timeline and break game mechanics something something auto fucks upYuudachi-kun wrote:
How do I make auto get a 100
I was only thinking about osu maniawinber1 wrote:
something something overlap sliders and hitcircles in timeline and break game mechanics something something auto fucks upYuudachi-kun wrote:
How do I make auto get a 100
Thank youuuusangu wrote:
*Edit
This is what I get for not doing the math... or reading the past posts properly. With 15000 notes the average accuracy was 99.994, but with 20,000 notes and a single 50, the acc would be 99.9959. So I recreated my test with 20,000 notes instead.
I guess, question answered?
Result of the 20,000 note test
Nooo.Full Tablet wrote:
Because of single precision floating point rounding errors, a single 100 with 5592405 300s should still give you an SS.
Looking at the game code, it is defined by the ratio of 300s and total amount of hits, which is calculated with single precision numbers (if the ratio is equal to 1., then it is an SS)Endaris wrote:
Nooo.Full Tablet wrote:
Because of single precision floating point rounding errors, a single 100 with 5592405 300s should still give you an SS.
100% yes but SS no as SS isn't defined per accuracy but per amount of 100/50/miss.
How large is a file with 16,777,216 objectsFull Tablet wrote:
Because of single precision floating point rounding errors, a single non-300 with 16,777,215 300s should still give you an SS.
If you carefully examine the game code you'll see that it's defined as (to paraphrase slightly)Full Tablet wrote:
Looking at the game code, it is defined by the ratio of 300s and total amount of hits, which is calculated with single precision numbers (if the ratio is equal to 1., then it is an SS)
float Accuracy =where CountX and TotalHits are 32-bit signed integers.
(float)(Count50 * 50 + Count100 * 100 + Count300 * 300) / (TotalHits * 300);
(float)Count300 / TotalHits == 1and single precision floating point rounds to a multiple of 2 starting from 16777217.
https://github.com/ppy/osuEndaris wrote:
How do you have access to the osu! source code though?
Then why isn't osu! using double precision?Full Tablet wrote:
Because of single precision floating point rounding errors, a single non-300 with 16,777,215 300s should still give you an SS.
How big is a file with 16,777,216 objectsThe Gambler wrote:
Then why isn't osu! using double precision?Full Tablet wrote:
Because of single precision floating point rounding errors, a single non-300 with 16,777,215 300s should still give you an SS.
How big is a player's ego in getting an SS?Yuudachi-kun wrote:
How big is a file with 16,777,216 objects
that's likeYuudachi-kun wrote:
How big is a file with 16,777,216 objects