• Home
• T3A:Online
• Tournaments & Games
• Replays
• Tutorials
• Mods
• Maps
• Downloads
• Forum
• Showcase
• Users
• Links
• Help

Quick Lists

Top Rated Popular New Updated Last Comments Users

Come visit our Wars Of Arda Mod at the link provided above.

I have notice many ways to cut down on lag for BFME2rotwk.

1: Object Placement - Most people just don't understand how many objects is too much. At the bottom left corner of your world editor is a counter that indicates the number of objects you have placed on your map. This refers to only persons and things on the map, but does not include places (waypoints, areas, waterareas). So here is my recommended amount of objects you can place on the map:

500 or less - Awesome.
500-750 - Still Awesome.
750-1000 - You are still good.
1000-1500 - Games start slowing down slightly when you spawn more units.
1500-2000 - If your map is more than 300 x 300 expect a good amount of lag as unit number inceases.
2000 or more - Start finding objects to delete. Their is no reason to have that many objects on the map and you are trying to be way to fancy. If your PC can handle the stress of rendering all those objects and being able to have large unit numbers then you have a great PC, the rest have slower computers so more than 2k of objects is stupid. Don't be a clown.

When considering the amount of objects on a map always take into consideration the size of the map itself. More objects on a large map will bring problems. While many EA maps have more than 2000 objects their simply isn't any reason for it. Not that EA's maps aren't bueatiful, the fact is that EA mappers are a bunch of clowns that have no idea that people running bare minimum requirements for the game can't handle more and more objects on a map.

2: Map Size and scale - Bigger is always better but always has more lag with the more objects and amount of units you put on the map. For fortress maps that are bigger than 300 x 300 it would be a good idea to scale up your objects to not only reduce lag by cutting down the number of objects but also making your map look as epic as possible. If you don't know how to scale a object you can simply click on a object in world builder and look at the properties of that unit, scale size is in there. If you can't find this you are a noob and should go back to mapping 101 or blind.

3: CAMERA ANGLE This is key to having a laggy map or not. The EA default for camera angle is 37.5 which does what it implies by placing the camera on a 37.5 degrees (downward) angle. This is retarded, their is no reason to have your camera angle on EA's default setting. Change it something between the range of 45-70. In this range your PC will have a more top down view which is not noticeable to players. The reason why this cuts down lag is because if you have a camera angel of 37.5 or less your PC now has to render more objects in the distance and also render more of the map while playing the game. If you are trying to make a RPG kind of feeling map with a more 3D angle it is possible to do but the game becomes more unstable with larger maps and more objects.

The next thing with the camera is the height in which your camera is allowed to go. You shouldn't have the height of the camera not exceed 500-600 since that would render too much of the map causing a slowdown. EA has it set at about 300.

4: Unit Placement, Epic Battles- Realistically I would say you can have about 50 battalion size units on a single map. Anything more than that would create lag spikes. Another indicator to go by is command points. Add up all of the players on the map command points and if it is more than say 8000 then you have way to many units. If you really want to make a epic battle you should consider placing waypoints on the map where you want units to spawn and only have them spawn in after a different unit already in play has died.

5: Wind Sway- You know every tree you have and bush sways from side to side in the course of a game. If you are just looking for ways to cut down on lag I suggest going into the scripting tool and making a new script and finding the windsway function in the unused section under environment. If you set everything to zero then it will remove all swaying of shrubs/trees and that can reduce lag alot if you have a map with heavily forested areas.

6: Water- This doesn't effect game play unless you start adding a lot of waves and rivers.

7: Fog/Snow- Adding fog or snow to a map can add a very small amount of lag to a map only if you play with the EA defaults. EA has nice defaults that you should just leave like they are. The only things you should change is the color of fog.