Map: Height Maps

[dmnt]

Originally Posted by DRG

Tuomas

I've had more time to use the program of late testing work that we are doing to help make "skinning" these maps ( and ours ) a bit less time consuming and after generating a map of the area around Villers-Bocage where the battle was fought it was clear that the contours are being overly exaggerated. They may be perfectly spot on but when translated to a game map things seem a "bit" out.

I really like this program, I really like what it can bring to map making for this game but I'm thinking it's putting at least twice as may contours in than it should to make a game usable map.

Thanks to Google you can "drive" Wittmann's route and it's not quite the grand canyon(ish) experience the map the program delivers now would suggest


what I propose, if possible. is a control for the number of individual height contours that are produced or at least halving the number produced now. I do appreciate the effort you put into this but I think it needs a wee tweak.


I realise some of the exaggeration can be manually corrected but does anyone else ( maybe it's just me......) think these tend be a bit exaggerated for game purposes? The circled area is the big problem as it drops into a steam and that's the main area of exaggeration for me

Edit......I will say though.... I generated a map of the area around where I live and it looks just about perfect so maybe its just a case of watching what's generated and if it seems wrong--- fix it manually?

Has anyone else noticed anything like this ??

Don

I'll check on that. In some cases the data we get from Google may be a bit off or there's some missing values that somewhere on the line get interpreted as "0.0" meters and a huge crater appears on map.

I'm thinking about creating a business account and speeding up the api we get in exchange for a couple of bucks. Then I'll have some time to invest for finding missing value errors and such and returning some information back to the user with the downloaded map. Now all the logs are out of sight for the end user.

[dmnt]

Originally Posted by dmnt

I'll check on that. In some cases the data we get from Google may be a bit off or there's some missing values that somewhere on the line get interpreted as "0.0" meters and a huge crater appears on map.

Looks like this is partially a bug and partially a data issue: In some cases if the max height difference is just correct, the handler might get an overflow (because the check was $height > HEIGHT_LIMIT, so no equality included in comparison) and instead of having level 15 in place a level 0 ground is created. I'm still inspecting this.