Omaha Beach - Scen #9

[dTerm]

Originally Posted by DRG

I suspect some will feel uncomfortable pressing END GAME without saving but doing that creates an autosave.

As the testing I posted showed it can take a LONG time for this to happen in some cases and it wasn't until Don sent me his tests that I saw it this time though and then I hit my test buildings with arty harder and saw it but in his test not nearly as much arty as I used managed to make a few go away.

I suspect a lot of players may not even notice it especially ones that might play out a turn or two per sitting because their save restores the building but in the case of the END GAME procedure, autosave takes a snapshot of that point the END GAME button is pressed so starting the autosave takes you to the exact point you were when you pressed it and the buildings are restored

The message for the End game button is "End the Game and EXIT" at the top of the screen
Then you see at the bottom of the screen "Do you really want to end the game Y/N "

I may change the first message to something like

"End the Game, autosave and EXIT"

or

"End the game and Exit (The game will be saved in the Auto-Saved game slot)

Final result ( both games )

While testing the fixed binary (which appears to consistently solve the junk terrain issues on my machine btw. ) I observed, that in single-player and hotseat games it's not the red END TURN button that creates the autosave, but the START TURN button on the Start Turn Screen, when you continue playing.

Can anyone confirm this, or am I missing something here?

[DRG]

Well this is weird. Will need to investigate further. I thought for certain that it was saving at the point the red up arrow was pressed

[DRG]

OK......

1/ I started a simple game, moved a unit then pressed the red up arrow then went to the auto-save slot and started it and that game was back to where I was before I moved the unit

2/ I started an old save game, move a unit then presses the red up arrow and started it and that game was back to where I was before I moved the unit

3/ I started a different old save game.... lets call it #3, I moved a unit then pressed the red up arrow button then went to the save game screen and started the autosave and it was old save game #3....... BEFORE I moved the unit


SO it would APPEAR your observation is correct. The autosave is being made when the game ( originally ) loads.

OK.... learned something new today........

We will look into this and get the procedure strainghend out and the working adjusted for the next release

That does explain why the building were restored when loading the autosave though........

[dTerm]

Originally Posted by DRG

[...]

That does explain why the building were restored when loading the autosave though........

But from what I observed, it doesn't make any practical difference regarding this issue. It works nonetheless.

I just wanted to let you know, because of the wording for the END TURN message you changed.

[dTerm]

Ah, ok, after reading you post again, I realized, that's what you mean.

[DRG]

..........This has been a l o n g journey

[DRG]

FWIW......

I just tried a new test with the "Vanish" game that had been posted

I hammered the buildings until one disappeared then saved normally.

When I restarted, the multi-hex building that had only shown rubble had been restored. ( WITH THE RUBBLE....which is as it should be )

Anyone interested can try that and report that they see the same thing.

EDIT

This was done with MBT but the test I ran with SPWW2 did the same

This is after the multi hex building had been hammered by arty and disappeared


I then saved the game in a regular save slot then restarted



The building returns on restarting the save

[DRG]

If anyone sees a building disapear check the registration hex ( typically the upper left hex of the series it had been in ) BEFORE it is saved and let me know if hovering the cursor over that hex shows it to be rough and after you save and restart does it show "paved"

The theory I am exploring now is if the registration hex is turned to rough that is when the building disappears.

After saving and restarting the building will be restored but report the hex under the registration hex is Paved

IF you build a map and place a multi over a rough hex the registration hex ( and some others usually ) will report "paved" and I think that change to rough during as bombardment might be the key to why they disappear

SO FAR I have not found a multi that shows rough under the registration hex

[DRG]

One step closer to solving this

This is a test map after bombardment. Note even though this is a lot of rubble the buildings still show






This is a test map after I placed rough on every multi hex building registration hex





It would appear if rough is created in the registration hex of a building (any building ) during a bombardment the building will disappear but re-appear after the save is restarted because the process of saving and restarting removes the temporary rough hex that was created

That's the working theory ATM

[DRG]

8 buildings placed



8 buildings with rough put into the registration hex