WallysWorld

Thanks for putting the time into these documents, Mike. I was just reading your document on Hungarian armor in CMBB and it was definitely fun to read.

Excellent! Thanks for doing this.

You can use this interface for CMFI which is a amalgamation of the excellent work done by Marco Bergman and Juju and combined into one download by von Albert: http://cmmods.greenasjade.net/mods/4961/details Many thanks for this updated CMBN UI, Juju.

I have Windows 7 64-bit and CMSF works no problem.

Super thanks for these icons, Ian. I'm using your icons for my other CMx2 games as well.

Many thanks for this mod, waclaw. Much appreciated!

Super thanks to BF for releasing a demo for CMBS. I haven't bought CMBS yet, but I'm sure the demo will finally convince me to do so.

Nice videos. I still enjoy playing CMA and I think it was definitely underrated.

Once I did that for all my CMx2 games, the frame rate stays at 30 just about all of the time which makes for very smooth gameplay.

That was fun to watch. Thanks for posting!

I had that kind of happen too after I took too many causalities in one battle. In a campaign, previous causalities carry over to the next mission if I remember correctly. Not all causalities will be replaced no matter what the briefing says. From the CMA manual: A Campaign is a single player game that progresses through a series of interconnected Battles stretching over many simulated hours, days, weeks, or even months. After completing a Battle, Combat Mission selects the next Battle based on the results of the one just completed. The Battles within a Campaign are all premade, but are adjusted to reflect combat results from the previous Battle. Certain units have their casualties, changes in leadership,ammo usage, damage, and other factors carried over to the next Battle they appear in. Such units are called Core Units and constitute the bulk of the player’s available force for the Campaign. Depending on conditions before each new Battle, Combat Mission may replace fallen soldiers, repair damaged vehicles, replenish ammo, etc. However, as with any real-life military campaign, replacement, repair, and replenishment are not guaranteed events. A wise player will keep this in mind and avoid wearing out his forces trying to achieve something that, in the larger context of the campaign, is relatively unimportant.

Turn the grass from High down to Normal and you should gain about 8-10 fps. Running ToW2 with the grass detail set to High is a good frame rate killer. That happened with my old 660 Ti and still happens with my new GTX 970 and my i7-920.

Yep, me three. Had the exact same issue too yesterday. As Markus86 wrote, the solution was to exclude the Battlefront\Combat Mission Shock Force\Modules folder from the Avast File System Shield under Active Protection. You can exclude the whole CMSF folder or just the Modules folder as I did. Either works.

You have to install the upgrade during the Command or orders phase of the PBEM. You shouldn't install the upgrade during the Reply phase.

In a game I'm playing now, my German squads are being hammered by the Soviet SMG squads in the forest. My squads manage to get off a few shots at the start and maybe take one or two Soviet soldiers out before I lose about 75% of the squad with just a couple of SMG bursts. This happens even when my squad is waiting in ambush armed with a couple of MG 42's.

From Wikipedia's entry on the Sherman: "The Sherman was one of the first widely produced tanks to feature a gyroscopic stabilized gun and sight. The stabilization was only in the vertical plane, as the mechanism could not slew the turret. The stabilizer was sufficient to keep the gun within 1/8th of a degree, or 2 mils while crossing moderately rough terrain at 15 miles an hour. This gave a hit probability of 70% on enemy tanks at ranges of 300 to 1200 yards. The utility of the stabilization is debatable, with some saying it was useful for its intended purpose, others only for using the sights for stabilized viewing on the move. Some operators disabled the stabilizer."

It's fine as long as you both upgrade during the command phase and not the replay phase. But both have to be on 3.0 for the PBEM to continue, I think.

Just fooling around in CMRT with a QB and caught this massive explosion when my StuG got hit right at the end of the playback. This great explosion is courtesy of Vein's special effects mod.

An updated 3.0 installer for CMBN and CMFI was released on the 21st: "Updated installers for the 3.0 Game Engine Upgrade for both Combat Mission Battle for Normandy and Combat Mission Fortress Italy are now available for download (PC only)! The updated installers address a number of additional issues found after the original release, mostly specific to certain hardware and graphics drivers: - The building entry bug should be fixed. - ATI decal-related lighting issues should be fixed. - General shadow performance and looks have been improved. - Air support should now behave as it used to in CMBN and CMFI." If you updated to 3.0 before the 21st, I would re-download the 3.0 installer again and run it. I did that and everything is fine.

My thanks too, Vein.

Thanks for posting. Interesting to see.

Have to agree as well on my 660 Ti. It seems I even gained a few frames as well. Not much, but a couple of frames per second.

Just checked the game after the 3.0 upgrade and everything is fine. I had the greyed out issue with the MG scenarios with the 'old' 2.12 patch that the 'new' 2.12 patch fixed.

In the patch notes it says as long as you save your current game in the Command phase before installing the upgrade, 3.0 will be compatible with the save game.

Basically to make it easier to reinstall the game and modules from scratch. I just bought CW and MG for CMBN and had to go through the process of installing CMBN right from scratch. A one time installer that installs everything is very handy.