We have several experiences created that take a tour of several different scenes. We have used the same method as the Google "Hotspot Example." We are experiencing crashes when the user moves around the scenes (no more than 10 on any experience) and hits the hotsposts around 20 times. This happens on iOS and IE. It seems to work okay on FireFox.
When using the Memory Profiler in IE, you can see that each time you go to a new scene, it increases the memory being used by about 50mb each hotspot. Shouldn't there be something that is scrapping the previous scene when you move to the next? Any help would be greatly appreciated!
Hello!
We have several experiences created that take a tour of several different scenes. We have used the same method as the Google "Hotspot Example." We are experiencing crashes when the user moves around the scenes (no more than 10 on any experience) and hits the hotsposts around 20 times. This happens on iOS and IE. It seems to work okay on FireFox.
When using the Memory Profiler in IE, you can see that each time you go to a new scene, it increases the memory being used by about 50mb each hotspot. Shouldn't there be something that is scrapping the previous scene when you move to the next? Any help would be greatly appreciated!