01-06-2015, 08:06 AM,
|
|
Scenario Editor Header Dialog Error
Hello Gents:
Mr. Dan here...stumped as usual...trying to create a new scenario (from scratch) for the first time since the new version and I keep getting "INVALID FORMAT" when I attempt to create the new .scn file. Got the map, got the OOB, etc., but when I get to the Scenario HEADER Dialog (trying to create the new .scn file) no matter what information I input I get "INVALID FORMAT".
I've gone through my old paper manual and the new pdf version but neither mention this issue.
I know you smart guys out there have probably already seen and conquered this issue...assuming it is not something I am doing incorrectly???
Regards,
Dan...
|
|
01-06-2015, 08:20 AM,
|
|
Warhorse
Moderator
|
Posts: 2,332
Joined: Jun 2001
|
|
RE: Scenario Editor Header Dialog Error
Hi Dan,
I haven't had time to delve into any scenario design lately, but this is due to the new format that you can set day/night/visibility per turn, or whatever you like. If you open one of the EF Odessa scenario's, you will see what the deal is now. Pay attention to spacing and all! I know there is a write-up on this, and it should be better marked, because I need to read it as well! Jason knows better, Jason?
|
|
01-06-2015, 10:38 AM,
(This post was last modified: 01-06-2015, 10:40 AM by Jason Petho.)
|
|
RE: Scenario Editor Header Dialog Error
From the manual Page 91:
Quote:Dynamic Visibility:
Scenario designers can now set the preferred visibility on a per turn or by a series of turns. This is achieved by noting the turn sequence followed by the visibility. In the following example scenarios that is 10 turns long, turns 1-5 will have a visibility of 3, while turns 6-10 will have a visibility of 5.
1-5[3] 6-10[5]
NOTE: The space is important between the two sets of values. Otherwise no spaces (none within each value set)
There is no limit to the number of visibility changes the designer can set for the scenario.
Dynamic Day/Night:
Scenario designers can now set the preferred day or night on a per turn or by a series of turns. This is achieved by noting the turn sequence followed by the visibility. In the following example scenarios that is 10 turns long, turns 1-30 will have a day setting, while turns 31-50 will have a night setting.
1-30[d] 31-50[n]
NOTE: The space is important between the two sets of values. Otherwise no spaces (none within each value set)
You can have as many days and nights as you wish. It is important that the number of turns in both the visibility setting and day/night settings are the same.
Hope this helps
Jason Petho
|
|
01-07-2015, 08:09 AM,
|
|
RE: Scenario Editor Header Dialog Error
Thanks guys.
As usual...spot on with help.
I'll get right on this.
This one is a day only scenario, 32 turns, visibility 13 hexes, so I believe the values should read: 1-32[13]. Or, if I were to mix it up, break it up with a space and a new set of values, etc.
Very excited about this new scenario. It's a small one. Time to reach out to the other half and try to concoct a compact but potent brew. Running armored fight through the Western Carpathian Mountains, late war.
Regards,
Dan
|
|
01-08-2015, 10:58 AM,
|
|
RE: Scenario Editor Header Dialog Error
(01-07-2015, 08:09 AM)Dan Caviness Wrote: This one is a day only scenario, 32 turns, visibility 13 hexes, so I believe the values should read: 1-32[13]. Or, if I were to mix it up, break it up with a space and a new set of values, etc.
Yes, that is correct.
and
1-32[d]
in the day/night field.
Jason Petho
|
|
|