i don’t know why this happened but after the update to 4.11.1 through the epic games launcher i cannot even start the unrealengine 4.11.1 to create new projects. The engine startsup and loads up to 75%, then appears the error message and the engine terminates.
And i am not even able to open existing projects.
At start i get asked this:
And if i click on “Ja” (Yes), the same as above happens. Loading up to 71~% and then terminates with the error above.
I used the engine installation verify function inside the epic games launcher twice and nothing got fixed.
We’ve had a couple other users report this issue with 4.11 but not specifically with 4.11.1. If you still have the copy of your project from a previous version, such as 4.10.4, could you try migrating the content directly to a new project created in 4.11.1 using the in-editor content migration tools instead of doing a conversion? This fixed the problem for other users, you can find that other post here: Why is my game failing to launch due to missing 'LeapMotionController'? - Platform & Builds - Epic Developer Community Forums
Although that may fix the problem, we would like to fix the problem at its root. Unfortunately, we haven’t had much success in the first step of process which is getting a reproduction case. Would it be possible to get a copy of your project either in 4.10.4 or 4.11 where the issue occurs? This should help us in our effort to fix the conversion issue.
I am having the exact same problem, except it is with a fresh install of the engine on windows, im not using the leap motion controller, just starting a new project file, the crash happens when I just try to launch the engine and decide what to do? Any Ideas? No plugins installed etc. Thanks
To clarify, as you are using a new project, when you get the error message that has taken a screenshot of, does it say “LeapMotionController” or just “LeapMotion”? Also, if the project is crashing, could you provide the logs from the project where this crash occurred? They can be found in the project’s directory under Saved > Logs.
Re: It says leap motion controller… and on my end there is no project started yet / built yet, its even before that step ( my stuff has been on mac side, and on windows its 100% fresh right now )
Just to state this clear. i did no conversion from any older engine version. the project i tried to open were created with 4.11.0. Just forgot to mention this.
In the meantime, if you weren’t having problems with 4.11 prior to the hotfix, I would suggest downloading the Source built from Github and installing that if you have the space available.
I’ll be working on figuring out what is wrong and get back to you as soon as possible, but having the Github version should let you keep using the editor for now at least.
Edit: The main thing that perplexes me about this, and the reason why I assumed you had converted from a previous version, is that the plugin isn’t even called LeapMotionController anymore, as there was an update and has been changed to be called LeapMotion with its release for 4.11.
That does sound like the case. Can both of you check your 4.11 installation for a certain directory? The default install location should be C:\Program Files\Epic Games\4.11\Engine\Plugins\Runtime\LeapMotionController. If that folder exists, please either delete it or move it out of the 4.11’s installation directory. Please don’t mix it up with the LeapMotion folder, as that folder needs to stay where it is.
It’s possible that the launcher didn’t clear out the old files for the plugin when you upgraded to the new version, so removing the LeapMotionController files should fix the problem.
Hi , I also get the same error, but only after launching the packaged game. I am using a source build of 4.11.2 (from yesterday). The folder “LeapMotionController” does not exist in my Engine\Plugins\Runtime\ directory, I only got a “LeapMotion” folder.
The “LeapMotion” plugin is disabled by default and I never changed anything about that. Enabling it does not change anything about the error, but I guess thats expected because it’s a totally different plugin than the one the engine searches for.
Is this project from a previous version of the engine perhaps? If it is converted from a previous version, that would explain it searching for that name, since the plugin was called LeapMotionController in 4.10 and prior. Also, did this occur at all in 4.11 or 4.11.1?
The project was started with 4.11P5. Packaging with 4.11P5 worked fine, I only recently upgraded to a source build of 4.11.2, so I never tried to package with anything in between.
How can I make the engine stop searching for the LeapMotionController plugin?
Just wondering. Found both folders just like you said. But isn’t every Major Engine Version like 4.11 preview a clean install?
Okay the first version that was installed of version 4.11 were the preview 1
maybe the folder still existed there and that “check” came in with the hotfix.
But yeah this would explain my situation. But not the situation of paradise10010.
As for now the moving of the LeapMotionController folder seems to work for me. But still on testing
EDIT:
atleast i can start the creation of new projects. i will test if i will run into the same problems like Alcatraz when i got the time to do this.
You’re correct. Installing a separate version of the editor does result in a clean install. In this case however, the LeapMotion plugin was not changed from LeapMotionController until Preview 6 of 4.11, meaning anyone with preview 5 or earlier could run into that problem, while it’s not guaranteed since it didn’t happen to me.
In that particular project, you should be able to disable it from trying to find that by right-clicking the .uproject file, editing it in a text editor, and replacing the “True” under the LeapMotionController plugin entry with “False”. I’m currently looking into how to make the engine stop enabling it by default with new projects.
The “LeapMotionController” is not mentioned in the .uproject file, so it has to be somewhere else. Any idea where I should search for it? This is a code project if it helps.
As this issue has been fixed for both and , I’ll be marking this as the accepted answer. If you still have problems after attempting the fixes proposed here, please let me know, Paradise10010, and I’ll be happy to assist you further.
