CM scenario creation kaput

[perrya]

The game works fine. When trying to create a scenario, what are the steps? what does one create first and so on ? also, after I enter the parameters data and press OK button, the screen does nothing, it does not return to the menu, thus, I have to reboot! stupid! When I type a brief desc. of the scenario, when I press P I get K. Any suggestions to clean up this?

[Schrullenhaft]

There is no set order that you have to go through to create a scenario. The default creation type is a battle (you'll have to click on New Operation to change the type). When you're at the Scenario Editor screen you can click on buttons like Parameters (which I would suggest first since it can affect unit selection and some of the map characteristics). You can go through the rest of the buttons like Unit and Map at any time. Load Briefings requires that you have the Briefings written up and saved beforehand (three separate files). Some of the details of scenario/op creation start on page 108 of the manual (page no. based on first release of manual). Remember to save your scenario !

To get out of the Scenario Editor click the Exit button in the lower right and that should bring you back to the main splash screen.

[perrya]

Ian, after the params are entered and OK is pressed, nothing happens. There is no going back to the scenario screen. There is no exit button you note. In fact, my screen looks exactly like the one in the book, pg 113 (which does not show any exit button).

Perry <BLOCKQUOTE>quote:</font><HR>Originally posted by Schrullenhaft:

There is no set order that you have to go through to create a scenario. The default creation type is a battle (you'll have to click on New Operation to change the type). When you're at the Scenario Editor screen you can click on buttons like Parameters (which I would suggest first since it can affect unit selection and some of the map characteristics). You can go through the rest of the buttons like Unit and Map at any time. Load Briefings requires that you have the Briefings written up and saved beforehand (three separate files). Some of the details of scenario/op creation start on page 108 of the manual (page no. based on first release of manual). Remember to save your scenario !

To get out of the Scenario Editor click the Exit button in the lower right and that should bring you back to the main splash screen.<HR></BLOCKQUOTE>

[Schrullenhaft]

What version of CM are you running ? If you're running one of the BETAs (16 or 22) there may be an error log being generated. The BETAs will trip up A LOT more easily than the standard releases. It may be just a small issue (that is understandably annoying) that may disappear once the full 1.1 patch is released. Check your CMBO directory for any ERRORLOG.TXT files (I believe that's the name).

If you're playing 1.05, then I'm at a bit of a loss as to why this would be happening. Do you have any other problems with CM crashing or hanging ?

[perrya]

I am running 1.5, and have no problems except for creating a scenario, which chokes.

Perry

<BLOCKQUOTE>quote:</font><HR>Originally posted by Schrullenhaft:

What version of CM are you running ? If you're running one of the BETAs (16 or 22) there may be an error log being generated. The BETAs will trip up A LOT more easily than the standard releases. It may be just a small issue (that is understandably annoying) that may disappear once the full 1.1 patch is released. Check your CMBO directory for any ERRORLOG.TXT files (I believe that's the name).

If you're playing 1.05, then I'm at a bit of a loss as to why this would be happening. Do you have any other problems with CM crashing or hanging ?<HR></BLOCKQUOTE>

[Schrullenhaft]

You may want to delete your 1.05 executable and the prefs file (though the prefs file should make almost no difference from what I could tell). Run Scandisk on your system to check for any possible problems with the file system and re-download and extract the 1.05 patch.

I'm not aware of anyone else here reporting the problem that you're seeing. If you have no other problems with lockups in CM or other applications, then I would guess that there is something corrupt with your CM executable (which the above suggestion should address).