PDA

View Full Version : Terrain breaching question



Pat Proctor
15 Feb 04, 16:22
Gentlemen,

We are hard at work on Raging Tiger and the v 1.04 patch, but we have come to a decision point where we would like a little user input.

We have fixed terrain breaching (which is currently broke in ATF, but not really a factor in any of the stock scenarios). We plan on including this fix in both RT and v 1.04. Here is the issue.

Right now, in ATF, saved games do not save terrain breaches. We can fix this, but it will break all of your current saved games. Here are the options:

1. Add saving of terrain breaches to v 1.04
Upsides: a) If scenarios are created that incorporate terrain breaching, these breaches will be saved when you save the game.
b) your saved games (saved under v 1.04) will be compatible with and loadable in Raging Tiger.
Downside: All of your current saved games will not run on v 1.04.

2. Do not add terrain breach saving to v 1.04 of ATF
Upside: Your saved games will not break with v 1.04 of ATF
Downside: In any scenarios that incorporate terrain breaching in the future, if you save after breaching terrain, your breaches will be lost when you restart the scenario later.

Please let us know by voting in the poll.

Ivan Rapkinov
15 Feb 04, 19:14
I voted for adding it - if it's going to be added at some point, I'd rather have it now than later.

cbelva
15 Feb 04, 21:29
Definitely add it.

Scully
15 Feb 04, 22:58
I'd say add it as well. I'm looking forward to both 1.04 and Raging Tiger.

Philip
15 Feb 04, 23:19
If it just causes a problem with saved games rather than scenarios created then I would definitely go for it

kbluck
15 Feb 04, 23:39
There is a third option --- hold off on the terrain breaching until Raging Tiger. But, I'm guessing you're not maintaining separate sourcebases, so probably that isn't a realistic option. Hey, I bet if we poke around in 1.04, we'll probably find a few other features intended for Raging Tiger...

:devil:

A fourth option --- an "updater" utility that can load a 1.03 savegame and then save it right back out in 1.04 format.

At any rate, this question is really pretty much a non-starter. People are going to go nuts if they save a game and find the game isn't left in the same state when they reload. You're essentially breaking a contract with them. On the other hand, people are fairly accustomed (sadly) to old stuff breaking after an upgrade, so the outrage will likely be much more muted, especially if you give fair warning in the upgrade process.

Besides, I think you broke savegames at least once before. Maybe I was doing something wrong, but I couldn't reload 1.01 savegames after upgrading to 1.02. My world didn't come to an end.

--- Kevin

Pat Proctor
16 Feb 04, 00:13
There is a third option --- hold off on the terrain breaching until Raging Tiger. But, I'm guessing you're not maintaining separate sourcebases, so probably that isn't a realistic option. Hey, I bet if we poke around in 1.04, we'll probably find a few other features intended for Raging Tiger...

Sorry to disappoint you, but...no.

The general concensus, accross several forums, seems to be to add the save feature. Stay tuned. I will be offering a sneak preview playtest in a little while...