y’know, i should’ve made this an actual bug report a while ago, instead of just offhandedly mentioning it in my hsb topic
steps to reproduce the problem every time:
use an hsb color with the h value set between, but not equal to, 359 and 360
be amazed as it outputs as black regardless of s or b
i expected this to happen: output as a normal color with s and b rounded to the nearest integer like they always are, and h outputting a color that is extremely similar to red but technically isn’t
but instead this happened:b l a c c
screenshots/video: i found out when the backgrounds to two of my songs, heat and final, passed through this range, and printed out a thin black ring as they did
I’d say “show us your code,” but since you are an undefined user, it’ll be much harder to do so, especially since you can’t save your projects no matter what :((
Are you sure the brightness was high and not (0)?
Since you tested on the web explorer, the HS version is Not Applicable. The player version in this case is Player 2.2.2
ok i ran both songs in the project builder but changed the player version to 2.0.0 before running & no black ring
turns out that the player version they were both posted in was 1.5.14 so this must have been fixed in the past
weird 'cause i sbyp’ed and found nothing
someone else must have noticed it– i dunno
anyway i’m solving this topic so it goes away
comes back from ae builder
also- i guess h was 361 [exactly] when it printed the black ring
i found out after messing around with final’s json in 1.5.14 for so long it made my brain hurt
also i changed it to a simple “move forward, width 100” trail hsb[361, 60, 100] and no black
oh well
i guess the world will knever no about the mysterious black ring