Suggested offset

[IVII1]

Hello, I use suggested offset often and it helps but sometimes, due to being an average of all the hits in the previous play (afaik) it is sometimes horribly off. Do you think that an estimated acc improvement should somehow be displayed alongside the suggested offset to help gauge if its actually worth using (basically, if the suggested offset had been applied in the previous play, what would the acc have been) This can give the player more info on whether they should try playing with the suggested offset.

[SchiavoAnto]

average of all the hits in the previous play

The suggested offset was changed a while back (#32601) to use the median of the hits, not the average, so it already should be more precise than before.

[sineplusx]

The quality of the offset suggestion depends on how accurate you can time your hits to the timing of the song. If you already feel that most of your hits were not on time with the music, applying the recommended offset will obviously give an inaccurate result.
The idea of a predicted accuracy improvement "if offset was x" is not useful, since the system cannot account for player error. It would always display an improvement, even if the offset is "objectively" wrong.

Improving the accuracy of the recommended offset can be done by playing the map for longer before restarting (more data points). Getting an offset recommendation for a difficult map can be achieved by playing a simpler difficulty of the same mapset, or, for example, using the "Target Practice" mod with the metronome off.

[IVII1]

That's a good point, but i don't think all inaccuracies are caused by player error. Sometimes causes can be system latency or poorly timed old maps. And at the end of the day if the player doesn't feel like they're getting value out of it they could reset the offset. I've had stretches where the suggested offset would stay the same throughout multiple runs, and after applying it i would do much better.

On that note, i think another thing worth considering is if its maybe better to calculate offset based on all plays in the current session, not just the last play

[n0Oo0Oo0b]

On that note, i think another thing worth considering is if its maybe better to calculate offset based on all plays in the current session, not just the last play

This already exists, accessible in the global offset settings:

It sounds like you've been using the per-beatmap suggested offset which, as its name suggests, only applies to the current beatmap and is intended to account for mistimed beatmaps rather than system latency.

[shiumano]

There have been a few times I have wanted an “if perfect offset” indicator, but perhaps that should be calculated by external software as well as “if fc”. Would I make it?
Personally, I think it should determine if the recommended offset should be used or not based on the recommended offset discrepancy and the Unstable rate.