Big Problem with Small Map

[Prince of Eckmühl]

I've been trying to make a 20k x 20k map today, and I've run into a problem.

It's intended to have a base altitude of 170m with a 10m increase per altitude layer, and I set the map data up that way when I started it.

However, when I loaded into SM (after the map was completed in MM), I noticed that it was all fouled up, altitude wise, with a 180m increase in layer, instead of 10m.

I went back into MM to check, and the map data indicated that it was in fact set to 180m per layer.

So, I started from scratch, being very careful to set the map data parameters correctly, created the map and saved it.

Well, darned if the map didn't turn out to have the same issue when I loaded it to create a scenario.

I went back to MM to check on it once again, and observed the exact same problem as before:



Help![:(]

[Lieste]

The screenshot appears to just have an error in that dialogue.

The colours and height names look ok to the left.

Perhaps the MM is confused by the non-SL first interval and is reporting the absolute altitude of the first 10m contour above your base, rather than the interval between contours.

Try it with a 1m contour interval to test - I would expect to see 170m and 171m for the two dialogue heights.

[Prince of Eckmühl]

ORIGINAL: Lieste

The screenshot appears to just have an error in that dialogue.

The colours and height names look ok to the left.

Perhaps the MM is confused by the non-SL first interval and is reporting the absolute altitude of the first 10m contour above your base, rather than the interval between contours.

Try it with a 1m contour interval to test - I would expect to see 170m and 171m for the two dialogue heights.

Thanks for responding, Lieste.

The altitudes are fouled up, not only in MM, but in SM as well.

I went back and tried numerous other values in the Map Data fields, and the same thing is happening.

I've also tried tossing the map and starting over, but that doesn't resolve the issue.

MM is adding the value that I place in the second (bottom) field to the first (top) field and displaying the sum as the "Metres per altitude layer" value.

For example, if I key in these values:

[Prince of Eckmühl]

ORIGINAL: Prince of Eckmühl

ORIGINAL: Lieste

The screenshot appears to just have an error in that dialogue.

The colours and height names look ok to the left.

Perhaps the MM is confused by the non-SL first interval and is reporting the absolute altitude of the first 10m contour above your base, rather than the interval between contours.

Try it with a 1m contour interval to test - I would expect to see 170m and 171m for the two dialogue heights.

Thanks for responding, Lieste.

The altitudes are fouled up, not only in MM, but in SM as well.

I went back and tried numerous other values in the Map Data fields, and the same thing is happening.

I've also tried tossing the map and starting over, but that doesn't resolve the issue.

MM is adding the value that I place in the second (bottom) field to the first (top) field and displaying the sum as the "Metres per altitude layer" value.

For example, if I key in these values:

I get these results

[Vance]

Workaround:

• Open Map Data dialog
• Set, base altitude to 0,  increment 10
• Press Ok
• Reopen Map Data dialog
• Set base altitude to correct value
• Press Ok

That worked for me.

BTW, how do you determine heights in the SM.

[Prince of Eckmühl]

ORIGINAL: Vance

Workaround:

• Open Map Data dialog
• Set, base altitude to 0,  increment 10
• Press Ok
• Reopen Map Data dialog
• Set base altitude to correct value
• Press Ok

That worked for me.

Thanks, I'll give that a try.

BTW, how do you determine heights in the SM.

Right click on the map, and it'll display just like in-game.

[Prince of Eckmühl]

ORIGINAL: Vance

Workaround:

• Open Map Data dialog
• Set, base altitude to 0,  increment 10
• Press Ok
• Reopen Map Data dialog
• Set base altitude to correct value
• Press Ok

That worked for me.

Vance, your workaround worked. [8D]

Along the way, I discovered that I was only having the problem when I had the base altitude set to more than 0, whereupon everything else was hosed. In opening other maps, Sidi Rezegh, for instance, I found that the values were exhibiting the same behavior, its map having a base altitude of 50m. I'm pretty sure that I didn't overwrite any files with a bad one. I'll keep my fingers crossed.

Thanks again! [&o]

[Vance]

ORIGINAL: Prince of Eckmühl

ORIGINAL: Vance

BTW, how do you determine heights in the SM.

Right click on the map, and it'll display just like in-game.

Aha, turns out you have to have a unit on the map for that to work.

Along the way, I discovered that I was only having the problem when I had the base altitude set to more than 0, whereupon everything else was hosed. In opening other maps, Sidi Rezegh, for instance, I found that the values were exhibiting the same behavior, its map having a base altitude of 50m. I'm pretty sure that I didn't overwrite any files with a bad one. I'll keep my fingers crossed.

I have to admit that I also found strange behavior while changing the map in SM. One time I noticed that the current map had the layer increment of the previous used map. Then I remembered that the current map had no calculated terrain tables nor map cache. But with experimenting with the terrain tables and map cache, and my workaround, I managed to create a map that was correct in the SM in the end.

[Arjuna]

Thank you Vance for the workaround. I will look into this but that will have to wait as I am knee deep in AI code for BFTB at the moment.
 
TT3752 - MM - Ensure Altitude Layer Interval set correctly when a non zero base latitude is set