Changing an estab in a scenario

[vandorenp]

Is the only time an estab can be assigned to a scenario is when creating a new scenario.?

Used an existing scenario to make a new one with the idea a new estab would be used. After editing the OB went to change the estab. Couldn't do it. Scenario maker manual cites setting estab only when starting a new scenario file.

[Arjuna]

Yes. The only way to change an estab for a force is within the ScenMaker and that can only open scenario files not saved game files.

[vandorenp]

ORIGINAL: Arjuna
The only way to change an estab for a force is within the ScenMaker and that can only open scenario files.

Of course I am not thinking of saved games. To be more precise I am believing that if I have an existing scenario with an estab already assigned I CAN NOT change the estab. (I have tried clicking on the estab name in the scenario hoping to prompt a way to change the estab like you can the map with no results]

The only chance to assign an estab is when creating a brand new scenario file. Correct?

[wodin]

I would expect you could change the scenarios est of current scenarios if you wanted to...sure I've read people doing it.

[parmenio]

I don't think you can change it using the Scenario Maker program. However, I did experiment with editing a scenario file (a copy of St. Vith tutorial) with a Hex Editor and changing the Estab filename that way. I took a copy of BFTBEstab.coe and renamed it BFTBEstb2.coe - I also copied the images folder and renamed it in the same fashion. It loaded up ok - I didn't test much further than that. Crucially as the .cos is a binary file, I think you should make sure your replacement filename has exactly the same number of characters as the original - otherwise YMMV.

[simovitch]

ORIGINAL: vandorenp

Is the only time an estab can be assigned to a scenario is when creating a new scenario.?

Used an existing scenario to make a new one with the idea a new estab would be used. After editing the OB went to change the estab. Couldn't do it. Scenario maker manual cites setting estab only when starting a new scenario file.

You should be able to drag and drop any estab into a force in the SM with a new or existing scenario. The stock scenario may be write protected, in which case you can Save As, or go to properties in explorer and unclick "read only".

[vandorenp]

Richard,
I believe you are referring to picking an estab for a unit like a platoon, company, Bn HQ, etc.
I am referring to setting the estab file for the whole scenario. Like on page 28 of the scenmaker guide, Start from Scratch.

[Merv0728]

You can also change the name by editing with Notepad,Wordpad or whatever.Open the .cos file & scroll to the bottom,there you will see the Estab name.Edit that making sure you use the same number of chars, (9).

Al

[parmenio]

ORIGINAL: Merv0728

You can also change the name by editing with Notepad,Wordpad or whatever.Open the .cos file & scroll to the bottom,there you will see the Estab name.Edit that making sure you use the same number of chars, (9).

Al

I'd be wary of using a text editor to edit a binary file. It's possible to inadvertently change it into a Unicode/Ascii/UTF-8 etc etc "text" file which will corrupt it.

[Merv0728]

Not if you keep your mind on what you're doing.

[parmenio]

ORIGINAL: Merv0728

Not if you keep your mind on what you're doing.

"The nice part about being a pessimist is that you are constantly being either proven right or pleasantly surprised"

[vandorenp]

ORIGINAL: Merv0728
Edit that making sure you use the same number of chars, (9).

Now i have to rename the file and folder I created already. Certainly a lot easier then creating a new scenario.

[wodin]

"The nice part about being a pessimist is that you are constantly being either proven right or pleasantly surprised"


something I've said myself to many a happy person...

A pessimist is never disappointed.

[vandorenp]

ORIGINAL: parmenio

ORIGINAL: Merv0728

You can also change the name by editing with Notepad,Wordpad or whatever.Open the .cos file & scroll to the bottom,there you will see the Estab name.Edit that making sure you use the same number of chars, (9).

Al

I'd be wary of using a text editor to edit a binary file. It's possible to inadvertently change it into a Unicode/Ascii/UTF-8 etc etc "text" file which will corrupt it.

Using a copy of the cos file I tried this. Does not seem to have worked. Not sure what being careful means. I found the estab file name twice in the file. Typed over the letters BFTB in both places. Then saved. Tried to open and received error "Can't open scenario file". How can one be even more careful?

[parmenio]

ORIGINAL: vandorenp

Using a copy of the cos file I tried this. Does not seem to have worked. Not sure what being careful means. I found the estab file name twice in the file. Typed over the letters BFTB in both places. Then saved. Tried to open and received error "Can't open scenario file". How can one be even more careful?

What did you change it to? In other words what is the name of your new Estab file? Is the number of letters in the name 9?

[vandorenp]

I changed it to KOADEstab. Best I can tell that is 9 characters exactly. [;)]

[parmenio]

Yep - 9 it is. [;)]

Then I'm guessing it must be down to one of the differences between the two Estabs - maybe referencing an object in BFTB that is not present in KOADE?

[vandorenp]

What about using http://www.chmaas.handshake.de/delphi/f ... /xvi32.htm ?

[Lieste]

I used UtraEdit to rename the Estab within a test scenario - there were IIRC three instances of the Estab name within the file, but I didn't pay any attention to where they were or what they related to...

The Estab in use is definitely the 'new' one so that seems to have worked.

[vandorenp]

Well I used it. Edited the last estab entry and left the previous untouched. It changed the effective estab in the scenario. But the estab cited on the scenario screen of the scenario maker kept the old name.