Reading Event Dumps?

[76mm]

I thought I would read some scenario and event dumps of complicated scenarios to see how the pros do events, but:
1) The scenario dump for Directive 21 is more than 3,000 pages long--yikes!
2) I tried doing the event dump (via F6 key) instead, but the resulting file is totally unformatted and unreadable (no line breaks, etc.). I tried opening it in Word to format it a bit, but it would not open. Anybody have any tips on how to make these event dumps readable?

I know I could try a simpler scenario, but the whole point is that I want to see some of the more creative/complicated uses of events.

[sPzAbt653]

Hi Tom - I cover the scenario dump here at the very beginning of the video: https://www.youtube.com/watch?v=hiRaL0s9sgg

But to answer your question directly, when you save the dump you must add the .txt extension.

[sPzAbt653]

Designing scenarios, everybody has their own way of doing things. Events can be difficult to keep track of and I like to keep a txt file of them, an example is attached below. If you look at this, it won't mean anything to you, and is probably just confusing. But the point is to keep everything straight, and I think if you don't keep a written record of events and structures, it makes it very difficult to do. I find it best to start this record before you even start entering events into the editor. With each scenario you do you will get better at it [:)]

[Oberst_Klink]

ORIGINAL: 76mm

I thought I would read some scenario and event dumps of complicated scenarios to see how the pros do events, but:
1) The scenario dump for Directive 21 is more than 3,000 pages long--yikes!
2) I tried doing the event dump (via F6 key) instead, but the resulting file is totally unformatted and unreadable (no line breaks, etc.). I tried opening it in Word to format it a bit, but it would not open. Anybody have any tips on how to make these event dumps readable?

I know I could try a simpler scenario, but the whole point is that I want to see some of the more creative/complicated uses of events.

Two options:

1) Rename the file extension to .xml, use Notepad++ to open/review.
2) Use Adndy's scenario viewer in order to see a proper list of events (works for the 3.4 version).

Klink, Oberst

[76mm]

Hi, i should have specified that i remamed the file with a txt extension and could open it with Notepad, but it was totally unformatted and unreadable—no lne breaks, etc. When i tried to open it in Word, i got an error message—something about an invalid character.

But Herr Oberst’s XML idea looks great, will try that as soon as i get a chsnce.

Steve, your file is also very helpful—the mabual refers to text file that can be imported unto the Event Editor—is your file an example of such files? Looks awfully “plain texty”.

[sPzAbt653]

it was totally unformatted and unreadable—

Doing something wrong there! I did these steps and it worked fine:

1. Dump Scenario as
2. [Opens to a save dialogue that is pointing to the scenario folder]
3. Click on Scenario name
4. Scenario Name.sce now appears in the Save As field
5. Remove sce and replace with txt
6. Save to Desktop for easy finding

[sPzAbt653]

text file that can be imported unto the Event Editor

OOB's and Event Lists can be imported and exported in xml format. See the Key Command list for F4 thru F8, I think.