It appears there may be slight issue with the storyboard? (map downloaded 2017-04-21)
NOTE: Using wine 2.0 on Debian testing, Not sure if this an actual bug or just a wine caused issue.
I don't actually know anything about storyboarding so this could all be horribly wrong.Dragging the map into the game loads fine but on attempting to play any of the diffs an error dialog pops up with:
Error in Storyboarding script Drop - Granat (diraimur).osb on line 18: MY,17,0,1989,NaN,NaN Input String was not int a correct format.
osu! locks up and has to be killed. After relaunching the map is deleted.
The NaN values sound wrong.
according to
https://osu.ppy.sh/wiki/Storyboard_Scripting_Commands#Move_.28M.29_Command it seems "NaN" is not a valid value for the Move (and all other) storyboard scripting commands.
Extracting the .osb and running
$rg NaN,NaN Drop\ -\ Granat\ \(diraimur\).osb
gives:
rg out, 16 lines18: MY,17,0,1989,NaN,NaN
19: MY,17,1989,3978,NaN,NaN
202: MY,17,0,1989,NaN,NaN
203: MY,17,1989,3978,NaN,NaN
386: MY,17,0,1989,NaN,NaN
387: MY,17,1989,3978,NaN,NaN
570: MY,17,0,1989,NaN,NaN
571: MY,17,1989,3978,NaN,NaN
754: MY,17,0,1989,NaN,NaN
755: MY,17,1989,3978,NaN,NaN
938: MY,17,0,1989,NaN,NaN
939: MY,17,1989,3978,NaN,NaN
1122: MY,17,0,1989,NaN,NaN
1123: MY,17,1989,3978,NaN,NaN
1306: MY,17,0,1989,NaN,NaN
1307: MY,17,1989,3978,NaN,NaN
which seems like something may have gone wrong with the storyboard creation/export somewhere?
After running
$sed -i 's/NaN,NaN/240/g' Drop\ -\ Granat\ \(diraimur\).osb
(which replaces all 16 occurrences of "NaN,NaN" with "240"),
updating the .osz archive with the modified ,osb and then loading the map into osu! again, all of the diffs seem to work perfectly fine (the storyboard also seems to be fine though some elements could possibly be misplaced as I do not know how to was supposed to look in the first place, nor did I spend much time examining it).
as it seems "nobody" else is having this issue am assuming that wine does not handle the NaN values where as Windows just defaults them to some other value possibly? and this causes nobody to notice, or maybe this is just a wine caused problem after all.