• Announcements

    • Battlefront.com

      Special Upgrade 4 Tech Tips   12/27/2016

      Hi all! Now that Upgrade 4 is out and about in large quantities we have now discovered a few SNAFUs that happen out in the scary, real world that is home computing.  Fortunately the rate of problems is extremely small and so far most are easily worked around.  We've identified a few issues that have similar causes which we have clear instructions for work arounds here they are: 1.  CMRT Windows customers need to re-license their original key.  This is a result of improvements to the licensing system which CMBN, CMBS, and CMFB are already using.  To do this launch CMRT with the Upgrade and the first time enter your Engine 4 key.  Exit and then use the "Activate New Products" shortcut in your CMRT folder, then enter your Engine 3 license key.  That should do the trick. 2.  CMRT and CMBN MacOS customers have a similar situation as #2, however the "Activate New Products" is inside the Documents folder in their respective CM folders.  For CMBN you have to go through the process described above for each of your license keys.  There is no special order to follow. 3.  For CMBS and CMFB customers, you need to use the Activate New Products shortcut and enter your Upgrade 4 key.  If you launch the game and see a screen that says "LICENSE FAILURE: Base Game 4.0 is required." that is an indication you haven't yet gone through that procedure.  Provided you had a properly functioning copy before installing the Upgrade, that should be all you need to do.  If in the future you have to install from scratch on a new system you'll need to do the same procedure for both your original license key and your Upgrade 4.0 key. 4.  There's always a weird one and here it is.  A few Windows users are not getting "Activate New Products" shortcuts created during installation.  Apparently anti-virus software is preventing the installer from doing its job.  This might not be a problem right now, but it will prove to be an issue at some point in the future.  The solution is to create your own shortcut using the following steps: Disable your anti-virus software before you do anything. Go to your Desktop, right click on the Desktop itself, select NEW->SHORTCUT, use BROWSE to locate the CM EXE that you are trying to fix. The location is then written out. After it type in a single space and then paste this:

      -showui

      Click NEXT and give your new Shortcut a name (doesn't matter what). Confirm that and you're done. Double click on the new Shortcut and you should be prompted to license whatever it is you need to license. At this time we have not identified any issues that have not been worked around.  Let's hope it stays that way Steve

Combat Mission: Battle for Normandy

Discussion Forum for Combat Mission: Battle for Normandy

Subforums

  1. CM Normandy Tech Support

    This is a "self-help" community for technical support for CM Battle for Normandy. To request support from our staff, please go to www.battlefront.com/helpdesk and click on Submit Ticket.

    11,635
    posts
  2. CM Normandy Maps and Mods

    Community forum for Scenarios, Campaigns, Maps and Mods for CM Normandy

    23,202
    posts

8,249 topics in this forum

    • 2,310 replies
    • 383,880 views
    • 234 replies
    • 47,428 views
    • 302 replies
    • 49,133 views
    • 275 replies
    • 31,735 views
    • 349 replies
    • 98,602 views
    • 55 replies
    • 9,055 views
    • 22 replies
    • 22,280 views
    • 847 replies
    • 133,410 views
    • 19 replies
    • 652 views
    • 8 replies
    • 211 views
    • 32 replies
    • 1,067 views
    • 150 replies
    • 11,416 views
    • 3 replies
    • 236 views
    • 7 replies
    • 155 views
    • 39 replies
    • 1,082 views
    • 55 replies
    • 1,245 views
    • 0 replies
    • 97 views
    • 5 replies
    • 206 views
    • 15 replies
    • 347 views
    • 13 replies
    • 331 views
    • 100 replies
    • 6,557 views
    • 17 replies
    • 277 views
    • 7 replies
    • 211 views
    • 4 replies
    • 161 views
    • 26 replies
    • 824 views