I was instantly punished by this new restriction. SO MANY maps have issues on offset and I used to chart all of these changes so I could change offset during gameplay for the really hardcore accuracy scores
There is a big problem then.lolcubes wrote:
There are way too many wrongly timed maps with wrong bpms.
Exactly this.kriers wrote:
I was instantly punished by this new restriction. SO MANY maps have issues on offset and I used to chart all of these changes so I could change offset during gameplay for the really hardcore accuracy scores
Let me just try and put things clear as to why I feel very unfairly treated right now:peppy wrote:
Please report incorrectly timed maps and we will fix them. This has always been the case.
I think you misunderstand my point. We often do several changes during one map where offset fleets back and forth. We want the ability to adjust to this again.peppy wrote:
Please restart the map and change at the beginning.
http://osu.ppy.sh/s/34083peppy wrote:
Please report incorrectly timed maps and we will fix them. This has always been the case.
We can't fix bad BPMs though.peppy wrote:
Please report in the map thread of to a BAT. Rather than each player fixing this, they should be fixed in the beatmaps.
We can still adjust by adding local offset. Or that was the case before.lolcubes wrote:
We can't fix bad BPMs though.
It cannot be both?peppy wrote:
Please report in the map thread of to a BAT. Rather than each player fixing this, they should be fixed in the beatmaps.
ykcarrot wrote:
I don't care about miss timed beatmaps. Just I can't adjust offset during testing in the middle of the map, it's really annoying.
Restore it please peppy
Not every BAT can force update beatmaps.TheVileOne wrote:
If peppy says BATs can fix bad BPMs, then you have permission to fix bad BPMs. It would take a map update, but I'm not sure if updating would revert it to the latest version. That was an issue awhile ago.
I believe there're at least 20% out of all ranked maps that are off by >±5ms. I can help to make a tool to automatically detect the timing of most single-BPM songs with reasonable accuracy and compare against the beatmap (and also a list of songs it can't time) if you wish running it on all ranked beatmaps should take less than one day.peppy wrote:
Please restart the map and change at the beginning, and also report the issues in the map thread or to a BAT directly. If there are many ranked maps like this, we need to get started fixing 'em. Local offsets are not the solution.
Starting from xxxxxx ms, offset timing by +/- yy ms and skew timing by +/- zzz ppmlolcubes wrote:
Fixing offsets is easy and if the offset is bad we usually fix it already (if reported).
But yeah as I stated in my previous post, there are multibpm maps with different offsets and maps with wrong BPM which I guess need some waiting now for peppy to implement the possibility to fix BPMs as well.
I wonder how would this look like, cause if it's something like "online offset at" such things could effectively fix a lot of problems without a need to unrank & wipe scores.
Timing is objective but perception of it is subjective. The point is not that a person should be able to use their subjective perceived timing because they do not agree with an objectively correct timing, it is that the "objectively correct" timing may not be objectively correct because it is merely what another person subjectively perceived to be correct, hence why discrepancies exist at all.merchat7 wrote:
@plaird
Timing is an objective thing. It's either right or wrong. I guess it's fine if people prefer to adjust it themselves through, but this is not up for me to decide.
Replays contain an md5 hash of the .osu file they were played on. If the .osu is modified in any way, then the replay and score won't show up on the modified map.TheVileOne wrote:
If you save a local replay and then change the where the objects are in the song, will that not affect how the objects appear in the replay?
Nah.. Are you sure about that BPM is wrong? I don't know how accurate you are, but I don't see any problem on those.statementreply wrote:
20 most recently ranked beatmaps:
http://osu.ppy.sh/s/73769 either bpm off or needs multiple sections
http://osu.ppy.sh/s/63233 bpm a bit fast
http://osu.ppy.sh/s/59830 bpm a bit slow, offset too late on main timing section
ykcarrot wrote:
Nah.. Are you sure about that BPM is wrong? I don't know how accurate you are, but I don't see any problem on those.
This one is off, but I'm not quite sure about the nature of off-timingstatementreply wrote:
http://osu.ppy.sh/s/73769 either bpm off or needs multiple sections
~131.996 i.e. original bpm gradually getting ~6ms early throughout the songstatementreply wrote:
http://osu.ppy.sh/s/63233 bpm a bit fast
~120.003 i.e. original bpm gradually getting ~6ms late throughout the songstatementreply wrote:
http://osu.ppy.sh/s/59830 bpm a bit slow, offset too late on main timing section
http://osu.ppy.sh/s/10435 wrong bpm and multiple offsets, LOTS of ranked playslolcubes wrote:
Small offset variations under 10ms are rankable.
As I said before, maps with bad offsets don't need to be reported here. Only if they have bad multi BPMs or just wrong BPMs. We can fix offsets already and the local offset already fixes the issue if the player wants to use it.
Yes allow changes during breaks will be helpful. Is there any chance to extend this "grace period" to say the first 20-30 seconds? Assuming the non-skipable intro isn't too long, 30s should give ample time for those who genuinely need to "tune" the offset.peppy wrote:
I initially removed this as some people were using it in dodgy ways (while macroing to make accuracy look more random), but I will allow changes during breaks in the next build.