Open smoogipoo opened 1 year ago
Massive performance drop on ranked SV maps (ex. /b/1572577 and /b/2669198)
Note that this was linked to another issue claiming SVs as the culprit, however as far as I can tell this doesn't appear to be (at least, not always) SV-related.
The map that was brought up to me at COE was https://osu.ppy.sh/beatmapsets/1252675#mania/2603455, where I witnessed the editor entering some 3/4 of the way through the map. It looks like the editor's still keeping hitobjects alive when it shouldn't be - likely another edgecase with HitObjectLifetimeEntry.
While I can't repro the above map starting 3/4 of the way through, I can repro it all the same by just clicking on the timeline to that point in time:
https://github.com/ppy/osu/assets/1329837/8cabc697-9407-4966-9d9d-d78491ec12f6
(notice how the pools are reporting many drawable instances are being used)
Performance potentially related to https://github.com/ppy/osu/issues/24007
(I was told to comment here so apologies if this is the wrong place) Given how many SVs some maps use in mania, to have to switch from the compose tab to verify to place an sv and then switch back to make sure you're sure on what you're sving feels disconnected (this is mainly from someone who got used to the timing panel popout) So a suggestion would be to use the timing panel to add the ability to see current bpm/sv values and then allow addition of new ones at the current timestamp. Quick mockup shown below:
This might fall under "You can place a note during a slider on the same column. This should not be possible." but I'd like to point out that one method for creating long note maps is to first place down the notes as regular notes, and then switch to the long note tool to extend those notes into holds. Stable's editor allows this, as using the hold tool to drag out a short note will extend it into a long note. However, doing this in lazer will just result in the long note stacking on top of the short note.
In Stable, if you are using the long note tool but you just click instead of dragging out the long note, you can place a short note, you can use this to replace a long note with a short note easily by just clicking at the start.
In Stable, to change the length of a hold note, you can drag from the beginning while the hold tool is selected to replace the old hold with the new one.
Just a few stable behaviors to keep in mind when you work on the issues with stacking, as these are all very important to the workflow of creating a long note map in my opinion.
There was another issue I found, but I'm having a hard time telling if it occurs solely in the editor, or if having the notes be unmoving just highlights it. I'm using a legacy skin, and the hold notes appear to end before they are supposed to. I am specifically running this on a Macbook M2 Pro, which could be part of the problem. See below:
I'm using a legacy skin, and the hold notes appear to end before they are supposed to
You're using a hack of a skin with "percy" ends or whatever. Those routinely exploit broken stuff like 30,000px high sprites. You should be happy it continues to work at all.
Out of scope of this issue.
Here's some feedback that was provided to me over the course of COE (and a little afterwards) pertaining to the editor. Some of it (especially around the timing screen) are more general usability concerns.