Who uses "mountainizer"?
Posted: Sun Aug 18, 2002 7:30 am
Gentlemen,
I was wondering if anyone uses Mountainizer, and if you do, what are, in your opinion, the "pros" and "cons" of using the program.
Here's my initial opinion. It is a neat program, because it gives us more "levels" and it allows a map/scenario designer to accurately reproduce lines of sight. However, at this point, the "cons" are outweighing the "pros". Here are several "cons" that will probably prevent me from using it in my next map, which, by the way, ranges in elevation from the Rhine River up to about 70 meters. It would be cool to show the correct elevations (which I can still do with WAWMAP, but I'll have to input the elevation of each hex, and it won't show slope), but:
1. Once you get the correct elevations and you make a mistake while laying down terrain, and have to erase, you do major damage to your elevation. For example, you want to change the path of a road that passes through a slope hex with an elevation of 60 meters. You can't clear the hex, or you are back at 0. You can't click on a level three hill, because you'll now have 30 meters, plus your slope disappears! In order to get that one hax back to 60 meters (you'll still have a visual elevation difference, though, you could do two things: edit the elevation in WAWMAP,along with all of the other screw ups, most of which you won't find, or go back into Mountainizer, which will get that hex back to 6o, and everything else, including your River and hexes whose elevations you are happy with, will increase 30! So, if you can make a whole map without making any changes, you are OK.
2. Any part of your map above 30 meters will be dark brown in your strategic map, depriving you of the ability to look at the disposition of your units in relation to high ground, etc. (Maybe not such a big problem, unless you are the map designer and you've got to listen to the complaints of those who rely on the strategic map.)
I'd like to hear the comments of others. Maybe there are solutions to some of the barriers to using this program, and I've just not found them yet. I know that there are some who swear by this program. Maybe their comments can restore my confidence in its use.
Regards,
David Boutwell
"Out of ammunition. God save the King."
I was wondering if anyone uses Mountainizer, and if you do, what are, in your opinion, the "pros" and "cons" of using the program.
Here's my initial opinion. It is a neat program, because it gives us more "levels" and it allows a map/scenario designer to accurately reproduce lines of sight. However, at this point, the "cons" are outweighing the "pros". Here are several "cons" that will probably prevent me from using it in my next map, which, by the way, ranges in elevation from the Rhine River up to about 70 meters. It would be cool to show the correct elevations (which I can still do with WAWMAP, but I'll have to input the elevation of each hex, and it won't show slope), but:
1. Once you get the correct elevations and you make a mistake while laying down terrain, and have to erase, you do major damage to your elevation. For example, you want to change the path of a road that passes through a slope hex with an elevation of 60 meters. You can't clear the hex, or you are back at 0. You can't click on a level three hill, because you'll now have 30 meters, plus your slope disappears! In order to get that one hax back to 60 meters (you'll still have a visual elevation difference, though, you could do two things: edit the elevation in WAWMAP,along with all of the other screw ups, most of which you won't find, or go back into Mountainizer, which will get that hex back to 6o, and everything else, including your River and hexes whose elevations you are happy with, will increase 30! So, if you can make a whole map without making any changes, you are OK.
2. Any part of your map above 30 meters will be dark brown in your strategic map, depriving you of the ability to look at the disposition of your units in relation to high ground, etc. (Maybe not such a big problem, unless you are the map designer and you've got to listen to the complaints of those who rely on the strategic map.)
I'd like to hear the comments of others. Maybe there are solutions to some of the barriers to using this program, and I've just not found them yet. I know that there are some who swear by this program. Maybe their comments can restore my confidence in its use.
Regards,
David Boutwell
"Out of ammunition. God save the King."
Cause of this some issues are to be expected when "mountanizing" and editing mountanized maps, but most can be worked around! (see my Ardennes44 and After Cassino44 scenarios for good results)
;)
