-
Notifications
You must be signed in to change notification settings - Fork 92
New issue
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
"Failed to generate hash: a file could not be accessed." Not fixed by Admin rights #45
Comments
Same problem here after updating to latest beta. Stable version doesn't show these messages but finds 0 songs. |
2.5.2 final. Same issue, application not useable at all. Back to ModAssistant for now... |
A patch for this is coming VERY soon. Please be patient as we try to fix this. |
WOW! That was fast. Thx ^^ |
Fixed in 57c650d. Available now in 2.5.3-beta. Will be pushed to stable in a few days. Thanks for waiting. :) |
Still happening in 2.5.4 beta, so still an active issue. Also, seems weird that a higher version beta (2.5.4) would give an update notification and install a lower version stable (2.5.2) over itself. It's just asking for configuration problems. |
This shouldn't be possible, as this error message was revised. What exactly is happening? |
I looked back through the code and found a small bug that may have a similar issue for maps with more than one set. Please try 2.5.5-beta and let me know if you have any further issues. |
I fixed it by manually deleting the The previous stable release also choked on my library at every launch, but the single error was dismissable. I think it just got stuck on the Scanning for songs overlap. Not sure what the log file encoding is, so I just did a quick and dirty conversion to UTF-8 and deleted every other character to see if I could spot anything. Some of this probably the conversion. It's possible that selecting to not delete old versions of maps is part of the problem.
Other oddities: Custom levels path weirdness...
Not sure if it helps, but I downloaded a song (no problems) and pulled the log file. Here's the top section of the log: And the bottom... Hope that helps. |
There isn't really any log files for BeatDrop atm. What you are looking at is actually what the persist library uses to rehydrate the state of the app when it's closed then relaunched. After updating and resetting the app, is the problem solved? |
Yup, 2.5.5 seems to work fine without deleting the cache and shows no errors after rescanning tracks. Thanks! |
This issue is still happening for me on It makes the app effectively unusable, there seem to be hundreds of messages (one for each song at this point?): It's also worth noting that the update dialog does not understand beta versions, and offers to "update" to an older mainline version. Deleting the entire |
New Steam version of Beat Saber on a Steam Library on drive F. Songs converted to new format by SongCore Addin. Songs work ingame. I tried a complete reset of appdata folders and added the Beat Saber path again. Result:
Only log I found was in C:\Users\USERNAME\AppData\Roaming\beatdrop\Local Storage\leveldb
https://hastebin.com/xafesebefu.cpp
The text was updated successfully, but these errors were encountered: