Can you upload one of the corrupted saves here please for us to inspect (and ideally the last good save you have for it too, bonus points for a save that is corrupted and then 1 order phase earlier is good).

Standoff would be my guess, yeah.

Yes. Units in R&R will not engage, though will return fire if fired upon.

The patch note I think is incorrect and was supposed to read the opposite. As such the .50 being a more powerful weapon will generate better predicted results and so be used instead of the 240.

In a multiplayer game, the game resolution will pause for the turn to be passed to the other player so that they can issue their orders. When a player downloads the save they will get a replay of what happened between when they last uploaded and the game's current state (actually, I think this might ...

That is one of the challenges of using these write-ups. The on paper "This is how we want to have our forces organized" doesn't always match up with the "These are the forces we actually have to organize and where we've decided to put them." So it's quite possible for both to be right, with the on ...

Did you place an HQ above the problem HQs, or were they not reporting to anyone else?

1) Each TT plan in the game is by definition (you can see consistent terminology used for them elsewhere in the game like in the Ops report tab) a Serial. A serial by definition has a single pickup and landing point. So if you want multiple pickup or landing points, do them as separate plans. At ...

Try issuing orders through the right click on the map menu rather than through the unit dashboard.

If you do need to use the unit dashboard (you don't want to get rid of prior orders already issued), are you hitting save before closing the dashboard?

I'm not sure how, but the order got deleted in the event queue and will never complete. It did work for me just re-issuing the barrage orders, so try that. I created this as FPSS-7013 in our bug tracking system. If you have any info about how you created these orders or what you did to modify them ...

Probably not until the .0.3 patch is released (it fixes some networking and FoW code), but I'll prod the publisher to make sure something is in the works.

edit: (oh, also slightly improves tournament scoring)

Those 2 Bradley sections should be avoiding being directly in the enemy path. Prefer striking from the sides and use Screen instead of Hold. Using Hold will cause the unit to take longer to move out of the hex. The other thing to consider is that if you're in a forested hex, you're not going to be ...

Your screen resolution is only 1366 x 768, which is below the minimum requirement of 1920 x 1080. As an unofficial workaround, you might be able to get past this by setting your windows display scaling to some value less than 100%.

A Standoff setting could maybe get you some of what you're looking for, but we don't have logic for that kind of decision making. (If it's a mech force the disembark when in X range of the enemy could also be used.)

Sorry, Capn Darwin was mistaken. They should already be fixed, but in the 3.0.3 update.

The priority number is our arbitrary heuristic calculation where a higher number will get serviced before a lower number (assuming a relevantly capable artillery unit is available).

When you go to Resume Scenario, use whatever path is listed at the top, that should work.

SgtZdog, I am pretty sure I left the battle plan on random. Sometimes I set it to plan #1 first time playing a scenario. I can send a save game but can't find them in the game folder. Are the saves in a remote document folder or something? And do you want the end save or a mid-game save or both? I ...

If you could, let us know the BP the AI was using or upload one of the saves from your playthrough here (an autosave is fine.)

I would hazard a guess you are modifying a current order's SOP instead of the Default SOP, then when you issue a new order it uses the Default SOP which is still set to 6. When you issue a new order to a unit, that order will use a SOP that is a clone of the Default SOP. But then afterward because ...