No edit summary |
Tag: 2017 source edit |
||
| Line 13: | Line 13: | ||
If that hasn't worked, perhaps you've got a copy of Resonite running that you can't see. You can kill this stuck process using your task manager. | If that hasn't worked, perhaps you've got a copy of Resonite running that you can't see. You can kill this stuck process using your task manager. | ||
* For Windows [https://techcult.com/how-to-kill-a-process/ this guide will help] | |||
== 3. Reboot == | == 3. Reboot == | ||
| Line 25: | Line 25: | ||
== Other Things to Consider == | == Other Things to Consider == | ||
* If this is a multi-user machine, another user might be running Resonite. | |||
[[Category:Troubleshooting]] | |||
Latest revision as of 13:01, 10 September 2025
When you start-up Resonite, you might see an error that says "A duplicate copy of FrooxEngine is running with this configuration.".
This page's goal is to help you fix that error.
1. Easiest Fix
In quite a lot of cases, this happens because you might be accidentally launching multiple copies of Resonite. This can happen if you spam click any of the options you use to launch Resonite such as a shortcut, exe file or even Steam.
Make sure you close all copies of Resonite and then try launching it again.
2. Stuck Process
If that hasn't worked, perhaps you've got a copy of Resonite running that you can't see. You can kill this stuck process using your task manager.
- For Windows this guide will help
3. Reboot
If that doesn't work rebooting your system will kill any outstanding Resonite processes.
4. Multiple Copies
This can also occur when running multiple copies of Resonite for testing. In these cases, follow the Relocate_Resonite_Folders for one test copy.
Other Things to Consider
- If this is a multi-user machine, another user might be running Resonite.