-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[BUG] (Charting State) Loading a song without difficulty/variation behaves unexpecfully or crashes #2468
Comments
nice catch! |
0.4.0 and still has not been fixed |
Does this still happen in v0.5.1? |
Yes, and can be replicated if you open a song without a Pico variation as well.
|
I can't reproduce this in 0.5.3/ the development build. |
This just in, this bug still exists on the 0.5.3 develop branch:
I was able to make it occur twice. One for a song without an Erect variation:
Another for a song without a Pico mix:
|
Using debugging with breakpoints, I believe I have found the problematic area in the code. The issue occurs in After the call to the This causes the variation to be added to the chart data too after the call to the Because the issue occurred after the call to the These values are fine until this line (line 124) executes: Conductor.instance.instrumentalOffset = state.currentInstrumentalOffset; After that line, the variation for the song you were previously on is added to the metadata of the new song you are trying to load: |
Still an issue in 0.6.x |
If you had loaded previously a song with another variation (like Erect) or difficulty and then try to load a dfifferent song unexpectedly changes song data or crashes.
(I think only crashes with song templates)
This could be easily fixed by resetting the variation and difficulty when loading a different song.
Video example: (using song template)
Recording.2024-05-12.014721.mp4
Video example: (loading existing chart)
Recording.2024-05-12.015142.mp4
The text was updated successfully, but these errors were encountered: