OMAC

This issue is still present in 1.68 hotfix RC. Please fix!!!!!!!!!!!!!!!!!!!!!!!

New 1.68 hotfix RC available! Is there a changelog?

I had this problem with "Caught In A Trap" as well. No way to proceed after airstrike. Campaign must be aborted or mission skipped using endmission cheat. Using 1.68 stable, no mods except for Bell Tolls campaign. I had no Friendly Fire message or anything. Also, before this, after team disembarks from Panther IFV to assault AAF base near Pyrgos, rest of team heads to S/SE for some reason, away from base. So I cleaned out the base myself. As above, I also was frozen if I loaded any savegame at that point, possibly because player died during cutscene. I couldn't move at all no matter which save I loaded. But if I quit mission, then I could load a save normally, although cutscene problem at end occurs every time. The campaign has been utterly fantastic, and virtually bug free, up until this point. Excellent work! --- Edit - Mission 02 - Up Cadillac (Recon): AAF Gorgon IFV at base northeast of Checkpoint Schoonerhead was already blown for some reason when I reached OP Cadillac and got the AT launcher. The Gorgon wreck was in road at the base. Possibly this was caused by the fact that I may have blown the Gorgon using Titan AT in first mission. If so, then Gorgon wreck shouldn't be at base, but where it was blown near defense point in first mission, and the task about destroying the IFV shouldn't be assigned, or even exist. Mission 02 - Up Cadillac (Recon): Greenback forces at Schoonerhead set their explosives off too soon and blow themselves up. AAF soldiers should flee before CP is blown (or shelled?). Mission 02 - Up Cadillac (Recon): CP Humpback - cutscene can start and then player and mate can be killed during cutscene by AAF along road to north. Once cutscene starts, that AAF patrol should be deleted, or at least have simulation disabled (better), until cutscene ends.

Do you mean Titan AT? Ok, I'll try that. Thanks.

Yes, that's exactly what I did. I had PCML going in and got more missiles from my AT guy when needed. Still it wasn't enough to get the task to complete! That tank is tough. I always flank to the left when leaving cemetery and reach main street down which is clear view of tank. But I believe there are some obstacles in the street that make aiming at the tank difficult. When BI fixes the mission, I'll try again.

PCML is a missile launcher! I couldn't get my AT guy to hit the tank, or he got killed...don't remember. I had a PCML myself at the time. Yes, as the FIA isn't much involved after that (they are in Game Over, however, if you choose that story path), shelling Pyrgos probably has no story impact other than the angry comm admonishment.

I've always ended up using arty to blow tank. Last time (1.66 I think), I damaged the tank enough with PCMLs to get crew to disembark, and then planted charge, but still that wasn't enough to kill the tank and get the task to complete. So I used arty to finish the job, but then got the angry FIA comms, making me wonder if arty shouldn't be used.... Anyway, I'm now playing In Our Time campaign by ted_hou. Totally awesome so far. I highly recommend it.

The mission is indeed broken in 1.68. Same problem occurred on two separate replays. I updated the ticket.

I almost wish Tanks DLC would be released before Tac-Ops so that the latter would include lots of missions using the new tanks!

That error has been around for a long, long time, and reported many times.

Seems to me that something changed over the last several days that returns the cookie-related problem of constantly having to re-log in to forums when I switch browsers. It was ok for months, and now the problem has returned. Seems better since at least yesterday...

There were some fixes for this mission in 1.68: Fixed: Vehicles would move incorrectly in the Moral Fiber scenario Fixed: There was no 3D task indicator for getting in a vehicle in the Moral Fiber scenario

I made tests with AI-controlled Tunguska and Shilka using current beta, and they did auto-engage enemy ground units if they are under combatmode RED waypoint orders.

Have you tried the A2 and OA betas? I would stick to them, as they have massive amounts of fixes in them, including some for Warfare, I believe. Check this old ticket: https://dev.withsix.com/issues/16766

The same plant is on A2CO Chernarus (although in smaller clumps), and there is no popping at all. Smooth as silk all the way.

Using current betas, AV-8B Harrier with AI pilot will never hit a stationary ground target using Mk82 bomb. The bombs always hit short of target (miss distance depends on speed and altitude of plane). If setCombatMode "BLUE" is set for opfor ground targets, Harrier Mk82 bombs will not lock onto them at all. They are seen as non-hostile or otherwise invisible to targeting. Edit: Using A2CO with A2 beta and OA stable (1.63 pre-corepatch), first Mk82 bomb dropped by AI-piloted Harrier scored direct hit on stationary tank target. Is there a way to have AI pilots use full locking with iron bombs, but human pilots only get the locking with reduced maneuverability (as in current OA beta)?

Yes I know, but why the crashes when the plane receives no damage from ground fire? The Harrier was crashing more than 75% of the time, apparently for no reason. I wonder if the crashes would occur if the enemy tanks it was targeting had no ammo...

I'll test AI now. I should have stated in my last post that I really didn't "aim" before dropping bomb other than trying to keep within a few degrees of vector to target (i.e. flying nice and flat directly towards target), and not going too fast. Edit: Harrier with AI pilot appears to be missing stationary targets quite badly using Mk82 bombs. Don't know the cause or if it is worse than before. Oddly, the Harrier keeps crashing into ground most of the time even though allowDamage is set to false. ???

Moving toward target zone, I tab lock on a target. Green square appears on target. Moving closer, green circle appears in square, indicating lock. I wait a second or so, and then drop bomb. Several times the bombs hit so close to tank that it was destroyed. You can't be moving too fast, or bombs will overshoot target. Stay under ~350 kph. I was flying at around ~400-500m alt. A few times the bombs missed, but only by 100-200m, as I wasn't flying flat enough, or too fast, or I veered off of vector toward target to avoid ground fire.

Has the clutter popping always been this way? I think it's been in there for a while, perhaps forever, but I'm not sure. Once you notice the popping, you become fixated on it, and it becomes even more distracting.

I tried the Mk82 bombs on a AV-8B Harrier using current beta, and they worked perfectly with "locking" on Veteran. They were very accurate for me, but not too accurate. I nailed 3 tanks in just a few runs. Great fun! Excellent job, samatra!

^ ^ Good job! That low-lying thistle-like plant with purple flower pops in a little also.

Check this out:

I swear that if they fixed the LODs (or whatever the problem is) for those two plants, most of the issue would be solved.

And also with these darkish, spindly, narrow, partially dry plants with small buds on upper parts.