Trying to run the Sample2-Rotation&Scale Unity Project

[Kiriakos_T_]

Hi,

I am trying to run the Sample2 which has been built in Unity. First of all, I changed the root path directory of "framework\Unity file" to Desktop, because there were some problems with Unity. After that I loaded the project and I run it. When I press "play" button then some warnings appeared

Sense Manager Object not found and was added automatically
UnityEngine.Debug:LogWarning(Object)
BaseAction:Start() (at Assets/RSUnityToolkit/Internals/Actions Utils/BaseAction.cs:497)

and 

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)

and I can't understand where is the error!

Could anybody explain me that?

Thank you in advanced!

[Pubudu-Silva_Intel]

Could you please specify the name of the sample?

[Matthew_S_2]

I ran into this same issue for the unity toolkit samples.  The ones I looked at were Sample 1, Sample 2, and Sample 6.

[MartyG]

The first line, "Sense Manager Object not found and was added automatically", is nothing to worry about.  It's more of a notification than an error.

As for the rest of it ... I wonder if it is a consequence of moving just the Framework folder to the desktop. Maybe it would work better if you installed the entire RSSDK to another area, such as your desktop or the root of your C: drive instead of the Programs directory of C:.

Also, Unity tries to load in the last project that was used in it, and looks for the files in the same location they were before.  So if you had the Framework folder installed in the RSSDK folder and then moved it to the desktop, the next time you run Unity it would be looking in RSSDK for the project files and not finding them.  To correct this, selecting Open Project from Unity's File menu and opening the project from it's new location on the desktop might correct that problem if that is what is happening.

[Yuri_B_1]

Did someone manage this issue? I have created new project and tried to add Sense AR to scene. But I got :

Unable to initialize all modalities
UnityEngine.Debug:LogError(Object)
RSUnityToolkit.SenseToolkitManager:OnEnable() (at Assets/RSUnityToolkit/Internals/RealSenseInput/SenseToolkitManager.cs:333)
RSUnityToolkit.SenseToolkitManager:Update() (at Assets/RSUnityToolkit/Internals/RealSenseInput/SenseToolkitManager.cs:550)

[Yuri_B_1]

Did someone manage this issue? I have created new project and tried to add Sense AR to scene. But I got :

Unable to initialize all modalities
UnityEngine.Debug:LogError(Object)
RSUnityToolkit.SenseToolkitManager:OnEnable() (at Assets/RSUnityToolkit/Internals/RealSenseInput/SenseToolkitManager.cs:333)
RSUnityToolkit.SenseToolkitManager:Update() (at Assets/RSUnityToolkit/Internals/RealSenseInput/SenseToolkitManager.cs:550)

[eyalfoni]

Hi,

I'm getting the same error - has anyone figured out the issue?

All the Unity Toolkit examples have this same error except for the object tracking example (sample 7, the last one). What is different about this example?

Best,

Eyal

[Marco_B_1]

I used the toolkit without any issue until I opened one of the sample scenes and started to get this error.

[Marco_B_1]

I *seem* to have it figured out for the case where I just add the 'tracking action'  (RSUnityToolkit/Actions/TrackingAction).

That action is configured to track hands by default

I was seeing the sensing manager open the rs300 camera, but then shut it down.

If I just put a hand in front of the camera before I press play on the unity scene, then no error is shown and the tracking actually works.

What seems to happen is that the SenseToolkitManager.cs script tries to track what it is supposed to track (the hand in my example) and if it doesn't find any it fails instead of trying again at a later time, which was my expectation.

Also, I was in a room at dusk without additional light, which may also have caused problems to the sensors.