#Holds not parsed properly from .DWI
3 messages · Page 1 of 1 (latest)
3 messages · Page 1 of 1 (latest)
CPU:any
OS::Windows and Linux
Version:Alpha V from website as of yesterday
If a DWI file is loaded in the alpha, a hold like B!B is treated as if it were BB!B which desyncs everything after the hold. All holds are wrong. If it isn’t, it’s because there was already a SM or SSCf file there that had priority
Easiest way to test this is DWInsanity’s sandstorm, which comes as DWI only and starts with that exact hold which turns into a jack jump hold and desyncs the entire chart after.
I tagged it as regression because it works fine in SM5