Search Issue Tracker
By Design
Votes
0
Found in
2017.2.0b2
Issue ID
934865
Regression
No
[New scripting runtime] Linking problem Kinect v2 SDK .NET 4.6
TypeLoadException while trying to load Kinect libs with .Net 4.6 profile.
1. What happened
From this forum post:
https://forum.unity3d.com/threads/problems-with-kinect-2-dll-and-net-4-6-profile.483478/
The attached project contains the dlls but in case you want to use the proper SDK, install the following:
https://www.microsoft.com/en-us/download/details.aspx?id=44561
2. How we can reproduce it using the example you attached
- Open attached project
- See errors in Editor.log:
TypeLoadException: Could not load type of field 'KinectTestScript:m_pKinectSensor' (0) due to: Could not load file or assembly 'Microsoft.Kinect, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. assembly:Microsoft.Kinect, Version=2.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 type:<unknown type> member:<none>
at (wrapper managed-to-native) System.RuntimeType:GetFields_native (System.RuntimeType,intptr,System.Reflection.BindingFlags)
...
Tried on Windows 10 in:
Version 2017.3.0a1 (b7f5aac47235)
Tue, 18 Jul 2017 12:54:26 GMT
Branch: trunk
Comments (1)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
npatch
Feb 01, 2018 14:36
Even if we don't include the dlls in the Plugins folder and just reference them in Visual Studio, intellisense resolves the symbols and removes the squiggly error lines and works ok, but Unity does not resolve the errors.