You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just ran into this bug today and it's unbearable because I can't figure out how to fix it at all. Let me explain...
When I opened Mapping Tools, I wanted to fetch any difficulty from osu! client so I can add hitsounds to one of them. But, every time I try fetching a difficulty, I get an error message. This also happens when you try to open current beatmap.
After reinstalling Mapping Tools, it didn't solve the issue. I did save my pattern gallery before I deleted Mapping Tools, and when I try to add an object to the gallery to go to the 'Pattern Files' the fast way, I get another error message saying 'Access denied'.
Screenshots/Recordings
Additional context
The text was updated successfully, but these errors were encountered:
This looks like an issue with Editor Reader. Something could be blocking access to reading the memory of osu! Maybe its an antivirus, firewall, or lacking permissions.
Until its fixed, i recommend disabling Editor Reader in the Preferences to prevent errors and not use "open current beatmap". Mapping Tools will at least be usable.
Prerequisites
Environment
OS version: Windows 11
Mapping Tools version: 1.12.17
Description
I just ran into this bug today and it's unbearable because I can't figure out how to fix it at all. Let me explain...
When I opened Mapping Tools, I wanted to fetch any difficulty from osu! client so I can add hitsounds to one of them. But, every time I try fetching a difficulty, I get an error message. This also happens when you try to open current beatmap.
After reinstalling Mapping Tools, it didn't solve the issue. I did save my pattern gallery before I deleted Mapping Tools, and when I try to add an object to the gallery to go to the 'Pattern Files' the fast way, I get another error message saying 'Access denied'.
Screenshots/Recordings
Additional context
The text was updated successfully, but these errors were encountered: