Matrix Games Forums

TOAW Scenario Viewer Homepage

Two big changes.

You no longer need to dump files out of the editor; the viewer can now read SCE files directly (thanks to Ralph for helping out with that one).

New event nodes. These are an attempt by me to understand and represent how events work. There will almost certainly be problems with these - particularly in the area of Theater Options. Hats off to the scenario designers for being able to understand events - after a month I'm still not sure if I've got it down pat.

Details of the release below. Please read the notes and limitations sections on the website for more information.

2.0.0.0: 24th October 2009. Change release.

Change: Now reads .SCE files directly (no need to dump the scenario first).
Change: New event nodes show event chains by trigger and by turn.
Change: New popups will give details on activated events/ available theater options etc.
Change: New popups will give details on formations/units activated by events.
Change: New unit type nodes show all formation/units categorised by type.
Change: File load supports multiple types (TXT, SCE, XML).
Change: Popup dialog size now calculated based on content.
Change: Popups may be closed with ESC or ENTER key.
Change: Popups automatically close after 5 minutes.

Good job Parm 

There's an issue with scenario files that use a modified equipment database - the standard equipment type names are returned instead of the modified ones. Works OK with a .TXT + .OOB combination. As soon as I've got a fix, I'll post an update.

ORIGINAL: parmenio

There's an issue with scenario files that use a modified equipment database - the standard equipment type names are returned instead of the modified ones. Works OK with a .TXT + .OOB combination. As soon as I've got a fix, I'll post an update.

That's only a minor inconvenience, we'll just save a dump
Great job [&o]

Maybe eventually there'll be a version that tracks changes in the scenario as you play. [;)][:D]

ORIGINAL: desert

Maybe eventually there'll be a version that tracks changes in the scenario as you play. [;)][:D]

... so you can look at a glance which of you units are using this-or-that piece of equipment

I have a partial fix for the modified equipment database issue. When updating equipment type names, since the scenario XML only contains the equipment names, I cannot distinguish between "Spare Equipment" in ITEM_1928 and "Spare Equipment" in ITEM_1929.

If any standard slots are modified, there shouldn't be a problem but anything past T-64A is all going to be lumped together and I don't think I can work around that.

2.0.1.0: 26th October 2009. Bug fix/Change release.

Fix: Now reads equipment databases to attempt to show correct equipment names.
Fix: All non-displayable characters are now replaced.
Fix: Now checks for invalid event id in deployment nodes.
Change: Outcome nodes combined into one (meant to do this before).

Homepage

Somewhat quicker than expected...

....yet another patch. The second fix being the serious issue.

2.0.2.0: 27th October 2009. Bug fix release.

Fix: Now checks standard equipment database exists before opening it.
Fix: The use of the '#' character for hyperlinks replaced with '|'.
(because '#' is used in XML files you muppet).

Homepage

2.1.0.0: 1st November 2009. Bug fix/Change release.


Fix: Custom equipment databases now used.
Fix: Invalid Unit Ids in Events no longer cause exceptions.
Change: Equipment database used added to Scenario information.
Change: Equipment file name stored for use with XML copies of the scenario.
Change: Where units are deployed by an event this is now clearer.

Homepage

2.1.1.0: 2nd November 2009. Bug fix/Change release.

Fix: More exceptions caused by invalid events now handled.
Fix: "Nuke" event effect now handled correctly.
Change: If "GetEquipmentFileName" returns empty default to standard equipment file

Homepage

2.2.0.0: 10th November 2009. Change release.
Change: Supply Points node added.
Change: Replacements node for each force added.
Change(internal): Consistent use of StringBuilder for speed.
Change(internal): Viewer is now a UserControl.

Homepage

That's probably going to be it as far as updates go for a while (aside from bug fixes) . Tomorrow AM I'll be releasing a new Equipment Editor (all being well) and then I plan to start work on a Scenario Editor - starting with being able to edit OOBs.

Is this combatible with Win 7 ?
I get a windows error message even running in XP or Vista compability modus.

ORIGINAL: Erik Nygaard

Is this combatible with Win 7 ?
I get a windows error message even running in XP or Vista compability modus.

As I state on the website, the Viewer and the Equipment Editor have only been tested against Windows XP SP3. What's the error message? Are you running Windows 7 32-bit or 64-bit?

ORIGINAL: parmenio

ORIGINAL: Erik Nygaard

Is this combatible with Win 7 ?
I get a windows error message even running in XP or Vista compability modus.

As I state on the website, the Viewer and the Equipment Editor have only been tested against Windows XP SP3. What's the error message? Are you running Windows 7 32-bit or 64-bit?

The error message is not specific, it only states that windows is looking for an error..
Win 7 64 bit

ORIGINAL: Erik Nygaard
The error message is not specific, it only states that windows is looking for an error..
Win 7 64 bit

There's probably an error in the Application section of the Event Viewer that may shed some light on the problem.