|
canuck64 -> Editing problems (2/20/2007 4:37:53 AM)
|
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.
|
|
|
|
