Hi All,
Thanks for taking the time to read my post. I recently received my Realsense developer kit. Everything installs fine and my camera is detected but I haven't had any success in running any of the examples. When I open an example (e.g. facetracking), I can see the camera feed and all the lights go on, but then the app freezes and does not update the camera feed view. All the buttons in the app become non responsive and I have to force-quit to close it.
I am running windows 8.1, on an intel -7-4700MQ CPU.
If anyone could shed some light on how to resolve thi I would be greatly appreciative
链接已复制
I'm running R2 and I've installed both drivers. Windows is also up to date.
The Capture Viewer runs fine but opening any of the example projects causes the crash mentioned above. When I try to run any of the Unity example projects from the editor, I get the following error:
Unable to initialize all modalities
UnityEngine.MonoBehaviour:print(Object)
RSUnityToolkit.SenseToolkitManager:OnEnable() (at Assets/RSUnityToolkit/Internals/RealSenseInput/SenseToolkitManager.cs:283)
RSUnityToolkit.SenseToolkitManager:Update() (at Assets/RSUnityToolkit/Internals/RealSenseInput/SenseToolkitManager.cs:478)
Is it just a power draw issue? I'll have to go but a powered USB 3.0 hub to test this out, and I'll report back. But if anyone has another solution you can save me a bit of time and money.
Thanks!
I'm having similar issues and I think its a hardware problem.
I purchased 2 cameras. One is working perfectly on the 2 systems I tested it on running windows 8.1 and 8GB of RAM.
The other camera slows down and crashes after a few seconds. The camera lights then go on and off intermittently.
Does the powered USB hub solve this problem?
Anyway to get a replacement camera?
It may be the cable itself. I remember reading somewhere that some units had defective cables...
I also have noticed that when using more than one camera, the system does not work well. Try using different USB ports, disconnecting and connecting it again, and rebooting the computer.
If the error persists, it probably is hardware related...
The powered USB hub could solve the issue if that particular unit needs more power, but it may be another thing...
