I see in some of the examples that the nuitrack.config file has some settings relating to smoothing skeleton data, however I can’t find this documented anywhere. Perhaps I just missed the page, but I can’t seem to find much documentation for nuitrack.config options in general? Is there a documentation page for the config settings?
I would like to smooth skeleton tracking slightly to make it less jittery, at the cost of introducing a little lag. How can this be configured? Also, I would like to use the integrated installation method for my app - the documentation doesn’t mention where the nuitrack.config file should be placed for integrated installations.
We don’t really have specific documentation for the nuitrack.config file because this file is primarily for internal use.
If you’re not satisfied wit accuracy please record specific problem case using this utility and send us : nuitrack-sdk/doc/Failure_Case_Recorder.md at master · 3DiVi/nuitrack-sdk · GitHub
So we can better understand the issue and provide you with possible solutions.
After you execute the make_embedded script, nuitrack.config will also be unpacked, so you do not need to copy it manually. (you can find it at nuitrack/data/nuitrack.config)
Hi @vadim.bazhin Thank you for your reply. I am now smoothing the data as needed within my application itself which works for me. However, I now have bigger problems as the issue I described in this post seems to be back: Nuitrack App crashing with Astra 2 Recently, whenever I open OrbbecViewer my Astra 2 camera is listed as a USB2.0 device rather than USB 3.0, and then Nuitrack crashes when I run the demo app. This was previously working but has recently started failing again. I haven’t changed anything in my set-up expect possibly a Windows update. I’ve tried re-installing Orbbec driver, upgrading to latest Nuitrack, upgrading all other drivers on my PC but nothing has worked so far. Any help would be much appreciated. Thanks.
It doesn’t seem to be a software problem, please make sure the USB cable mounting screws are screwed in from the sensor side.
Also, if possible, could you test this sensor with a different USB3 port / cable / host PC, would the problem persist?