we have created application for interactive exposition using Wikitude SDK v.5.3.1. and we were using it successfully. Now, we want to update our application with Wikitude v.8.5.0. After trying Wikitude SDK v.8.5.0. (for iOS) we faced some critical problems in rendering 3D model which has internal animation.
Here is the link to video with description of the problem: https://drive.google.com/file/d/1-21YJiT12-deAlvRddlmaFfRmN6I-gzY/view?usp=sharing
Also here is some relevant information regarding this issue:
Version of the SDK
Are you using the JS API?
Are you using any of our Extensions (Titanium, Cordova, Xamarin, Unity)? If yes, which version are you using?
Application doesn't crash. It just renders undesired artefact shortly before it starts correct rendering. It could be important to note that this animation crashed the application on second appearance before Wikitude 8.5.0. Now it doesn't crash the application no matter how many times it's triggered, but it just renders the artefact shortly if previously the same animation wasn't fully completed. It just seems that if previously the same animation is not completed then it's not unloaded fully, so on second (and later) appearances it just shows leftovers from the previous run.
What device does this happen with (os Version and model)?
Latest 12.3.1 iOS version. Multiple iPads (iPad Mini 4, iPad 4 etc.).
Is this happening with the sample app or in your own app? If it happens with your own app, does the sample app work on your device?
We tried to test on Wikitude Sample App, however none of the 3D models were triggered when tracking Car Ad.
Send exact steps to reproduce this issue and a video so we can check how we can reproduce this issue (in this case the link to your video)
Please see the video in the link.
Please, we need fix for this issue.
thank you for the detailed description and demonstration, we don't get very many of those with the initial issue report.
We've recently added code that tries to resume animations that have been interrupted by either losing tracking or pausing the application. This code seems to malfunction in your case. The 5.3.1 version of the SDK did not do any such attempt to recover an interrupted animation.
What you could try as an immediate fix is calling `stop` on the `AR.ModelAnimation` in the `onImageLost` callback function of the `AR.ImageTrackable` and then correspondingly calling `start` in `onImageRecognized`. I believe this should reset the animation to its original state and bypass the resuming procedure.