I also took some time to look into directly including System.Runtime.WindowsRuntime.dll directly into Unity, however, Unity repeatedly stated that that assembly would cause errors and unloaded it. Th

1. I tested the noppl branch, and Unity still freezes, and now also crashing after second time. @Eric - Is there something else to do ? Is the PPL is also inside the "Windows.Devices.Bluetoo

Adding nuget packages to a unity project.

https://github.com/tpitman/unity-plugin-mbientlab-metamotionr-example

Adding nuget packages to a unity project.

What you suggest might be available on Windows, but I can't find it anywhere on macOS in Unity or Visual Studio for Mac.

If you're using Unity 2018, you don't need to import the source code into Unity. As stated in the C# SDK's readme:

I make a plugin for Unity that gives Unity developers Bluetooth Low Energy support on iOS and Android in a single plugin. It is cross platform.

Good to hear you're going to try and help it getting it working in Unity Eric.

I have no idea if it works in Unity but if it does, then great, you can just use the .NET Framework plugin and avoid the native dll entirely. The same Win10 plugin package also provides the same code

Eric. Just to be clear... Are you (and by you I mean Mbientlab in general) working towards making the Mbientlab sensor work in Unity?

and one that terminates it, that we can use in Unity's OnApplicationQuit().

(https://mbientlab.com/community/discussion/2601/unity-works-perfectly-with-metawear-sensor-on-first-run-hangs-on-2nd-run#latest "here")?

I tried option 3 from my previous post. I'm calling GetCurrentThread in your PPL async callback, and setting the DELETE restriction on the thread so that Unity ignores the thread when it shuts down th

We compile them as DLLs in Visual Studio. For Unity we place it in Assets->Plugins->MbientLab.MetaWear.dll

Hey GabRiv, How did you manage to set up Unity to recognize the SDKs you used? did you place them on a specific folder, did you compile them as DLLs, or did you do anything different?

https://forum.unity.com/threads/problem-with-callbacks.87513/

The task result code is 45 the first time around, and then unity freezes on 2nd play. Now that we have a minimum reproducible test, I'll see if there is a potential work-around. I doubt we'll ever get

If the same freezing behavior appears, then its highly likely a compatibility issue between Unity and Window's thread management for its async task classes. In that case, the issue is out of our hand

This discussion was created from comments split from: Unity works perfectly with MetaWear sensor on first run, hangs on 2nd run.