-
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
[BUGFIX/ENHANCEMENT] Sustain trail alpha fix #2893
[BUGFIX/ENHANCEMENT] Sustain trail alpha fix #2893
Conversation
Why do it in the update? Also why remove the existing alpha = 1.0? The code suggests to me that it was meant to become fully opaque when you hit the hold, similar to other VSRGs which make held holds lighter (ITG immediately springs to mind) Maybe I'm wrong? Personally I'd just make it alpha in the create tho, not the update |
I tried editing the existing |
in
Maybe @FunkinCrew considers using the old alpha value, which could be why @EliteMasterEric didn't reject this. |
Oh, I never saw that LOL, woops... |
Just tested it out, it only applies the alpha when the note is being pressed, even when the alpha is changed in 2024-06-24.19-58-00.mp4 |
then you will have to look for all lines of code that change |
2024-06-25.18-31-29.mp4if you change it to the desired 0.6 alpha, then it becomes just like in the good old days |
Oh wow, that is a large oversight on my part. I thought everything would've been handled within |
For the record, I messaged Dave about it but my recollection is that opaque holds were an intentional change. I will definitely merge the other PR that fixes the issue with mods changing opacity regardless. |
Yeah the opacity change was intentional. |
Sustain trail alpha would always default to 1 regardless of what alpha value was defined. Simply moving the alpha value into
update()
fixes this issue. This is similar to pre-rewrite sustain trails which were also semi-transparent.