We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I've stumbed upon a beatmap that used multi-segment linear sliders: 556757 fhana - RHAPSODY OF BLUE SKY (Sotarks) [Pentori's Hard]
556757 fhana - RHAPSODY OF BLUE SKY (Sotarks) [Pentori's Hard]
Here's an example: 123,73,53738,2,0,L|126:43|129:13,1,47.9499985366822,8|8,0:0|0:0,0:0:0:0:
123,73,53738,2,0,L|126:43|129:13,1,47.9499985366822,8|8,0:0|0:0,0:0:0:0:
Sadly, the current implementation of the beatmap parser, and the geometry module, assume that linear segments were… linear, not polylinear. Crap.
Maybe the simplest solution is to drop linear sliders and only use Bézier paths, as the former is only a specialization of the latter, technically.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I've stumbed upon a beatmap that used multi-segment linear sliders:
556757 fhana - RHAPSODY OF BLUE SKY (Sotarks) [Pentori's Hard]
Here's an example:
123,73,53738,2,0,L|126:43|129:13,1,47.9499985366822,8|8,0:0|0:0,0:0:0:0:
Sadly, the current implementation of the beatmap parser, and the geometry module, assume that linear segments were… linear, not polylinear. Crap.
Maybe the simplest solution is to drop linear sliders and only use Bézier paths, as the former is only a specialization of the latter, technically.
The text was updated successfully, but these errors were encountered: