Post not yet marked as solved
Are you monitoring the cameraDidChangeTrackingState? This is needed to deal with interruptions to the session and decide how to handle them.
Post not yet marked as solved
I can’t tell from this. For me, random crashes in ARKit seem to always trace back to improper access to the main thread. A variable getting accessed on the main that is also being changed on another thread. 99% of the time it’s fine. But occasionally it collides with itself.
Post not yet marked as solved
It would be like any file, wouldn’t it? I’d probably setup a dedicated folder for the app’s ICloud drive and pick it up from there. Plus that interface allows the user to select it from anywhere on their drive. Look up UIDocumentPickerViewController.
Post not yet marked as solved
Solved. Turns out I'm just not very bright. Didn't set the class variable in my init. So it only had an empty array to work with.
Post not yet marked as solved
I’m hacking away at this. I know this is months old and you’ve probably already solved it. The fastest I’ve found is mesh to voxel. I can’t top that algorithmically yet even with multithreading. But now you need meshes and the problems that can go with that. And is there an opposite to “setvoxelatindex”? I can set them but I can’t make them go away in similar fashion. I use Boolean between two voxel arrays instead. Getting them to relate to each other properly doesn't seem very intuitive for me. The things are all “get” and no “set”. But it’s a real speed advantage versus iterating over each element.
Post not yet marked as solved
I just got this error after doing the 5.3 update today. Works on device but not on simulator.
I did find that commenting out SCNCamera's zNear and zFar prevented the app from crashing immediately. Not a practical solution as it doesn't display the scene either. I don't call "setDepthClipMode".
