@ Soren
Quote: "Could anyone else try saving/loading some built games? It could help locating the bug (there might be more than one)."
I can verify that we have an issue with saving/loading a saved game. I have posted this on more than one occasion, only to have my posts ignored or no response. I can also tell you that my partners are also aware of this issue which caused us to restart a complete commercial project. After reviewing your bug report, I can confirm that is a similar error that we received as well. Here is what happened on our end.
We had a WW2 commercial development we had started. We discovered that we could save a game, but the load gave us the exact same error as you have outlined. I took out RPG Mod and tried the vanilla FPSC- same results. I went through the entire code for both FPSC and RPG Mod and could not spot the problem. So after numerous tests, we devised a solution. I had to put "save points" in our game. In other words, the player does level one, then hits a small "segment-room" level 2 where their progress is auto-saved. Then they go to level 3, another save-point in level 4, and so on. This was the only way we could have the player load a saved game with no issues. I also had to disable the ability to save during the game and rely on my auto-save script to look after this.
We use not just stock media, but a lot of custom media as well. Because we develop RPG Mod, we immediately looked at it to see if the error was in our mod. I then swapped to vanilla to ensure and discovered it was the same thing with vanilla FPSC.
It is interesting to note, we tried our SciFi commercial development, and even our newest Egyptian development. Guess what? They save so far with no issues. I could not figure out why that was. All our developments work properly, but only our WW2 developments have this save/load issue. Mind you, we are wondering how long before all our commercial products we are about to deploy will go through this.
Like I mentioned before, it is
very frustrating. As a developer, it is frustrating when you post a legitimate bug only to be ignored. I've even briefed KeithC on this issue so he is aware of it as well. I know it's was suggested to send a stock map, but we have an entire development with this issue and not one person was willing to reply to us or help us out.
Perhaps when you find a solution, you could contact myself to share what you've discovered/learned. My wife and I would be very grateful with whatever you can tell us. I'm hoping this issue is resolved, because we hold 6 titles to be deployed and can't deploy them with this type of issue. All this time spent on projects to hit a brick wall is not exactly a fun time, and becomes costly to some of us.
ADDITIONAL: It might be interesting to note that we battled this issue since v1.16 of FPSC. We mentioned it before v1.17 came out, and now it is brought up in v1.18.
- BlackFox
