osu-lazer/osu.Game/Screens/Edit/Components/Timelines/Summary/Parts/IControlPointVisualisationRedundant.cs

// Copyright (c) ppy Pty Ltd <contact@ppy.sh>. Licensed under the MIT Licence.
// See the LICENCE file in the repository root for full licence text.

using osu.Game.Beatmaps.ControlPoints;

namespace osu.Game.Screens.Edit.Components.Timelines.Summary.Parts
{
    public interface IControlPointVisualisationRedundant
    {
        bool IsRedundant(ControlPoint other);
    }
}
Reduce number of redundant control points displayed on summary timeline As pointed out in https://github.com/ppy/osu/discussions/16435, beatmaps with too many control points (usually added via external automation apps) could cause the lazer editor to grind to a halt. The overheads here are mostly from the GL side. An eventual goal would be to render this in a smarter way, rather than using thousands of drawables. Until that, this optimisation should help reduce the overhead by omitting control points in close proximity that are redundant for display purposes. I've tried to contain this in the display logic directly, with the goal that it can be ripped out as fast as it was added. Certainly required more changes than I hoped for, but I don't think it's too ugly. 2022-01-14 15:29:26 +08:00			`// Copyright (c) ppy Pty Ltd <contact@ppy.sh>. Licensed under the MIT Licence.`
			`// See the LICENCE file in the repository root for full licence text.`

			`using osu.Game.Beatmaps.ControlPoints;`

			`namespace osu.Game.Screens.Edit.Components.Timelines.Summary.Parts`
			`{`
			`public interface IControlPointVisualisationRedundant`
			`{`
			`bool IsRedundant(ControlPoint other);`
			`}`
			`}`