I have done all things according to the docs, set all paths, I successfuly run BasicSkeleton example scen in the Editor.
When i built it for an 64 bit device i recieve the above exception inside the NuiTrackManager script at the niutrack.Run function.
Why is that happening?
The only think I am not sure i have done it correctly is that according to the docs you should copy .bin., .data, and .middleware folder into your <app_dir> and then give the path “<app_dir/data/nuitrack.config>” in Init()
For the <app_dir> i have chosen the forlder of the project where assets, library, project settings,… are
I don’t know. Only the 3DiVi staff can answer to that. I’ve been merely evaluating the sdk’s capabilities in trial version before our company makes a decision. So far it seems there are better alternatives with more responsive support.
I copied the contents of the bin folder in the project root folder (i.e. same folder where library, assets etc are).
In build, I copied the files to root folder as well (where the .exe resides).
I did not copy files from other folders. Do think some of those files are needed?
Copying same files to each app’s folder is not really acceptable solution in the long run, but at this point I’m willing to make compromise if some kind of temporarily solution is found out.
Well at first I want to build an .exe nothing relate to an android project so your tutorial in your page (please) MUST be more flexible and change.
I have done the same action by install and activating realsense d455 and nuitrack latest version
Following the instuctions from nuitrack documentation on github and it plays again in unity editor 2019.4 (I have all my specs above).
When I build an .exe file code crashes at nuitrack.Run() , meaning that ddl are correctly initialized but somethis is going on probably with d455 and your sdk on windows 10 unity build.
May I ask why you ponted me at an android tutorial and can you help me solve thsi issue?
Although the tutorial says “android”, in fact, it is universal. And it should work both in the editor and in the Windows application.
Let’s try to figure out what the problem is.
Run the allModulesScene in the editor with the connected sensor. And, if it works, then build the application with this scene and report the error on the screen.