Hi,
I’m on Windows 11, having this issue.
When launching a project with the latest zed-unity package from github I get this message in Unity. I have the latest SDK (5.0.2) installed. Depth Viewer f.e. is running just fine.
Any idea how to troubleshoot this?
I just got a new Laptop with an RTX 5000 series, so I had to upgrade from SDK 4.2.5 which was working fine with the older Unity Package.
Unity Version is 6000.1.9f1
Best, Jan
Thanks Benjamin for reaching out!
The diagnostic tool seams to crash. It checks everything until the step Devices and then just closes.
(same after uninstalling and installing the SDK from scratch, which I just tried)
Can I ask you how you install the Unity package?
What was it through the package manager, or did you download the release directly from GitHub?
Thanks.
Stereolabs Support
Sure, via the package manager from the link provided on github.
https://github.com/stereolabs/zed-unity.git?path=/ZEDCamera/Assets
Ok thanks.
The issue might come from the ZED SDK installation itself.
Can you try to run a tool we provide with the SDK, ZED Depth Viewer for example?
Stereolabs Support
Yes, they all seem to work 
Is there a config somewhere where I could point the Unity SDK to the ZED SDK?!
Do you have, by any chance, Dependancy walker installed on your machine? (https://github.com/lucasg/Dependencies)
If so, you could open the slèunitywrapper.dll lib with it and share a screenshot of the result?
You can find it at My project\Library\PackageCache\com.stereolabs.zed\SDK\Plugins\x86_64
Stereolabs Support
Yes, sure. here you go. Is that what you need?
Is the sl_zed64.dll showing as incorrect an issue? File is there and it’s not empty at least 
Maybe also relevant, it not only happened on this laptop. I also tried installing 5.2.0 SDK on my older machine, where the latest Unity SDK failed to find it as well.
Thanks, that’s perfect. Everything looks fine, it manages to load the lib from the ZED SDK.
I need take a closer look on my side to understand what’s not working as intended.
I’ll keep you informed when I have a solution.
Best,
I made a small change, hoping it fixes the issue on your side.
Can you update the plugin and try again ? I changed the version to 5.0.2 as well.
I am a bit embarrased now 
I think the error was a special character in the file path (an “Ö” to be specific). A bit of a german rookie mistake.
It is still peculiar though, it worked with the 4.2.5 SDK and the same filepath. Let’s say that’s the reason I didn’t try removing the “Ö” sooner 
But everything’s working now, thank you so much for your efforts!
No problem, it can happen to everyone!
Stereolabs Support