While using CompileSimai to convert a simai chart to ma2, if for example, a slide's "tap" and "slide" action lies in different BPMs, the slide duration won't be calculated correctly, resulting in dramatically lower or higher slide durations.
The slide 6-1[16:1] is exactly one beat from the first tick where BPM is changed to 12.4375, at which the "slide" action is performed. Hence, the slide duration need to be divided by 16 (=199/12.4375) to accomodate this change.
While using
CompileSimai
to convert a simai chart to ma2, if for example, a slide's "tap" and "slide" action lies in different BPMs, the slide duration won't be calculated correctly, resulting in dramatically lower or higher slide durations.Example
Given this simai expression:
Expected output
The slide
6-1[16:1]
is exactly one beat from the first tick where BPM is changed to 12.4375, at which the "slide" action is performed. Hence, the slide duration need to be divided by 16 (=199/12.4375) to accomodate this change.Below is an example of how this would work:
Actual output
The slide duration is not divided to accomodate the BPM changes. Below is the actual result that the program produce.
As such, the slide duration is increased by 16 times when rendered in-game, which is an incorrect output.