Troubleshooting the game crash issue
Hello everyone, we've recently received several reports stating that the game crashes on the first stage, "Merry-go-round". We checked the game data and confirmed that this is a locale-related issue. Sorry for the inconvenience.
To fix this problem, please refer to the following instructions. And please note that the information in this announcement is a temporary measure. We're working to resolve this issue completely, but we still need more time. So until the new build is ready, please use the method below.
That's all for now. Sorry again, and please let us know if the problem still remains. We'll come back with the patch that fixes this problem. Until then!
To fix this problem, please refer to the following instructions. And please note that the information in this announcement is a temporary measure. We're working to resolve this issue completely, but we still need more time. So until the new build is ready, please use the method below.
- Connect to https://pooi.moe/Locale-Emulator/ and download the "Locale Emulator" v2.4.0.0.
- Unzip the file and run "LEInstaller.exe". Press "Install for current user"(or you can "Install for all users". No matter what you choose).
- Locate to the Black Dream install directory.
- If you're using 64-bit Windows, the default directory is "C:\Program Files (x86)\Steam\steamapps\common\Black Dream".
- For 32-bit Windows, it's "C:\Program Files\Steam\steamapps\common\Black Dream".
- If you're using 64-bit Windows, the default directory is "C:\Program Files (x86)\Steam\steamapps\common\Black Dream".
- Right-click on "RPG_RT.exe". Select "Locale Emulator" on the pop-up menu, and again select "Run with application profile".
- On "Location" drop-down menu under "Location Settings" section, pick "Korean".
- Click "Save As...", then the game will start automatically, and will also leave the shortcut of "RPG_RT.exe" on your desktop. Use this shortcut on next launch to avoid repeating the same process above.
That's all for now. Sorry again, and please let us know if the problem still remains. We'll come back with the patch that fixes this problem. Until then!