Load Game error

Mentos

Prince
Joined
Sep 29, 2010
Messages
377
It happens especially at the initial turn of a game. If you save there and reload the saved game, the game messes up. It only occurs with TBC (using v61 now but happend earlier too)
I remember it happened during a longer game session too sometimes when (re)loading a game.

The only way to reproduce it now is to start a new game with TBC.
1. Let the Settler build the first city
2. Save the game
3. Load the same game again

Then you get like this here:


Buttons won't work anymore, unit icons vanish, and you are totally stuck then.

I tested this with cleared cache folder too and it still happens.
 
I don't know of anything that could cause that from what I do, it's probably some sort of vanilla bug with the store/load game data functions when used in a mod.
 
The UP\Core\Misc Text\Tech* and Production* lua files seem to cause this somehow.
This kind of initialization error won't happen if I don't use these files (but this will maybe break whatever other stuff, of course).

I guess it started when you implemented more foreign mods into the Unoffical Patch. I don't remember this happened few months ago too.
It's like tuning cars. They will sometimes fall apart with too many extras. But at least your mod-pack is still driving most of the time.
 
I don't think it's a problem with those files. There's some sort of vanilla game bug when exiting and loading games. For example, stuff like this happens whenever we "exit to main menu" from a game:

Runtime Error: [string "D:\Thalassicus\Documents\My Games\Sid Meier..."]:28: attempt to index global 'Game' (a nil value)
Runtime Error: [string "D:\Thalassicus\Documents\My Games\Sid Meier..."]:8: attempt to index global 'Game' (a nil value)
Runtime Error: [string "Assets\UI\InGame\InfoTooltipInclude.lua"]:12: attempt to index global 'Game' (a nil value)

This output doesn't make sense because "game" is a core global value, I don't see how it could be nil.

Similarly, when we save and then load a game in the first turn, this happens:

..."]:31: attempt to call global 'setmetatable' (a nil value)

This is completely nonsensical because setmetatable is a standard lua function. I don't override it anywhere in my files, so somewhere in the vanilla game code they've got a bug that's wiping out standard globals and API calls. It happens at the top of my utilities file, which is included everywhere else, and is why it might appear to be an issue in other files when it's really just the first thing that's loaded. :undecide:
 
Yeah, I noticed that only an Exit to Windows helps to load the games successfully again. A wipe to cleanse the jagged memory.
 
I've found quitting to main menu, then going back in through mods to load the game works when it happens to me. Still annoying, but a bit faster than going to Windows.
 
To confirm: I have also found this from a version or two prior to 6.2. Whenever any game is loaded up from within the game (playing), the game usually crashes or screws up. However, if you return to the main menu it loads normally.

Could it be that the game is trying to load the save game without the mods unless you specifically tell it to via the main menu-mods-load?
 
I only know that UP/TBC is somehow making the game mad when loading during a game.
Loading works if I deactivate UP/TBC and only play (some turns) with my other mods.

What's strange that rather manual saves don't get loaded correctly while Auto-Saves most often do. Only talking about loading during a game here.
 
Can anyone confirm the earliest version # they encountered the issue? If I know about when the problem started, I might be able to figure out which change caused the problem.
 
I can't tell you the version but I could help you searching if you have uploaded a bunch of them somewhere.
 
I haven't tested every single version yet, but these messed up UI loading problems seem to start with Balance - Combined (v4.23 beta).
v4.22 and some earlier versions still work according to a couple tests.

Can someone else confirm this?
 
I stopped playing for a while until the most recent patch, so it was definitely since then, but I first noticed it a while ago. I haven't seen it too recently though, and only had it happen maybe 4-5 times total, so it's not a particularly urgent issue.
 
Back
Top Bottom