Profile of Rosbone

The game has to do a million things for each unit on the screen. So larger modes like 3v3 and 4v4 will always fall apart as the unit count gets large.

Since COH2 has broken physics I would try turning that off first. I dont recall ever noticing any changes with physics???

The Image Quality is the next feature to adjust. Real Time shadows is an expensive routine. So as you reduce the quality, Coh2 reduces the size of the real time buffer. The shadows will get pixelated and eventually turn off. But your FPS may improve.

Snow maps you can turn snow quality all the way down.

I see a lot of players turn the TEXTURE quality down to where the ground looks like plastic. This may help some people more than others.

Assuming you are not videocard limited, If you have a good motherboard you can think about getting faster RAM and/or overclocking it. That may give the largest improvement in FPS.

This ^

For you guys building your own RTS this is what I have so far...

Still trying to figure out how to handle all of the different mappings for Pathing, Sight, and Cover values(PSC).

Currently I am using a bit mask method where each byte in an array represents the PSC elements.


BIT 0 = Infantry Pathing
BIT 1 = Light Vehicle Pathing
BIT 2 = Medium Pathing
BIT 4 = Sight Block or not
BIT 5 = Light Cover
BIT 6 = Heavy Cover
BIT 7 = Building Cover
BIT 8 = Static or not

The PRECISE map is a blend of the three pathing maps.
The COVER map is a blend of the three cover maps.

Vehicles are larger than infantry and therefore require more room to get around. So blocking objects are increased in size.

Cover needs to surround the objects it is using for cover, so its size is also increased to create a reqion around it where units are standing in cover.

Since my code is pretty bad, any unit in cover sets the squad to that cover value for now. Will update it soon maybe. Maybe average all of the individual units cover values?

I thought I should talk about the way I am checking the FOW.

DEMO FOW CHECK
BLACK = Unit position, RED = Sight Blocker, GREY = Vision


Standard FOW is usually a simple circle based on the distance from the UNIT. COH2 also checks for sight blocking on objects in a 2D top down fashion.

Originally I planned on drawing a line from the unit position to the outside perimeter of the sight circle. Drawing lines can be very slow and the same points can get checked over and over. Could have a 2nd map that flags if a point has been checked or not.

To try and optimize I came up with this algorithm.

KNOWN DATA
Working in 90 degree increments I know how many degrees each pixel blocks.
Angle = 90 degrees / Number of pixels
Each row grows by 2 pixels and moves up 1 pixel.

The 1st row only has 3 pixels: 135, 90, 45 and each pixel is worth 30 degrees.
The 2nd row has 5 pixels: 135, 112.5, 90, 67.5, 45 and each pixel is 18 degrees.

I created an array with 360 elements that represents 360 degrees of clear vision.
When I hit a blocked pixel I check off the angles in the array that pixel represents.
Any pixels checked are first checked against the 360 degree array.

In our example, the white pixels above the RED line are flagged as blocked by the 360 vision array test.

Algorithm
- Loop left to right each pixel/texel row.
- Check each pixel for 360 degree vision blockage.
- Check if pixel is within vision range distance.

This is done for each of the four quadrants: Up, Down, Left, Right.

Currently this gets checked for each individual unit on the map. Could simplify it to a calc for a SQUAD. But for now, the frame rates seem to be holding up fine.

Not sure if I should keep posting in the main post? It may get really long. But it keeps it all easy to read for now