Holman

I think historical SOP was to pop smoke and then displace, so firing into the last known location would be a bad bet.

It's pretty confusing that the "3.0 upgrade" upgrades you to 2.20. I wonder why they did that.

Is this part of the updated 3.0 update, or is it a separate download?

Thanks! And this can be applied on top of the first release of 3.0 with no problems?

Yes, it does.

You can already mix American and Commonwealth forces. Perhaps not in quick battles, but certainly in the scenario editor.

British "Funnies" Flamethrowers Protective terrain features (shingle, obstacles, seawall) for D-day scenarios More variety of bunkers and defensive works French tanks in German service Landing craft (too much to ask, I know)

Did Americans ride tanks into battle or just use them as road taxis? I've heard of no episodes where American infantry intentionally rode tanks into enemy contact. (The only accounts I can recall describe troops scrambling to jump from tanks as they came unexpectedly under fire.) Of course there may be cases I've never heard about, but nothing I have read suggests that tank-riding in combat was widely practiced or trained for.

The truly game-changing elements in 3.0 have to do with AI logic and scenario design, but those will develop over time.

One problem with the Nijmegen campaign is that (at least in the missions I've played) your forces are out in the open while the enemy is in cover. I believe undirected air units will attack what they can see, so the odds of blue-on-blue may be much higher than 50%.

Will the fix to CMBN/FI air support (setting it back to controlled as was intended) be out soon, or do we have to wait for a longer patch cycle?

What is the cost of losing one's leader specialists (as casualties or when the squad is split)?

Just to be clear (because my earlier post might be ambiguous), the gun didn't reappear after a save game reload. I started the campaign fresh both times. Once the gun was there, and once it wasn't.

I can report a weird result. I'm playing with v3.0. I checked with a fresh start of the campaign (no saved game) to see what was up. Both times I started up CMBN and loaded the campaign first thing. When I first checked the campaign this morning, the AT gun was indeed missing. This team starts the first scenario loaded onto a halftrack, and I saw the crew (and ammo) but no gun on the back of the vehicle. Unloading the team put them on the ground with no gun. Loading and unloading them made no change. The AT gun was definitely absent. However, just now, I fired up the campaign scenario again because I wanted to make sure of what I saw before posting here. This time the AT gun was present. It was limbered at the back of the halftrack and could be loaded and unloaded with no problem. The gun was definitely there. I made no change to my installation between these two tests.

As usual, a numbered upgrade changes CMx2's text files and necessitates a new version of Vin's Animated Text. I'm posting to thank Vin for this great mod and to ask if there will be a new version.

$10 buys me CMBN not becoming obsolete the way CMBO did. 'Nuf said.

I expect that the CMRT patch will come before the v3 upgrade for CMBN or CMFT. The patch will set the new engine standard, and then the upgrade will bring the other games up to there. (n.b. I have no insider knowledge. This just makes development sense to me.)

TL;DR and take my money!

Yes. BTS plans to keep all of the games at the same level.

Sometimes, for sure. But I've found that swallowing those mistakes against the AI (just as I would in a human PBEM) makes the game feel more dramatic.

I've killed lots of pixel enemies with pixel bolt rifles in CM. As has been pointed out, however, CM scenarios tend to favor short range engagements where automatic weapons decide the issue quickly.

Also: if I read the annoucement correctly, the new installer's are only available to those who have bought bundles in the past. Can those of us who bought the games/modules individually download the new clean installers as well?

Good news on the streamlined files! However, "[ Click here to jump to the updated CMBN store page ]" on the announcement page actually links back to itself.

Historically, it has been shown that apparently easy things can actually be very difficult at the level of code.

My number one rule for a decent game against the AI is "no do-overs." The temptation is always there to go back to an earlier save and try again when something goes wrong. You can't do this against against a human opponent, and of course the AI can't do it, so don't do it against your poor hapless computer. I break this rule all the time.