Matrix Games Forums

The best solution would be to let the scenario designer designate climate zones north to south and east to west.

Editor on the Left, In-Game on the Right. So it's doing something different ... very TOAW-ish [:)]

EDIT: To clarify - Editor on the Left [with no scenario open, like when creating a new scenario]; On the Right is with a scenario open.

ORIGINAL: sPzAbt653
Editor on the Left, In-Game on the Right. So it's doing something different ... very TOAW-ish [:)]

[&:]

[:(]

ORIGINAL: 76mm

ORIGINAL: sPzAbt653
Editor on the Left, In-Game on the Right. So it's doing something different ... very TOAW-ish [:)]

[&:]

[:(]

There's one thing positive I can say for TOAW in its present state. I've been loking at boardgames again.

ORIGINAL: jmlima
There's one thing positive I can say for TOAW in its present state. I've been loking at boardgames again.

[:D] I'm not there yet...at least for operational level games.

I am, however, tired of waiting for WWII tactical games that I like, so have gone back to ASL for the first time in 35 years. This is what progress looks like?

Set environment is only available in the editor. [&:]

Based on hex scale, in the scen editor for the latest version, the zones appear to exist for 700 hexes (one climate zone) for 0.25-km hexes, then drop to 234 hexes (and three climate zones) for any hex scale 2.5-km and higher. This is for a 700 hex by 700 hex map.

Cheers

Because it isn't based on how many hexes rather on how many kilometers.

ORIGINAL: Lobster
Because it isn't based on how many hexes rather on how many kilometers.

But if it is really the same number of hexes for any hex scale at or above 2.5 km, it doesn't really appear to be based on km...

He said on a 700x700 hex map.
x axis is constant. distances are y axis only

1 climate zone <900 km
2 climate zones =>900 km to <1500 km
3 climate zones =>1500 km

Lobster,

The scenario editor interface doesn't indicate such. It shows one zone for a given range of hex scales, and then goes to three climate zones at a selected point in the hex scales ... but the number of hexes in the zone(s) is of course constant, per the selected map scale.

How it actually works in a running game, I don't know. But the scenario editor isn't depicting any way to have only two climate zones. It seems to be either a single zone or three zones.

For a map of 350 vertical hexes, there is a single zone for scales up to 2.5-km per hex. At 5 kilometers per hex, it goes to three climate zones. At 200 kilometers per hex, a single weather zone spans 23,400 kilometers. At 5 kilometers per hex, the a single zone spans 585 kilometers. Or so the editor indicates?

Cheers

ORIGINAL: cathar1244
But the scenario editor isn't depicting any way to have only two climate zones. It seems to be either a single zone or three zones.

That is a result of the interplay between the size of the map (700x700) and the map scales. Create a 20x20 map, for instance, and you'll see two weather zones at the 50 km scale (20 x 50 km = 1000 km); below that scale, only one zone (20 x 25 km = 500 km), and above it, three zones (20 x 100 km - 2000 km).

Weather zones seem to be tied to the size of the MAP in kilometers--not the size of the hex or the size of the weather zone itself.

Weather zones seem to be tied to the size of the MAP in kilometers--not the size of the hex or the size of the weather zone itself.

Thanks. That seems to be the key. And possibly hard to summarize in a manual.

A side effect of this is one could define a map with a lot of vertical depth but only use one third of that vertical depth, with the rest of the hexes marked unplayable. Should allow a single weather zone to be forced in the case of some map sizes. I wonder what odd behavior that might induce. &#128053;

Cheers

ORIGINAL: cathar1244

Weather zones seem to be tied to the size of the MAP in kilometers--not the size of the hex or the size of the weather zone itself.

Thanks. That seems to be the key. And possibly hard to summarize in a manual.

A side effect of this is one could define a map with a lot of vertical depth but only use one third of that vertical depth, with the rest of the hexes marked unplayable. Should allow a single weather zone to be forced in the case of some map sizes. I wonder what odd behavior that might induce. &#128053;

Cheers

An equatorial climate will negate weather zones. Strangely enough, you can assign any weather to an equatorial zone including frozen.

ORIGINAL: Lobster

ORIGINAL: cathar1244

Weather zones seem to be tied to the size of the MAP in kilometers--not the size of the hex or the size of the weather zone itself.

Thanks. That seems to be the key. And possibly hard to summarize in a manual.

A side effect of this is one could define a map with a lot of vertical depth but only use one third of that vertical depth, with the rest of the hexes marked unplayable. Should allow a single weather zone to be forced in the case of some map sizes. I wonder what odd behavior that might induce. &#128053;

Cheers

An equatorial climate will negate weather zones. Strangely enough, you can assign any weather to an equatorial zone including frozen.

That's climate change for you.

That makes sense to me. Perhaps the Civilian Manual should read:

17.7.1. Weather Zones (Northern or Southern Climate Areas)
The size of a Weather Zone is determined by the size of the Map in Kilometers and the Map Scale.

P.S. the Civilian Manual is text only, no charts or tables.

It might be more clear if we just fix the numbers in the existing version of 17.7.1, which talks about the number of Weather Zones--we just have to fix the numbers to read 0-899, 900-1499, and >=1500. We can add your sentence about the size of the Weather Zones for good measure.

we just have to fix the numbers to read 0-899, 900-1499, and >=1500

But that's an example of one map scale and map size, right? So it would then read 'in this case' or 'for example'. What are the parameters to get those numbers?

ORIGINAL: sPzAbt653
But that's an example of one map scale and map size, right? So it would then read 'in this case' or 'for example'. What are the parameters to get those numbers?

No--whatever the hex scale and map size, those are the number of weather zones if the map ends up being within those size ranges (y-scale).

I've posted screen shots of five separate configurations and none of them equal 900km per zone, so why am I confused?