Menu

QSave / QLoad test

2014-05-27
2014-06-03
  • Billy Venus

    Billy Venus - 2014-05-27

    Billy Venus wrote:

    I donwloaded FM v.0.8.5.6 and tried to continue the game I initiated with FM v.0.8.5.5,
    but it didn't work. So I intiated a brand new game.

    On the turn # 70 or so, a new bug occured. First I thought it was a "new version" of
    the Blank Data Window bug, just as if you had tried to fix it... in vain. But now I
    think it's a new bug.

    I had opened a Colony Data window (I was needing to check for the Fertilizer reserve),
    then I tried to close it. The window's title bar turned grey (as if toggled to
    background tasks however displayed on the foreground) instead of getting closed.

    I waited a few of seconds but it was still staying there, on the foreground. I tried to closed it again, in vain.

    Then I clicked on the game's main window (displayed in the background) and could open many other Data windows. But I couln't close them, their title bar just turned grey as if toggled to the background tasks, however still displayed on the foreground.

    I opened Paint and pasted there a screenshot, and when I got back to the game, all the Data windows were closed and the game worked fine until the turn # 87 (blank Data window bug).

    Arikande wrote:

    Hi Billy Venus,

    I tried the game on the following machines and again could not reproduce this bug :(
    Desktop - Win 7 - 1920x1080
    Netbook - Win XP - 1024x600
    Laptop - Win 7 - 1600x1200
    Laptop - MacOS - 1600x1200

    Can you try the following (when you have time :) )
    Play the game for 10-15 turns, quicksave, exit freemars, launch freemars, quickload & >repeat. :)

    You didn't asked to do this test from a new game, so I'll use my current game.
    The Blank Data Window bug occures now after 15 turns or so. This test may be a way to prevent it.

    BDW bug: Turn # 153, 177, 190, 204 & 219

    On the turn # 231, I felt the BDW bug was going to occure, the game was working very slowly (about 30 secondes before any reaction to the mouse-clicks). JAVAW.EXE file's RAM use: 305 808 Kb but only 0 to 3% of Processor Use.
    And the BDW bug actually occured.

    So I'm going now to continue my game from the savegame # 231 and try to do not forget you test ;o)

    BTW, my config is still Desktop - Win XP-SP3 - 1024x768x32 - HD free space 8 Gb. - Java 7 Standard Edition (v.1.7.0_25) (Activated)

    I noticed Java has settings (security: High, Environment securization: almost all the box are checked, Code's security check: activated, etc.). Can they be the source of the "bugs" in the game?

     
  • Billy Venus

    Billy Venus - 2014-05-27

    Let's go!

    Starting FM 0.856
    Continuing the current game (Turn # 231)
    ...
    TURN # 240: BDW bug (9 played turns only!)


    Screenshot:

     

    Last edit: Billy Venus 2014-05-28
  • Billy Venus

    Billy Venus - 2014-05-27

    QSaving...
    and I can't find the file... Where is it? in the FM usual Save directory? Is it a .FMS file?
    I can find the AutoSave file # 239, but not the QSave file (searched thru all the HD using the Date/Time filter. The biggest file crated/modified after the AutoSave file # 239 is only 100 Kb big).
    I moved the AutoSave files to an other directory, just to check the game's ability to find back the QuickSave file... if any...
    Quitting, Starting again, QLoading: Qload file not found
    Then I move the AutoSave files to their usual directory...
    Qload file not found again.
    Finally, I'm Continuing the test (
    Continue* from the AutoSave file # 239)...

    TURN # 249: BDW bug again (8 played turns only!)
    Nothing works better.
    QSave unsuccessful.
    I'm going to play 3 turns from the last AutoSave file (# 248) (I wish to synchronize the Shuttles arrival with the QSave/QLoad test... way of reminder ;) ) then I'll Continue the test and try to QSave after 6 turns only...

    TURN # 252:
    This time, the QLoad file was created (checked for it in the SaveGames directory).
    Quitting, Starting again, QLoading: It works...

    TURN # 259:
    Oups! I forgot to Qsave on the last turn.
    I prefered to rename the previous QLoad file before QSaving.
    Qsaving, Quitting,Starting,QLoading: Nothing to report... it works...

    TURN # 264:
    It's time to QSave, but...
    ... But the Colony Manager Window is behaving a strange way: It is repainted line by line only with the cursor moves, and the tabs (Production, Manufacturing, etc.) are repainted only after I click on their location. Only Growth was displayed on the window opening.
    I checked for the other Data Windows: they're all behaving normally (including Colony & Orbit/Earth windows).
    Back to the Colony Manager window: It's still behaving the same strange way.
    I guess the BDW bug is going to occure, butI'll never be sure.
    I rename the previous QLoad file.
    Qsaving, Quitting, Starting, QLoading: Nothing more to report...

    TURN # 264 "RELOADED":
    I checked for the Colony Manager Window behaviour: the bug is still there.


    Screenshots and Qload file in the archive:

     

    Last edit: Billy Venus 2014-05-28
  • Billy Venus

    Billy Venus - 2014-05-31

    A few of days later, I tried to continue the QSave / QLoad test, but the bug was still there.
    Obviously, it was saved with the current game, however I never could include the BDW bug in a savegame file.

    I tried to load the previous turn Autosavegame file, and the bug is there, too.

    I tried to load various Autosavegames, the bug occurs in the file # 251.

    Is this what you were expecting from this test?

     
  • Billy Venus

    Billy Venus - 2014-05-31

    Now, I'm going to take up the test from the turn # 250 (the turn before the bug)...
    Starting...
    Loading turn #250...

    TURN # 261:
    Oups! I forgot the test... What a tough work!
    Well, I erase the last savegame files and I take up the game from the turn # 250 without Quitting...
    Loading turn #250...

    TURN 251:
    Damn! The Blank Data Window bug occured however I had played only two turns in a row, but I played a dozen of turns and the BDW bug frequency is around 12 turns. This point is interesting: this bug occurs even when I load a game in the interval and seems to be saved in the savegame file.
    This time, I'm going to Quit the game before taking up the test.
    Quitting...
    Starting...
    Loading turn #250...

    TURN # 258:
    QuickSaving...
    Quitting...
    Starting...
    QuickLoading...

    TURN # 258 (QLoaded):
    The Colony Manager Window repaint bug occurs again.
    It seems it's the only result...

    The first available AUTOsavegame after the turn # 250 is the file #254 and the bug is already there.


    Now, I'm going to check for the Colony Manager window on every turn...
    Quitting...
    Starting...
    Loading turn # 250...

    TURN # 250:
    Checking for the Colony Manager window: O.K.

    TURN # 251:
    Bingo! The bug is there!


    Now, I'm going to check for the Colony Manager window after every action...
    Quitting...
    Starting...
    Loading turn # 250...

    TURN # 250:
    Checking for the Colony Manager window: O.K.
    Scout entering in an enemy Colony: The bug occured again!
    Quitting...
    Starting...
    Loading turn # 250...


    TURN # 250:
    Checking for the Colony Manager window: O.K.
    Scout... no move ordered. Colony Manager window: O.K.
    Transporters moved. Colony Manager: O.K.
    Engineers moved. Colony Manager: O.K.
    Shuttles: in transit.

    TURN # 251:
    Checking for the Colony Manager window: O.K.
    Scout entering in an enemy Colony: The bug occured again!

    Well! It seems the bug is caused by the Scout entering the ennemy Colony of Busan.
    Note: I already captured two other Colonies (chinese and russian) during this game. Both were populated, and the bug occures when I capture the third one... uninhabited (korean?).


    Here you have the savegame file to check for this bug:

     
  • arikande

    arikande - 2014-06-02

    thank you for this "excellent" test & analysis. :)

    I found the bug, it will be fixed in the next version.

    You painted the target with laser, all I had to do was to drop the guided bomb, thanks :)

     
  • Billy Venus

    Billy Venus - 2014-06-03

    My pleasure! ;)

     

Log in to post a comment.

MongoDB Logo MongoDB