StreamCompanion VS osu-stable-issues

I don't know how to fix this, but gosumemory is out of date as far as pp calculations go(that map is 290 for ss), but steamcompanion is up to date, so maybe try using that to see if it solves both problems.

streamcompanion or gosumemory for pp counter (personally recommend streamcompanion)

My recommendation is to just use StreamCompanion.

one of the overlays from streamcompanion https://github.com/Piotrekol/StreamCompanion

StreamCompanion

These are issues that support claims justify my restrictions to be kept, despite the fact that Griffin has admitted to those claims being false11. It seems strange to hold a player accountable for their past restriction if the person reporting retracts their statement. Support has claimed that external programs (such as Stream Companion5) have the ability to pause the game for you and I would be more than glad to email the programs used. The same issues persist with my current restriction: Why doesn’t Griffin’s outspins get removed while Griffin can report mine and I get restricted when we are doing the same thing?

you can use streamcompanion https://github.com/Piotrekol/StreamCompanion/releases/tag/v221108.21, 1. download and install the setup.exe and the text overlay.exe, 2. open the program then click https://i.imgur.com/HbLsBW8.png, 3. go to output pattern then click show on osu https://i.imgur.com/e7eKsWR.png

its widget on osu streamcompanion you can custom it, for example this is my custom widget https://postimg.cc/PPFBCYh7

You could instead try gosumemory or StreamCompanion.

Encourage you to report the issue here: https://github.com/ppy/osu-stable-issues/issues

yeah, with such a bleeding edge gpu downgrading drivers is probably not much of an option. you could try and make an issue at osu-stable-issues, though make sure you try these tips (but I suspect you already have). It might really be possible that the only thing that can be done about this is waiting for vulkan/dx12 support that's gonna be added to lazer soon-ish.

Stable is not getting any features added and minor bugs are mostly ignored but critical issues like those that affect gameplay and crashes are still being fixed. You can see peppy still actively responding to the issues posted.

We understand that peppy is a very busy person, but he should be able to explain why he wants to keep this change in. Griffin wrote his concerns about the pause delay change on GitHub, with peppy responding that “the overall reception was positive”. Yet, over 30 players commented on their concerns with this change (over half of them made a GitHub account JUST to comment on the change).

Something I don't understand is why past bug fixes do not seem to uphold the same ideology. The previous bug fix for spinners is the source of the current bug you're addressing, which is exactly the scenario you mentioned (new loophole). The sliderbug fix took several attempts to fix, and still ended up breaking replays; see osu-stable-issues #554, where in the comments, you said "at the time we decided it wasn't so bad to break replays". And in lazer, spinners already work differently, so maintaining "forward compatibility" shouldn't be much of a concern. To me, it feels a bit silly to worry about "breaking replays" when these replays will be recalculated in lazer anyways. Especially for scoring-related things like spinner/slidertick points, having past replays show slightly more/less points is a non-issue for the majority of players. So I agree with your former opinion, that breaking a few replays to fix a bug doesn't seem like a bad tradeoff, especially when this tradeoff vanishes when migrating to lazer.

Report it here https://github.com/ppy/osu-stable-issues

Issues can be adressed on the GitHub for osu! stable/lazer or via. email to ppy. https://github.com/ppy/osu-stable-issues/issues