AI and roads

[floosy]

Ok problem are dead....

Thanks to bravo 6 for testing my map. The problem was the "gen terminator " + "texture layers parameters" (5m grrrrrr better with 40 )

[IceBreakr]

So, you're telling me that with texture layer of 10x10m AI is unable to drive on roads, despite rightly placed terminators?

[bravo 6]

I'm not confirming as an official information as BIS would do.
It is merely based on what i have experienced.

I experienced it in 512x512, 1024x1024 and 2048x2048 Terrains with texture layer of 10x10m, like you said, and all roads were bugged for me. They could have AIs issues or simply some cuts in the roads in flat ground.
There for if i change the texture layer to 40x40m everything would work better, also the map would run much, but much more smooth without CTD when using maximum View Distance.


Again, it is only based on a year of experience. As you know I'm simply and merely a green noob on this subject.

[IceBreakr]

It is confirmed, I just lost 2 days for testing why AI don't drive on roads, although they were properly terminated... I've noticed you fixed Floosy's roads by changing texture layer and I've tried that. To my amazement AI drove like nascar drivers and finished a 5km road full of tight turns in just 4,5 minutes

Now there's a problem. My satimage is based on 10x10 (5120x5120) image, and of course now its FUBAR. What must I do with satimage, resize it somehow?

Here's my 5120x5120 satimage on 512x512 terrain with 40x40 texture layer setting:

[bravo 6]

Why is it fubar?

From what i understand you terrain size is 512x512, correct?


So in Visitor3 Project Parameter:

• terrain grid size: 512x512

• terrain cell size: 10.0

• terrain size (meters):5120.0x5120.0

• texture layer (edit): 40.0x40.0m

• your sat image should be a 5120x5120 Pixels.

edit: your background image .bmp should be 5120x5120 pixels

[IceBreakr]

I've edited my post above with an image, see it for yourself

[bravo 6]

ah yes, i remember now..

yes, since the sizes are different, the images won't match the terrain.

Do you really want to know what i did when that same thing happened to me?


... i did my sat image all over again from scratch and then i added more details to the image. Use lower altitude with bigger image size and in the end resize it to 5120x5120.

I know it sucks.. an its a terrible solution, but thats what happened to me with Al Amiriya long time ago.

If you are going to resize the image to fit the terrain you will lose details.

[IceBreakr]

I really hate this BIS "undocumented features" that take days to figure out... problem is that my texture already is at 5120x5120. I'm checking the corners now and filling them with "fake" sat-image instead of blue (unused terrain underwater)...

Edit:
oh well, it seems that 5120x5120 satimage has an offset or something. I draw a border of orange color all around 5120x5120 png and this is what buldozer shows

[bravo 6]

I know what you mean and i understand your point, though i believe for ArmA2 BIS did not use the "crappy" Visitor3 like we do for our terrains. I bet they have a more sophisticated tool, with better features time to time, so why would they lose precious time making an official Document that would be sooner outdated?


Try to look for the positive side: BIS did in fact release some tools for us community, thats good enough.

[IceBreakr]

I understand, but there must be solution. I did further tests:

Data: 512x512 terrain, 10m cell size, 5120x5120 satimage&mask
Texture layer:
10x10m - AI doesn't know how to use roads / satimage works perfeclty
20x20m - AI does use the road but stops every 100-200meters and then proceeds / satimage works perfeclty
40x40m - AI drives on roads like a pro / satimage doesn't work (pics above in this post)