Page 1 of 1

Version 1.0.1 Scenario Editor Problems

Posted: Thu Feb 24, 2005 12:27 pm
by CapnDarwin
I have two bugs when trying to use either of the scenario editors. If I hit the Ad-Hoc button I get dumped into the full editor. Second, if I make a scenario with the full editor and save it, it will not load when I choose it from the scenario menu and I need to kill the game from task manager.

Can anyone else confirm these issues with 1.0.1? It is making checks of my mods impossible at this time.

Thanks.

S!

Cap'n D

RE: Version 1.0.1 Scenario Editor Problems

Posted: Thu Feb 24, 2005 5:33 pm
by David Clark
I can confirm the Ad-hoc error - from a clean install of 1.00 and 1.01 on top of it, pressing the Ad-hoc editor button puts me into the full editor.

Attempting to save any scenario from the full editor results in two Access Violation errors. I loaded the Tutorial scenario from full editor, changed the Starting Date from May 7th to May 5th, and saved under a different name. The result was the two error messages above, although the altered scenario loaded fine for me. To repeat, I got errors when saving the scenario, not when loading it.

Hope this helps.

RE: Version 1.0.1 Scenario Editor Problems

Posted: Thu Feb 24, 2005 7:37 pm
by Erik Rutins
Thanks for the reports, we'll include this in our next update as a priority fix.

Regards,

- Erik

RE: Version 1.0.1 Scenario Editor Problems

Posted: Thu Feb 24, 2005 8:42 pm
by CapnDarwin
Erik,

Thanks for the thread move.

I have some other info on this scenario bug. In most cases the exe keeps eating more and more memory and needs to be killed from Task Manager. The other cases (see attached error report) when I hit Procede all of my core memory (1.7Gb's) gets tapped and the game require external killing.

I hope this gets fixed in 1.0.2.

S!

Cap'n D

RE: Version 1.0.1 Scenario Editor Problems

Posted: Wed Mar 09, 2005 4:05 am
by IronManBeta
Thanks Capn, that first problem was fixed in 2 minutes. The 2nd is not reproducable yet but I had changed a lot of things already since 1.01 and that may have impacted it before I had a chance to look at it. Loading the file you provided worked fine in 1.02 anyway.

More later, Rob.