Skip to content

Conversation

@secretbnuuy
Copy link

@secretbnuuy secretbnuuy commented Sep 15, 2025

Beatmap/Circle_size says circle radius equals 54.4 - 4.48 * CS osu pixels. at CS=5, that would equal 32, but the correct value (in both stable and lazer) is actually 32.01312. both clients also display the (rounded) correct value when hovering over difficulty numbers.

the correct formula is: (54.4 - 4.48 * CS) * 1.00041. (this isn't a rounding error (at least not anymore), it's hardcoded in. a comment in lazer's source code explains why)

alternatively, * 1.00041 could be said in a footnote.

reason for change:

  • the current page says "Circle size is derived through the following formula", and the following formula is actually an approximation, which is misleading.
  • this info can matter if intentionally causing an edge case. example: barely-overlapping streams that require keeping the cursor in the middle pixel(s), where whether a (discrete) screen-pixel counts as within a circle's hitbox can (rarely?) depend on this difference, or you need to know the formula to get your desired radius.

Self-check

@secretbnuuy secretbnuuy changed the title Use precise formula in Beatmap/Circle_size Use correct formula in Beatmap/Circle_size Sep 15, 2025
@github-actions
Copy link
Contributor

Thank you for contributing to the osu! wiki.

Please take note of the following:

  • Make sure you've read this self-check checklist.

  • Translations that have not been reviewed by a native speaker will be merged after a minimum of 1 week. If there are no reviewers for your language, please mention it explicitly.

  • Refrain from spamming the Update branch button. A maintainer will do this before merging anyway.

  • Apply review suggestions in batches from the Files changed tab like this:

    Demo GIF

See the contribution guide for more information.

All changes are run through continuous integration checks, which provide automatic detection of common errors. If you need help with decrypting CI check error messages, or with any other issues, ask in the #osu-wiki channel on the osu! Discord server.

@cl8n
Copy link
Member

cl8n commented Sep 15, 2025

it should definitely be explained in the article. I don't remember why we left it in a comment like that (probably just didn't get around to writing about it...)

Copy link
Contributor

@MChecaH MChecaH left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did some research to ensure the formula was correct. According to CalculateScaleFromCircleSize which scales objects according to a map's CS. An inconsequential amount, but plays into the formula.

@MChecaH MChecaH self-assigned this Oct 23, 2025
In [osu!](/wiki/Game_mode/osu!), circle size changes the size of [hit circles](/wiki/Gameplay/Hit_object/Hit_circle) and [sliders](/wiki/Gameplay/Hit_object/Slider), with higher values creating smaller hit objects. [Spinners](/wiki/Gameplay/Hit_object/Spinner) are unaffected by circle size. Circle size is derived through the following formula:

`r = 54.4 - 4.48 * CS`<!-- multiplied by 1.00041 in the end to account for some bug in old replays -->
`r = (54.4 - 4.48 * CS) * 1.00041`<!-- multiplied by 1.00041 in the end to account for some bug in old replays -->
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Before merging though, I think it'd be worth explaining where this ratio comes from in plain text rather than a hidden comment. Believe the ratio should be explained as to not let users wondering "what is this for". Especially when we're already commenting all the other variables in the formula.

@peppy
Copy link
Member

peppy commented Oct 28, 2025

I agree that this should not be a hidden comment. Please add the explanation to the actual wiki pages.

Copy link
Member

@peppy peppy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As commented

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants