Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UE 5.4.2 - v5.0.1 - Plugin 'UltraleapTracking' failed to load because module 'UltraleapTrackingEditor' could not be loaded #147

Open
kefon opened this issue Jul 7, 2024 · 3 comments

Comments

@kefon
Copy link

kefon commented Jul 7, 2024

I'm unable to launch an existing 5.4.2 UE project using the Ultraleap plugin (v5.0.1). I tried a different approaches but each time I activate the plugin and restart the editor, I get the error:

"Plugin 'UltraleapTracking' failed to load because module 'UltraleapTrackingEditor' could not be loaded".

What I tried:

  • add the plugin via the marketplace (add the plugin to 5.4.2 engine), open the project and activate the plugin, restart -> error

  • uninstall the plugin from the engine, then download the plugin via github (using latest release v5.0.1), add the plugin into the Plugins folder, launch the project -> error

  • redo the two previous steps using a new empty project -> error

Any idea?
Thanks!

My setup:

  • Leap Motion Controller v1
  • Ultraleap Gemini v5.20.0
  • Window 11
  • For precision, I have previous projects in UE 5.2 + ultraleap plugin working fine
@JamesProvan-UL
Copy link

Hi @kefon.

This due to a dependency our plugin has on the OpenXR plugin. This has always been the case, but it looks like its now a breaking issue in Unreal Engine 5.4.

I am going to look at fixing this directly in our plugin, but in the meantime please follow these steps to get 5.0.1 working in UE 5.4.

  1. Create a new Unreal 5.4 project.
  2. Open the project and enable OpenXR plugin in the "Plugins" window.
  3. Close the project, then add the Ultraleap hand tracking plugin using either the marketplace or via GitHub directly.
  4. Re-open the project - you should find the error does not occur and you can now use our plugin.

Hope that works out for you.
Jim

@kefon
Copy link
Author

kefon commented Jul 31, 2024 via email

@kefon
Copy link
Author

kefon commented Aug 1, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants