Overview Height
 

How is the "Height" setting of an overview.txt determined ?
I'm working on one, but don't know how this 3 is found.
Cheers !

Re: Overview Height
 

???

Most likely it is made when you use Botman's BSP Slicer automatically. In fact, I think you can decide what height you use in the slicer.

Re: Overview Height
 

It's the zmax value displayed in the console once you have zoomed/scrolled your overview to the ideal perspective.

In the overview.txt, the third number in the line "ORIGIN" must be the same as the number behind "HEIGHT".

So if you have a line like this:

ORIGIN 453 -226 -514

the HEIGHT would be -514 as well (if the console showed "514" as zmax value).

See this thread:
http://forums.bots-united.com/showthread.php?t=2071

Re: Overview Height
 

Hmmm ... never heard of the slicer thingy.
How does it work for you ?
Pretty good proggy, er wot ?

Re: Overview Height
 

the slicer does what it says, it cuts the map into slices and writes each slice in a BMP file. People can use these drawings later to get a precise contour of the map. But one problem, the slicer doesn't apply any textures, the drawings are black&white.

http://hpb-bot.bots-united.com/bsp_tool.html

actually I've always wondered how mappers do their overview bitmaps. I'm not sure it's the slicer they use.

Re: Overview Height
 

No, I suppose not. Basic overviews are done like I described in the thread I linked, even multi-level ones. The more multi-level stuff and eye candy, the more Photoshop is involved, of course.

To get the different slices, all you do is go into overview perspective and change the Zmin value. Then you take screenshots at the desired height levels, and finally you photoshop them all together.
But the height in the overview.txt file is always the Zmax value, not Zmin.