@Hadasi If it still doesn’t work for you, here’s another build you can try - it explicitly enables TLS 1.2 on our side, so we can be sure that isn’t the culprit anymore. I came across this myself while investigating something completely different.
From the logs you’re also affected by that TLS 1.2 security stuff. No idea why this now pops up all over the place. The fix I mentioned above wasn’t yet merged in the preview you were using. Just pushed a new version (0083) which explicitly enables TLS 1.2 on our side before doing the nuget restore - can you try with that version please?
Jesus, seems you stumbled upon something very special here :/
Root cause is that the Stride asset compiler can’t load the Microsoft.Kinect.Face.dll because of this - and the very bad news is that there’s no immediate fix. Only workaround I can think of is to remove the entire Face reference and all nodes with it - which is obviously only an option if you don’t make use of it.
Otherwise you’re out of luck as long as we don’t have a fix in Stride. Will open an issue there.
Ah, ok, I’m just using what is in that patch, skeleton and depth, how do I remove the face reference, do I have to remove it from the nuget? (I’ve always been good at finding the weirdest errors, its like a superpower!)
Any clues as to how to remove kinect face, I’d like to export to an app to see if that gains me any performance, I presume so, as there is no gui, my patch is almost running perfectly on a latte panda with an atom Z8350, it would be great to get it fully working on it.
Removing the face dll from the nuget gives me an error still
My superpower again, even with your version I still have the same issue, same build of gamma, downloaded the patch from here again, even deleted the dll which you hadn’t, and unhappy exporter!
Thanks for testing though!