Update Ranking Criteria
#7433
Update Ranking Criteria
#7433
Conversation
| - **Maximum width:** 2560px[^maximum-dimensions] | ||
| - **Maximum height:** 1440px[^maximum-dimensions] |
There was a problem hiding this comment.
These dimensions are larger than I recall them being, kinda scary in terms of the technical requirements but I guess it's what has been in place. Also I don't know who made the storyboard rule about 17m pixels but that's pretty high too. Dangerously.
There was a problem hiding this comment.
bg image context: pr, thread 1 (mostly about resolution), thread 2 (mostly about file size)
people use high-fidelity monitors these days so i can definitely understand this one. i'm not sure why a static 1440p image would cause technical concern
apparently @smoogipoo suggested it, with 4096x4096 being a little under 17m
There was a problem hiding this comment.
I have no recollection of suggesting this, fwiw. So you can discard anything I suggested and re-evaluate as if I didn't.
There was a problem hiding this comment.
some of the forum threads mention wanting to get my opinion but either i am very forgetful (not usually the case) or that never happened 😅
people use high-fidelity monitors these days so i can definitely understand this one. i'm not sure why a static 1440p image would cause technical concern
become a developer and you will understand multiple causes for concern.
There was a problem hiding this comment.
concerns aside, there are ranked storyboards with images above e.g. 10m pixels fwiw:
- https://osu.ppy.sh/beatmapsets/935708 (4000 x 4000 = 16000000)
- https://osu.ppy.sh/beatmapsets/1134425 (4096 x 2731 = 11186176)
- https://osu.ppy.sh/beatmapsets/1188324 (4500 x 2531 = 11389500)
- https://osu.ppy.sh/beatmapsets/1246880 (2804 x 4096 = 11485184)
there aren't many (probably any) cases where large images are necessary though, because the images can just be split into multiple sprites. sakuraburst - 「skyshifter vip」 for example uses three 1920x1080 px images to create a vertical panorama
There was a problem hiding this comment.
Multiple smaller images is definitely the preference, to the point I'd consider changing this criterial to reduce the limit to 12m or lower...
| - **Maximum width:** 2560px[^maximum-dimensions] | ||
| - **Maximum height:** 1440px[^maximum-dimensions] |
There was a problem hiding this comment.
bg image context: pr, thread 1 (mostly about resolution), thread 2 (mostly about file size)
people use high-fidelity monitors these days so i can definitely understand this one. i'm not sure why a static 1440p image would cause technical concern
apparently @smoogipoo suggested it, with 4096x4096 being a little under 17m
Co-authored-by: Dean Herbert <pe@ppy.sh>
wiki/Ranking_Criteria/en.md
Outdated
| @@ -30,7 +30,8 @@ Important to understand before using: | |||
| ### Rules | |||
|
|
|||
| - **No two hit objects can be placed on the same tick.** This includes hit circles and the durations of sliders and spinners. osu!mania difficulties are exempt from this. | |||
| - **No two key presses can be less than 20 milliseconds apart.** osu!mania and osu!catch difficulties are exempt from this. | |||
| - **There must be at least 10 milliseconds between a hit circle and the next object.** osu!mania and osu!catch difficulties are exempt from this. | |||
There was a problem hiding this comment.
Hmm, I didn't realise this was to be applied to osu! ruleset only..
To be honest, this can probably be removed and covered by existing timing rules (that hitobjects need to generally be snapped) at this point. Just for simplicity.
There was a problem hiding this comment.
not sure simplifying would work too well. the map with circles 13ms apart doesn't snap them to supported timeline ticks (1/24), so it'd be unrankable by the simplification, or the logic that permits 1/24 would also permit circles <10ms apart
There was a problem hiding this comment.
I'm fine if that's the case, but would defer to others for further opinions.
applying a handful of mostly minor changes from the rc subforum. i'm planning to use footnotes to make the rest of the article easier to read once this is merged
changes: