Matrix Games Forums

Hi,

Perhaps I have something overlooked but memap is a good program for making maps but its not easy to work with without a background image or export for comparing with the background image.

Is there a way of working with a background image or export?

Harry

Hello Harry,

Not with Map Editor, now. What I do instead I create a map of the size I want, turn hex grid on, turn hex co-ordinates on, then take a screen print of that and paste that on top of Google Earth as a layer. Then, based on that, you can observe what each hex should have. Not quite what you're asking, but a nice technique nevertheless.

Huib Versloot wrote a really nice document about that, but the section of the Blitz where it was stored seem to be no more. [:(]

I'll see if I have a copy of it somewhere....

Ha! Found it [:)] Thank gawd for Google Mail, everything is saved even from years ago.

Mapping doc attached to my post, HERE.

Thanks for the fast response.

For now I do made with hexdraw a background grid and Starting Column=-1 & Row=-1 and Hexnumbers=ON. On my second monitor.

Interesting way of making a overlay.

This is a transparent 40x40 map.

A question left.

Is 250m the hight or width of a hex?

Sorry, logged off a while ago, on my cell phone now.

Not sure I understood you, but a hex is 250x250, and elevation is as you set it as the Delta value in map editor.

If for example a map is 40x40 hexes then the map is not square but the hight is more then the width.

If the hight of one hex represents 250m then the width represent less then 250m.

ORIGINAL: harry_vdk

If for example a map is 40x40 hexes then the map is not square but the hight is more then the width.

If the hight of one hex represents 250m then the width represent less then 250m.

OK I see what you mean. Got this picture from Jason explaining why a hex grid is not a perfect square, for in the X axis there's an overlap while in Y axis there's none. So yes, a hex is 250m each side, but due to hexagons they don't create a square.

Thanks, Petri!

Now that I see this on my laptop and not on my cell phone this actually makes sense now [8D]

Thanks for the clear explanation.

This was the way I was thinking but the document was talking about a horizontal measurement and that was unexpected.

Good catch harry, should be measured using Y axis instead