Jump to content

WallysWorld

Members
  • Posts

    148
  • Joined

  • Last visited

Posts posted by WallysWorld

  1. 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.

  2. 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.

  3. 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.

  4. 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."

  5. 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.

  6. I thought I installed ok in CMBN, but all my MG scenarios and saved games etc are greyed out. What to do?

    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.

×
×
  • Create New...