Save game to slot did not work in background thread

Development Programming & Scripting
1

Hey guys, I find my game experiences a noticeable hitch when the game is saved. Therefore, I decided to move the “save game to slot” to the background thread. However, I had some problems when doing so.

  1. The function works fine on the game thread. However, it seems did not work on the background thread. That’s how I did that:

    image
    image1207×698 55.8 KB

  2. Second, I know there is a function called “Async save game to slot”. However, it seems it still hangs the game when the game is saved.
    image

Did I miss sth? Thank you guys in advanced!

2

I don’t know about the C++ implementation of this, but I did test the async node and found both of these things:

  1. Hitching ( I thought the whole point of async was not to do that )

  2. Incomplete saves

One thing I might say about 2, is that I think it will work successfully, as long as there is only one call running concurrently.

4

I checked the SaveGameObject.sav under the saved directory, and the size is just 2kb, which equals to nothing. When I use the game thread to save, it’s about 34mb. Too weird lol

1 Like
5

yeah SaveGameToSlot has to run on game thread, calling it from a background thread just silently does nothing. thats why your bg version never writes

AsyncSaveGameToSlot helps with file io but LoadGameFromMemory / serialize still hits game thread so big saves still hitch a bit. keep struct lean or chunk arrays if its large

advanced save system from fab Save System / Cloud Save / Encryption / Slot management | Fab wraps async properly so you dont have to hand-roll threads, does the save off thread where possible and keeps hitches down vs vanilla nodes