You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the Issue
In the Billie environment, when an 'Right Sunbeams' (or left) sunbeams event is active, the rays are either equidistant or 'randomly' distributed, depending on the parity of the 'Ring zoom' events. The preview of the in-editor however, does not track this parity properly. The parity seems to change every time the editor plays a bit of the song, so repeating the same events could either show equidistant rays or random rays, depending on what parity the editor has in-memory. This is in contrast to the in-game behaviour, where parity is tracked across the entire song. (Well, it should be, but that's apparently very buggy)
Sorry for the vague description, the steps to reproduce are hopefully enough to show my point.
Provide Screenshots or Videos
Steps to Reproduce
See above screenshot: playing these 3 events over and over has two different alternating results in the preview. Note: this behaviour was seen in a V3 map, using the Billie environment.
Expected Behavior
I expected the parity to be tracked 'over the song' (i.e. counting all previous 'Ring zoom' events mod 2 or however it would be tracked), but instead the editor counts how many 'Ring zoom' events it has played (i.e. shown in preview).
Additional Context
This was in a V3 map, using the Billie environment.
The text was updated successfully, but these errors were encountered:
ChroMapper version
v0.8.568
Describe the Issue
In the Billie environment, when an 'Right Sunbeams' (or left) sunbeams event is active, the rays are either equidistant or 'randomly' distributed, depending on the parity of the 'Ring zoom' events. The preview of the in-editor however, does not track this parity properly. The parity seems to change every time the editor plays a bit of the song, so repeating the same events could either show equidistant rays or random rays, depending on what parity the editor has in-memory. This is in contrast to the in-game behaviour, where parity is tracked across the entire song. (Well, it should be, but that's apparently very buggy)
Sorry for the vague description, the steps to reproduce are hopefully enough to show my point.
Provide Screenshots or Videos
Steps to Reproduce
See above screenshot: playing these 3 events over and over has two different alternating results in the preview. Note: this behaviour was seen in a V3 map, using the Billie environment.
Expected Behavior
I expected the parity to be tracked 'over the song' (i.e. counting all previous 'Ring zoom' events mod 2 or however it would be tracked), but instead the editor counts how many 'Ring zoom' events it has played (i.e. shown in preview).
Additional Context
This was in a V3 map, using the Billie environment.
The text was updated successfully, but these errors were encountered: