Technical support > Feature Requests
Testing request: 2.1.1 testinstaller.
smalul:
--- Quote from: "Mattn" ---just make sure that you are using new savegames for every new binary - e.g don't use savegames from 20.04 binaries and try to load them into 22.04 binaries. that won't work
--- End quote ---
The files from my previous post are new game started in the April 22th version. I will always use the newer versions, as long as you release them for download, but please - give each release a different version number - it would make it much easier to refer to the right version.
Zenerka:
smalul, you are very good betatester and really no need to apologize for bugreports - that is your "job" here and our job is to read.
So did I, and have additional questions/requests.
I loaded your Shai50 and got assertion hit for (type < MSG_MAX) at cl_menu.c:3977 (writing it here just to not forget). But I suspect that the save is just corrupted. Then I loaded your Shai49 without any problem. Placed second base, added two radars, powerplant and quarters there, then went back to first base, placed two additional radars there - all exactly what you wrote. Then back to geoscape. No errors. Then saved. No errors. Then loaded. No errors. The bytes amount for load/save are ok. So I am asking - can you reproduce that with Shai49? If yes, can you, please, note all the steps you are doing to reproduce that bug? That would really help to identify that.
The B_GetNumberOfBuildingsInBaseByTypeIDX: Bad base-index given: 2 (numbases 2) error - just looking to the code, looks impossible to hit. The only way to get this would be to call this function with parameter being base index bigger than or equal to the amount of bases. Actually it can be done if only the baseCurrent pointer DOES NOT point to existing base... but THAT would mean something is really broken somewhere, because baseCurrent should always point to existing base. Otherwise -> KABOOM.
smalul:
--- Quote from: "Zenerka" ---So I am asking - can you reproduce that with Shai49? If yes, can you, please, note all the steps you are doing to reproduce that bug? That would really help to identify that.
--- End quote ---
Sorry, but I have not been able to reproduce this bug. I know that in both cases (in games started with both the April 20th and April 22th versions) I had 2 bases, with more than 1 radar station in each.
I will run memtest86 overnight just to make sure I don't have any problems with my computer memory.
--- Quote from: "Zenerka" ---The B_GetNumberOfBuildingsInBaseByTypeIDX: Bad base-index given: 2 (numbases 2) error - just looking to the code, looks impossible to hit. The only way to get this would be to call this function with parameter being base index bigger than or equal to the amount of bases. Actually it can be done if only the baseCurrent pointer DOES NOT point to existing base... but THAT would mean something is really broken somewhere, because baseCurrent should always point to existing base. Otherwise -> KABOOM.
--- End quote ---
I have had this bug more than once, and now that I think of it - I'm quite sure some kind of saving/loading crash followed this bug.
Zenerka:
Updated first post here with the links to newest testinstaller. If nothing bad happens, this is the "final" testinstaller before 2.1.1 release. Changes:
- small bugfixes for various things
- one serious bugfix for savegame system (which means saved games from previous versions won't work)
- employee renaming reintroduced.
As always, testing is needed and bugreports should be placed here and additional on sf if they are not about saving/loading.
Thanks to you, people, for your hard betatesting work.
smalul:
I got another "Assertion failed!" with the April 22th version, but now I see there is a newer version, so I'm downloading it now.
By the way, memtest86 didn't find any problem with my computer memory (after more than 10 hours), so do you have any idea what else could cause such a corruption of the saved games files, if it's not a problem with the load/save system?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version