Jump to content
  • 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:


      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
    • Battlefront.com

      Forum Reorganization   10/12/2017

      We've reorganized our Combat Mission Forums to reflect the fact that most of you are now running Engine 4 and that means you're all using the same basic code.  Because of that, there's no good reason to have the discussion about Combat Mission spread out over 5 separate sets of Forums.  There is now one General Discussion area with Tech Support and Scenario/Mod Tips sub forums.  The Family specific Tech Support Forums have been moved to a new CM2 Archives area and frozen in place. You might also notice we dropped the "x" from distinguishing between the first generation of CM games and the second.  The "x" was reluctantly adopted back in 2005 or so because at the time we had the original three CM games on European store shelves entitled CM1, CM2, and CM3 (CMBO, CMBB, and CMAK).  We didn't want to cause confusion so we added the "x".  Time has moved on and we have to, so the "x" is now gone from our public vocabulary as it has been from our private vocabulary for quite a while already.  Side note, Charles *NEVER* used the "x" so now we're all speaking the same language as him.  Which is important since he is the one programming them

Stefano Z

  • Content count

  • Joined

  • Last visited

About Stefano Z

  • Rank
  • Birthday 12/15/1978

Profile Information

  • Gender
  • Location:

Recent Profile Visitors

352 profile views
  1. Please keep the T90-AMs and BMP3s buttoned.
  2. Area target question

    Yes, that is crucial if your opponent has drones and precision arty - and/or Javelins...
  3. Area target question

    The problem with this approach, in particular with the Russians, is that the driver is busy driving and not spotting and sometimes it ends badly.
  4. Area target question

    I thought this would delete the previous waypoint, but never experimented, thank you! Have you tried with vehicles?
  5. Soft launch... CMBS Battle Pack 1

    Warning, more spoilers ****** Another PBEM player here, both scenarios on the US side... In Honor I stayed away from the bridges and went for the fords, so I was able to cross at ~30 minutes into the game but with the iglas knocking down the Apache life is not easy and I am not sure I'll be able to pull a victory off now that we are ~30 minutes from the end. Should the Apache survive this would be a very difficult scenario for the Russian side. In Fort Apache I am having serious issues with my dismounted .50 cal and grenade launchers teams getting stuck in an action spot and not being abel to move. I wonder whether this should be reported as a bug? Overall, the battle pack was great value! Stefano
  6. Deploying Humvee-mounted weapons

    That is not the case, the issue already occurs during the setup phase and does not resolve once the game starts.
  7. Hi all, I started playing the Fort Apache mission from the battle pack as a PBEM and realized that the Humvee crew is unable to deploy the vehicle-mounted M2 or Mk19 after dismounting. One of the soldiers is carrying the weapon but the deploy command is not available in the UI. In a different battle I played after upgrading to v2.10 the Humvee squads were able to dismount and deploy. Has anyone noticed? Mounted weapons are not very effective as the Humvee is difficult to hide so any advice on how to address this would be helpful. Thank you, Stefano
  8. Area target question

    I was not even thinking about suppression. In my limited CMBS experience even a 15 second-long HE 30 mm burst is sufficient to clear out an action square in a woodline. Same thing with foxholes or trenches. I do not play WW2 titles so I cannot comment on those. I am aware of all the workaround/alternatives that have been proposed in response to my initial post but they all come with a cost.
  9. Area target question

    I am trying to have a stationary unit targeting different action squares in the same turn. Let's say a stationary IFV "walking" fire along a treeline, or targeting different buildings, to cover advancing infantry. Mostly to avoid a vehicle getting bogged and minimize exposure to enemy fire.
  10. Area target question

    Hello all, In WeGo games, is it possible to area target different action spots in the same turn without issuing movement orders? Thank you, Stefano
  11. Tactical Lifehack

    I'd say it depends on the terrain. I tend to spread out a whole platoon when lines of sight are limited and just use a scout team with Javelins (they seem to spot much better then scouts or snipers) if I am playing on an open map.
  12. Troop Breach kits and Barbwire

    Is the blast command unavailable or when you attempt to breach the barbed wire the blast command turns into a quick move?
  13. I had an Oplot choosing missile vs sabot against a tank ~1.5 km away, same game I mentioned in the previous post. As far as that game is concerned ~half the time the Oplot fires an ATGM against tanks... n = 2, I am aware it is not ideal. At least selective pressure should weed out those ATGM-loving tank commanders fairly quickly...
  14. I am playing a PBEM and had this happen in ~20% of my collective tanks shots. The target in that instance was a Khrizantema, not a tank, it missed. Two fragmentation rounds were shot at infantry and two APFSDS were shot at a tank and another Khrizantema. I am not including area fire, but those shot seem to always be frag. Game just started so things may change. Stefano