So I want to start a new map that will include flyers. The image backgrounds in the sky dome, like mountains, start to move in very unrealistic ways when flying with a star fighter. So the only solution is to extend the the terrian and add mountains to give it a more realistic perspective when moving through the map.

So my question is, adding this much terrian, will my map be more likely to crash because of the resources being used? is there any memorypools that I should use in the LUA to provide stability?

*Note: I will also increase the 'farscenerage' in the sky file to very large values in order to render the visibility of the full terrian.

Size perspective:

• 2048 represents the number of grid squares on your terrain in one direction
  Each grid square is 8x8 meters
  2048 x 8 = 16384 meters (53753.280839895015 feet) or 16.384 kilometers (10.1805 miles)

Your map will be huge.
I've never created a map with terrain that large so I can't provide input on stability, i'd say go for it and report back to us the problems you encounter along the way. When you choose to do extreme things with this game you can always expect to hit limits of some kind.

Well, sadly it did not work. First of all, in ZE, when I started changing the height of the map, beyond the 1024x1024 limit, the change in height would clone on the opposite side. So when I raised the height on the right side of the map, it would automatically raise on the left side also.

Another thing is after the 1024x1024 limit, there would be a pattern patches of textureless terrian. When I tried to munge my map it said that there was a missing bracket in the TER file. And when I ran the map in game, I was not able to spawn. So I adjusted back to 1024x1024 and it worked back to normal. So Another BF2 limit is that maps cannot be bigger than 1024x1024.

1024 should be plenty. I started a map with about the same idea, and 1024 seems to be enough space for a fighter to fly around without constantly turning.

For comparison stock SWBF1/2 maps are on a 256x256 "plate" of terrain, but typically only take up about 1/3, directly in the center.

DomeModel()
{
Geometry("kas2_mountains");
Offset(80.0);
MovementScale(1.0);
Reflect();
}

If the root of your problem is the movement of the sky dome, try adjusting the highlighted line above. I think the original value in my example was 0.95 - I had the same problem as you, so I changed the value to 1.0 and the sky dome no longer moves around.

Eggman wrote:

DomeModel()
{
Geometry("kas2_mountains");
Offset(80.0);
MovementScale(1.0);
Reflect();
}

If the root of your problem is the movement of the sky dome, try adjusting the highlighted line above. I think the original value in my example was 0.95 - I had the same problem as you, so I changed the value to 1.0 and the sky dome no longer moves around.

Yeah that seemed to work thanks eggman and the other guys who responded, much appreciated.