Saving Hotspots on iPhone

MoehrIi

Hey,

sadly I'm back here with another question, or should I call it a problem? I implemented an "autosave" action list recently that is getting executed every time our player enters or leaves his hub scene. I implemented it mostly while testing in the editor, where every Remember Hotspot, Inventory item, etc got saved as I imagined it.

Yesterday when I finally built the new "savable demo" onto our iOS devices I saw, that the inventory and variables still got saved fine as they were, but sadly the "remember hotspots" weren't. We're still working on AC 1.63.2 so I'm not sure if that problem still remains in the current version, but sadly when I tried updating, my whole project got all messed up and I'm currently in a bit of a rush in terms of development time. If anyone knows, that the update will fix this issue I will have to take my time bringing everything back to order, or just updating the necessary files.

I hope someone can help me with this problem...it's actually driving me nuts right now.

Sincerely,

Silvan

ChrisIceBox

Are there any other "Remember" components not saving, or present, in your game?  Do your Hotspots have any other Remember/ConstantID components on them?

What exactly is not saving with the Hotspots?  Their enabled state, or the state of the Interactions within them?

I shall attempt a recreation of the problem.  What are your versions of Unity and iOS?

MoehrIi

In a night attempt I actually finally managed to wrap my head around it again (Everybody knows these moments where you wake up in the middle of the night having THE IDEA to fix your problems, right?). 

The thing is, that the Editor ist just REALLY slow when it comes to loading the scenes, while the iOS device speeds through that process. So the actual problem is, that the system is not able to save all the data before the scene is being changed. The actual "bug" would be the editor which is just fine saving everything because it needs so much time loading. As soon as I put in a Wait 1s action the saving worked just fine on iOS aswell, but now it looks a bit weird, because my loading scene isn't starting for 1s. 

There were many things not being saved, all having to do with "Remember components". For instance the visibility settings, hotspot on/off state, interactions. I guess these components were just unlucky because the system is choosing to save them at last.

Would there be any way to wait until the saving is finished before loading the next or unloading the last scene? I don't think the saving process has a wait until finished bool?

ChrisIceBox

Again, I'll need your version numbers, please.

The Save: Save or load Action actually does wait until the process has finished - there's a wait for a callback triggered upon saving is complete.  Can you post a screenshot of the ActionList you're using?

Also, the actual saving of Remember components across scenes should be automatic anyway - no need for manually Autosaving via Actions.  I'd have thought any Autosaving you perform should be at the start of the new scene - rather than the end of the old.

MoehrIi

Okay so as I mentioned in the first post the AC Version is 1.63.2 and Unity was updated to 2018.2.6f1 today.

Hmm well that seems odd...
https://imagebin.ca/v/4E5gzVjs4b4B this is my Action List.

Okay if that's automatic, of course I could save in the next scene, but we actually do want to always load into the hub no matter where the last autosave took place...is there a way to pull that off?

ChrisIceBox

I was referring to the iOS version.

If the Save: Save or load Action is used to load your Autosave, you can check Selective loading? which will give you the option to not load the scene in which the save was recorded.  You can then follow it up with a Scene: Switch Action to load the hub.

MoehrIi

This actually helped so much. It worked perfectly fine. Thanks for your help