@JD_Wang No I'm using the updated Steam version. Ill try the fourms version though.

It seems that combat support is still being used by vcom. Had mine take off mid mission to go loiter over an area.

Did 3.0 fix taking over combat support?

Depends on what you are trying to do, but I usually just have insurgents without a taor, and I blacklist all the spots I don't want them to be such as bases and airports. I don't see the point in a bunch of small taors unless you are trying to do something specific. The commander will pick up the objectives just as fine if you set it to the complete map instead of small taors.

Hey I'm having trouble with this as well. Before the recent update I could do the locally hosted server thing and save the game, but now whenever I press the admin save and exit thing nothing happens. I have my mission set to save local as well.

So what you could do is have OPFOR Commander have 2 civ objectives and 2 mil objectives synced. The first set of objectives is set to the TAOR that you want the enemy units to spawn in. Then for the second set, you can make it objectives only and set it to the TAOR that you want the OPFOR to attack.

I'm going to throw something else out there, if you're looking for large scale, dynamic air campaigns, you should check out Falcon BMS. You fly in a complex F16 and everything is persistent like an Alive campaign. Its free too.

Also one more thing, I've been looking at the RPT, and I keep seeing a reoccurring "count IED location: 0" What does that mean? When I tried to reproduce the problem, I kept running into issues where no IEDs where spawning in and I just restarted the mission.

Ok I submitted a ticket

Okay I did some testing. It appears that the problem is with the debug, but then theres more to that. So I made the mission with just Alive, CBA, and cup maps. The same issue happened with the debug going away, however, the IEDs are still in the game world. I went back to check it on the main mission, and I got the same result. So its just the debug not working. However, I encountered a 2nd problem. After the first IED goes off, the next IEDs that are still spawned in don't function right. I rolled over a dug in one, and ~10 seconds after I made contact, it went off. Same happened for the VBIED after setting off the first IED: the car de-spawned with white smoke, and left a clay charge on the ground, which took a while for it to go off.