forum

"Beatmap import failed! Check logs for more information."

posted
Total Posts
7
Topic Starter
Link1024
Problem details: My beatmap I made will not download correctly and is corrupt. The beatmap is beatmapsets/2271749#osu/4839118


osu! version: lazer
Snapy
Upload all the files of the map to somewhere and send the link to it here.
spaceman_atlas
@Snapy: there is no need for that. The OP has put the link to the beatmapset. It does break on import.

@Link1024: The import is failing because the game isn't recognising the .osu file inside, its filename looks mangled (has four NUL bytes at the end). Can I ask how you uploaded the map? Do you have something weird set on your PC, like a custom language set or something that might have to do with file encoding?
Jason X
It seems there is non-alphanumeric unicode where it doesn't belong:

(My PC doesn't recognize the unicode I guess, therefore the questionmarks)
Import works fine when I remove the questionmarks using 7zip, so they seem to be the problem.

I suggest to check the file in the maps folder and also remove those questionmarks, or whatever letters you used there, then update it so it will work for import again.
Topic Starter
Link1024
There are no map files folder because I am on lazer. I exported the map from lazer editor, put it on stable, and uploaded it from stable. I uploaded another beatmap (beatmapsets/2271745#osu/4839113) just minutes before uploading the corrupted one.
Jason X

Link1024 wrote:

There are no map files folder because I am on lazer. I exported the map from lazer editor, put it on stable, and uploaded it from stable. I uploaded another beatmap (beatmapsets/2271745#osu/4839113) just minutes before uploading the corrupted one.
Unlike lazer, Stable does have folders, you can access the folder for this specific map from the editor via the "Open Song Folder" function.
Then you can fix the unicode problem and update the map.

Also, the other map you mention is not part of the issue.
It imports without any issue.
Topic Starter
Link1024
Thank you!
Please sign in to reply.

New reply