actually there are some other wt3 which has the same habit in my project
Bascially if one crashed, it will affect the whole arworld and the only thing you can do is to kill the app and restart the app...
Thank you for your help
about 5 years ago
Please test with latest SDK version (an update was just released yesterday) and check if the issue still occurs.
Also ensure to optimize your 3D Models for mobile use, a 6.5MB wt3 file is not recommended as it will consume multiples of the compressed filesize in memory. Please try optimizing it so that it uses hald of the size approx. Besides that I recommend using a datastructure that holds all required information of an augmentation, that way you can easily loop through components that need to be paused or destroyed instead of hardcoding them.