Profile of Rosbone

DAY 27 PROGRESS
Not too much progress over the last few days. But I did come across some useful things about UNITY I thought I should share for developers.

After adding a bunch of code for Pathing, Fog of War, Enemy Combat, etc, Unity started to slow down to the point of missing mouse and button events. I wrote some code to track FPS min/max. And during heavy code usage, the min FPS was around 30. This only lasts for 1-2 frames then pops back up.

So I stopped adding new things and started optimizing a little.

COROUTINES
I am a noob at Unity and did not feel the need to start MultiThreading the app just yet. But I did want to try using COROUTINES.

COROUTINES give you an ability to do some work in a function, give up control for a frame, then return to do more work. So it spreads heavy calcs out over time. This was very useful in the FOW calculations since I only want to update it once per second or so. Just sprinkle in some YIELD RETURN NULL commands throughout and you are good to go. No more missed clicks or presses.

AUDIO IN UNITY
I also wanted to spend some time getting the audio to play in a 3D mode. UNITY only has one normal 3D command that lets you play a sound in 3D space. However, it rudely sucks ass. Decent for one sound if you dont move. Multiple sounds and moving just created random muted noises and volumes. Horrible.

Luckily I found this guy on YouTube and his tutorials are always fantastic.


This gives you great control and management of sounds but only in 2D. Which is all I am shooting for at this point. Just a couple distance checks and I can set volume and pan of sounds with no glitching or warbling.

Good enough for me.

RED UNITS STILL OP WTF RELIC ?!?!?!?!?!?!"2112212

I will rephrase for you "R3d UnIts sTIll oP WtF rELic ?!?!?!?!?"

Best of luck boys! Good work all!

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?