PatHightree / SpaceNavigator

SpaceNavigator driver for Unity3D
MIT License
171 stars 53 forks source link

Error building player in Unity Hololens branch #10

Closed ghost closed 3 years ago

ghost commented 8 years ago

Unity (hololens branch) throws 54 errors when the scene is built, and will subsequently not run in visual studio. I'm currently working with the hololens emulator, not a physical device yet. Once the SpaceNavigator asset is removed, the build works. Easy to workaround for now, but I thought you should know. Log file attached. Editor.docx

PatHightree commented 8 years ago

Thanks for reporting. I was going to ask you to send your hololens over so I can investigate, but then I saw you're using the emulator ;)

It looks like the hololens sdk project has System.Runtime.InteropServices disabled or configured in such a way that SpaceNavigator can't use it. Which is unfortunate, because the functionality to get data from the device is located in a dll. As a workaround, you could wrap each C# file with

if UNITY_EDITOR

endif

That would keep the code out of the player.

ghost commented 8 years ago

When the actual device comes you're more than welcome to come over to do some investigating. I'll give it a try tomorrow and confirm that the fix works. Thanks!

myreee commented 7 years ago

I have the same problem. It only happens when building for the hololens. Never in the editor. Deleting and re importing the assets is a huge pain.

PatHightree commented 7 years ago

I've reproduced the issue. The workaround I proposed above does not work, because it is the code inside the the3dconnexion dll that tries to reference the interop namespace. Maybe 3dconnexion have a newer dll that is compatible windows store ? Unfortunately I cannot enter the 3dconnexion site at the moment. To be continued.

PatHightree commented 3 years ago

Closing this issue as with version 2.0.0, the driver has moved away from dll based communication to Unity's new Input System.