Releases: KapiWilq/HitErrorMeter
v1.0
v0.9.10
Thanks for wanting to try out my overlay!
Changelog
- Rename some settings to be more 'murican
- Use the Unstable Rate value from tosu
- Don't add hit error ticks (and don't update the average moving arrow) when the hit error meter is invisible
- This might cause the overlay to be inaccurate for the first 9 ticks after hiding and then showing the hit error meter, e.g. in osu!catch
- New setting: "Hit error ticks appearance style"
- Adjust hit windows to be accurate AGAIN.
- Apparently, osu!(lazer) does the same trickery with EZ/HR as well. Interesting
- Code:
- Replace
maniaConvertruleset type with a combination ofmania&beatmap.isConvert - Adjust some comments
- Replace
v0.9.9
Thanks for wanting to try out my overlay!
Changelog
- Don't add new ticks if the hit error meter is not visible
- Note: if you decide to make the overlay show the hit error meter in the middle of the play, the moving average arrow will be "incorrect" for the first 9 ticks
- Slightly adjust hit windows calculation for osu!(stable) to be more accurate
- Make hit windows be affected by the rate in osu!(lazer)
- Code:
- Update comments
v0.9.8
Thanks for wanting to try out my overlay!
Changelog
- Update the overlay to support tosu v4
- Use the new
play.mods.ratefield (the overlay doesn't have to get the map speed by itself anymore) - Add proper support for osu!(lazer)
- Use the new
- Add support for osu!mania converts
- Fix the overlay not being accurate in osu!mania with EZ and HR
- Discovering this one was the worst. Normally EZ and HR apply multiplication (0.5 and 1.4 respectively) to the Overall Difficulty value (before rate change), however osu!mania in osu!(stable) applies a scale factor of 1.4 to hit windows instead (divide when using EZ, and multiply when using HR). E.g. in osu!(stable), without the ScoreV2 mod, 320's hit window is a constant 16ms, and if enable HR then it's ~11.5ms
- Increase the overlay resolution (width only)
‼ IMPORTANT PLEASE READ ‼
With this update, there are a few settings that are exclusive to osu!(stable). This is due to tosu not having reading the score meter and resolution settings implemented yet. The thing with these is: osu!(lazer) allows you to put a hit error meter anywhere, rotate it and stretch however you want. With this overlay, it's much harder (and even impossible if using in the in-game overlay) to achieve the same thing, therefore I think these two settings are gonna be osu!(stable)-exclusive probably forever.
v0.9.7
Thanks for wanting to try out my overlay!
Changelog
- Add a setting to automatically scale the overlay with resolution
- Scale the hit windows in the osu!catch ruleset
- Fix some hit windows' values not being rounded
- Code:
- Treat the osu!catch ruleset as an actual ruleset (previously it was simply fallbacking to make it look like osu!catch was supported in some capacity)
- Please do note that with this change there could some more errors (and potential breakages of the overlay). If this ever happens, please make a detailed issue about it!
- Treat the osu!catch ruleset as an actual ruleset (previously it was simply fallbacking to make it look like osu!catch was supported in some capacity)
v0.9.6
Thanks for wanting to try out my overlay!
Changelog
- Fix the Unstable Rate display resetting its value when changing its display style
- Rearrange some settings
- Allow for WAY more customizability of the Unstable Rate display (font size, font family (aka font name), font colo(u)r)
- Allow for customizing the moving average arrow's size
- Allow for customizing the hit error meter's main tick colo(u)r
- Rewrite some settings' titles and descriptions
- Add """category""" separators to settings
v0.9.5
v0.9.4
Thanks for wanting to try out my overlay!
Changelog
- Update the in-game score meter hider to use the map's background and player's background dim (you can disable the entire thing if you don't like it)
- Add support for arbitrary WebSocket ports (so you can set something else that's not
24050, e.g.http://127.0.0.1:20727) - Allow for the customization of the Unstable Rate display (options:
"Show nothing","Show only the value","Show both the prefix and the value") - Allow for the customization of the hit error ticks appearance and disappearance animations durations (max 5 seconds and 10 seconds respectively)