Ever since v3 I have been noticing inconsistancies between the game's judgements and the error meter. (Async on) This was especially obvious when trying to play with "Pure Perfect Only" set on Limit Judgements setting. Whenever I died to an EPerfect or LPerfect, the game would say [No "Judgement" allowed] and that judgement would be reflected in JipperResourcePack. However, the error meter would show a judgement that was the opposite almost 90% of the time. For example, if the text [No "EPerfect" allowed] showed up at death, JipperResource Pack would show 0 0 1 100 0 0 0 but the error meter would have a light yellow tick on the LPerfect side. This error also occurs with all other judgements as well, with its equal opposite being shown on the error bar.
#v3 Error Meter? (lmk if I should ask in diff channel or if this is known issue)
gusty condor
Note: There are also moments where error meter picks up on EPerfect/LPerfect judgements even when JRP or the game's limit judge system does not, even when timingscale is 100%.
Additional Note: I use Linux (Fedora 44 KDE) and additionally have not felt any other difference in judgement from async on v3, if anything, the timing feels much more stricter. Async on this version on linux also makes the error bar look as if I wasnt using Async at all from v2.