Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Current composition placement being cancelled by other HitObjects becoming alive in the editor #12630

Closed
LumpBloom7 opened this issue Apr 29, 2021 · 0 comments · Fixed by #12926
Assignees
Labels
area:editor priority:1 Very important. Feels bad without fix. Affects the majority of users.

Comments

@LumpBloom7
Copy link
Contributor

LumpBloom7 commented Apr 29, 2021

Describe the bug:
After beginning the placement of a HitObject that has a duration, it is possible for the placement to be cancelled by another DHO becoming alive.

This usually results in the placement simply disappearing without a trace, but on occasion a ghost timeline blueprint gets left behind that can't be interacted with in any meaningful manner.

Other objects becoming dead doesn't affect the current placement.

I noticed this while building the editor for sentakki, and was able to replicate in osu!standard. I think I managed to get the same problem in mania, but I can't seem to reproduce it.

Screenshots or videos showing encountered issue:
Note that the placement gets cancelled the same frame as a HitCircle gets retrieved from the pool.
https://www.youtube.com/watch?v=xyYbIJ5SHBI

osu!lazer version:
2021.424.0

Logs:
N/A

@LumpBloom7 LumpBloom7 changed the title Current composition placement being cancelled by other HitObjects becoming alive Current composition placement being cancelled by other HitObjects becoming alive in the editor Apr 30, 2021
@peppy peppy added area:editor priority:1 Very important. Feels bad without fix. Affects the majority of users. labels May 1, 2021
@peppy peppy self-assigned this May 24, 2021
peppy added a commit to peppy/osu that referenced this issue May 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:editor priority:1 Very important. Feels bad without fix. Affects the majority of users.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants