-
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 Report: Lag on Pico songs (Pico mix) #4299
Comments
I'm personally not able to reproduce this (at least to the severity in the video), |
Issue confirmed. bug-repro.online-video-cutter.com.mp4I think this is because the stage script spams the hair blow animation when the train is passing, but Nene doesn't have the animation, which for some reason causes lag (and may even flood Flixel's debug log window) Preventing the animation from being spammed seems to solve the issue, but it's not a proper fix since the spam is needed or else GF will just play the animation once then freeze until the bug-not-present.mp4 |
Interesting, I wonder if there is a way to not have it spammed only on pico songs? |
No idea how the code works, but I'd imagine you could check if a girlfriend has the hair blowing animations and then disable the animation if not |
Related to trying to play animations that a character doesn't have, a similar issue happens on Pico mixes for Week 2 songs: The script tries to play the scared animations for both BF and GF whenever a lightning strike happens, but Pico and Nene don't have these. I don't know if this causes as much lag considering that the animation is not spammed, but only played twice per lighting strike. Interestingly, the script for the normal stage,
It seems that this was forgotten in
|
Good find! |
Issue Checklist
Platform
Compiled from GitHub Source Code
Version
Develop branch
Description (include any images, videos, errors, or crash logs)
The more you restart, the worse it seems to get:
2025-03-12.20-24-25.mp4
Steps to Reproduce
The text was updated successfully, but these errors were encountered: