Addressing a fix for the basic starting error with the RealSense SDK plugin in Unity 5 has been addressed here:
https://software.intel.com/en-us/forums/topic/542710
Some moderator can merge this thread if they feel the need. To sum up the basic set up, I'll write the steps quickly, re-iterating in a little more detail how to set up in Unity 5, then additionally help you get rid of some of those warnings about deprecated code as well. At the time of this post, Unity 5.0.1 is the most recent release version as of April 8th, 2015.
1. Open Unity 5 (This step is the same for previous versions of Unity; however, Unity 5 will allow you to use the "personal free" version which is the full pro version. In earlier releases, 4.6 and earlier, you must have the Pro version of Unity). Anyway, open Unity... and create or select the project in which you want to use the Intel RealSense plugin. Select "Assets > Import Package > Custom Package" from the menu bar. You will find the RSUnityToolkit package that you want to import, I'm fairly sure by default, in the "C:\Program Files (x86)\Intel\RSSDK\framework\Unity" folder. Click this and select all (I'm just saying for general purposes, select all) and click import.
2. Specifically to get the currently provided RSUnityToolkit package up and running in Unity 5, like Rick Blacker mentioned, you must replace the libxccpp2c.dll and libxccpp2c.dll.signature with the 64 bit versions. You can find these by default included with the RealSense SDK installation in "C:\Program Files (x86)\Intel\RSSDK\bin\x64" hiding among a lot of other dll files. Copy these two files and paste them in your Unity 5.0.1 project. These two files must replace the existing copies located in your project found by default in the "...Assets/Plugins" directory in your hierarchy.
3. In addition to the two necessary files, you might also note that there is a 64 bit version of the libpxcclr.unity.dll file included in the "C:\Program Files (x86)\Intel\RSSDK\bin\x64" folder. I would recommend copying this file into your project as well.
Now let's get rid of a couple of those pesky warnings that crop up in the console every time Unity re-compiles your code.
Let's do the easy one first. "...warning CS0618: 'UnityEngine.Object.FindSceneObjectsOfType(System.Type) is obsolete." Clicking on this warning should open up Monodevelop and take you straight to line 90 in the C# script where you can literally do exactly what the warning asks you to do. Just delete the word "Scene" from the method to use the updated method "FindObjectsOfType" in Unity 5.
The second one is almost as easy. "CS0618: 'UnityEditor.EditorGUIUtility.LookLikeInspector()' is obsolete." There are some Stackoverflow Q&A's covering this. What you want to do is comment out or delete the offending line of deprecated code, line 80 in Monodevelop according to the warning in my console. Then add these two lines instead:
EditorGUIUtility.labelWidth = 0; EditorGUIUtility.fieldWidth = 0;
The only warnings you'll have to put up with for the time being (if you imported the entire package) are merely Intel RealSense specific. They are regarding the use of deprecated methods in the RealSense SDK that may be updated soon. You can certainly dive in and try to update the methods yourself. Here's a good starting point:
The warning is letting you know that there is a newer, potentially better way to initialize and query the PXCMBlob information from the camera. Instead of using the PXCMBlobExtractor object, there is an updated way to initialize this object using the PXCMBlobModule class.
If you begin by replacing line 93 in the "SenseToolkitManager.cs" file, you'll see what I mean. Beyond this point these are no longer instructions. I'm making some observations and will not attempt to update the blob detection methods. Replace:
with
You could change the name of the object, but that would be more trouble than it's worth. Ok? Then do the same thing in line 428 of the "SenseToolkitManager.cs" script. You'll get some initialization errors because the method for initializing the blob has changed.
Initializing the Blob:
Configuring the Blob:
The documentation code is very clear and can be followed specifically using the C# sample. Hopefully if you are interested and have read this far, you can follow this initialization method fairly easily. Assign the configuration of the BlobExtractor (so it's called in the Unity file) to the "sm" and "blobConfig" objects thus:
I guess I could just paste that directly in from Monodevelop... starting from line 615 of "SenseToolkitManager.cs":
if (!_isInitBlob)
{
// the deprecated lines, commented out...
//PXCMImage.ImageInfo info = ImageDepthOutput.QueryInfo();
//BlobExtractor.Init(info);
//BlobExtractor.SetMaxBlobs(MaxBlobsToDetect);
//
// Create an instance of the SenseManager
PXCMSenseManager sm = PXCMSenseManager.CreateInstance();
// Enable the blob module
sm.EnableBlob();
// Get an instance of PXCMBlobModule
BlobExtractor = sm.QueryBlob();
// Get an instance of PXCMBlobConfiguration
PXCMBlobConfiguration blobConfig = BlobExtractor.CreateActiveConfiguration();
// Configure the blob module
blobConfig.SetMaxBlobs(MaxBlobsToDetect);
// … call more configuration methods
// Apply the new configuration values
blobConfig.ApplyChanges();
_isInitBlob = true;
}
Anyway, that's where I get stuck updating the blob methods or just don't want to bother right now. The next piece of the puzzle here would be simply updating the "BlobDetectedRule.cs" file. Just looking at the function calls, it's clear that a blobConfig method needs to be used instead of directly accessing the BlobExtractor object itself. If you'd like to dive further down that rabbit hole here, please feel free.
Thanks, and I hope you found the first part helpful at the very least.
Until next time,
Link Copied
