Editing problems

[canuck64]

Had it in mind to tinker with the editor, and loaded up Gazala, and made a few unit changes to reflect varying (as I see them) changes needed for DF especially.
I understand from the Run5 site that a CTD when the editor loads an "incorrect" database is expected, and moreover, assumed to be the most effective way of ensuring uncorrupted scenarios.

I've unfortunately (due to that philosophy) wasted a few hours' time, and I'm not sure I follow the reasoning. I cannot load the scenario, can't use the editor to correct and nothing in the way of an explicit description of what might be the problem shows....

Can anyone expand on why this critical feature (the scenario editor) is so strangely setup? This pretty much precludes us creating scenarios until some workaround is created.

[JSS]

For other's benefit I re-iterate that the following thread (and its linked thread) should be reviewed before attempting to edit an existing scenario:

tm.asp?m=1377758

@ canuck64: Typically the crashing scenario events DON'T happen in the editor itself.  They happen when you attempt to play a fouled up scenario (usually this happens when you're early in the building a full battleset from scratch process).     Think you may be having a problem because it sounds like you saved updates to one of the stock scenarios... had some problems along this line with the final testing version (this maybe a no go, SSG will have to address).

[canuck64]

thanks JS, alas-I saw your post AFTER I had drawn up the editor and plowed away at a stock scenario..

So I'll second JSS' warning to read through his thread PRIOR to attempting to edit things.