Map making problem persists?

[GliderRecon]

Thoroughly enjoying CotA thus far, but...

One of the reasons I stopped making maps for HttR was this weird LOS problem: tm.asp?m=926028 . I've done just a couple of experiments with CotA's Map Maker and I seem to be seeing the same thing. Hopefully it's a problem with my map creation technique, or something relatively easy to fix.

(Image shows a Korinthos map (decluttered for testing) ; max visibility apparently no more than 2km in clear conditions)

[Arjuna]

That's a bug, already reported since release where the MapMaker CalcVisibility Tables function is not using the correct range. It should be set to 10kms but instead defaults to 3km. I will be looking at this next week.

[GliderRecon]

Good to hear. Thanks.

[simovitch]

Ok, this one has been driving me nuts, but I accidentally stumbled on the solution:

(edited for clarity)
In MM,

1. build movement tables
2. build vis tables (optional)
3. If you did 2, then rebuild move tables again.

Remember you dont have to build visibility tables but it speeds up the in-game LOS tool.

Incidentally the same is true for HttR maps!

[Arjuna]

simovitch,
 
So are you saying if the vis tables are done before the terrain then the LOS tool works fine in the game out to 10km?

[simovitch]

ORIGINAL: Arjuna

simovitch,

So are you saying if the vis tables are done before the terrain then the LOS tool works fine in the game out to 10km?

Yes

[GliderRecon]

ORIGINAL: simovitch
In MM, if you build the visibility tables, then BUILD THE TERRAIN TABLES AFTER the visibility tables...

Incidentally the same is true for HttR maps!

No luck here with that strategy [:(] Calculating vis before terrain just crashes Map Maker for me (in both COTA and HTTR)

Not calculating vis doesn't work for me either. I still get the 1km radius spotting bubble.

[simovitch]

you shouldn't have to calc vis[&:]
make sure your scenario start time is daytime, like 10:00.

then try this:
1. calc move.
2. calc vis.
3. calc move again.

[GliderRecon]

ORIGINAL: simovitch
then try this:
1. calc move.
2. calc vis.
3. calc move again.

Nice one Simovitch! That extra terrain table calc at the end does the trick.

[GoodGuy]

Time-consuming, though......... [>:][:@][:-]

Good to know, though [:)]