The best way for me to fix this would be getting my hands on one of those FileSystemCache_Osu.json files. But it's good to know this issue exists and it's kind of likely that it will occur again (which is both a bad and a good thing, a good thing because when it happens again we can gather more information). That's fairly nasty, especially because the information isn't sufficient to write a fix, yet. Thanks for the screenshot - that does help a lot because it tells me that under certain circumstances (probably something with Unicode titles), the JSON file gets corrupted and then cannot be parsed anymore. I hope one of the above suggestions already fixes the issue for you but if not, I'll make sure you get your library up and running again in the next few days. If you have already played a lot, you should not delete that JSON file because we currently keep track of a few things in that file and if you delete it that information will be lost.Īlso, can you send the file output_log.txt (this one definitely is in Holodance_Data) to jashan at narayana minus games dot net (or simply take the address available at: )

That file is either in the main Holodance-folder or Holodance_Data. That will trigger a complete re-scan of your osu songs-folder. One thing you could try (if you haven't tried already) is renaming the osu file cache JSON file. What exactly do you mean by new and old installer? The workaround is to temporarily remove those beatmaps a proper fix will be in the next release. But I'll definitely be online tomorrow (it's exactly midnight and I'm just about to go to sleep).ĭid you add new songs before this happened? I did have reports of certain beatmaps crashing the file scanner which may cause what you are seeing.

Hi Jason, I'm sorry to hear about this! I'm just returning from a little meditation retreat and will be back in the office tomorrow or the day after.

Get osu lazer on pc