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

Vanir Ausf B

  • Content count

  • Joined

  • Last visited

  • Days Won


Vanir Ausf B last won the day on December 12 2017

Vanir Ausf B had the most liked content!


About Vanir Ausf B

  • Rank
    Senior Member

Profile Information

  • Gender
  • Location:
    In the middle of a desert in SW Wyoming, USA


  • Location
    In the middle of a desert in SW Wyoming, USA.
  • Interests
    Paintball, FPSs

Recent Profile Visitors

2,057 profile views
  1. We would need the save file from the turn before the bug happened and it would need to be reproducible. The reason this bug is still around after all these years is that it seems to be not reproducable.
  2. The manual is wrong about that. The Hide command has no effect on the visual spotting of vehicles.
  3. The manual says the Hiding vehicle will "keep a low noise profile". You can debate what the could mean but it's important to note that giving a vehicle a Hide command cuts the range at which it can be heard in half rather than reducing it to zero.
  4. Detection/Magic = Experiment

    Ah, no worries. You were too subtle for me
  5. Detection/Magic = Experiment

    Ummm... I'm pretty sure I already acknowledged that. I was simply explaining why the "experts" are not reacting with shock and horror. http://community.battlefront.com/topic/111671-vision-restricted-when-closed-down/?do=findComment&comment=1475929 http://community.battlefront.com/topic/113566-spotting-ability-of-tanks/?do=findComment&comment=1508404 http://community.battlefront.com/topic/84426-spotting-changes-in-111/?do=findComment&comment=1102947
  6. Detection/Magic = Experiment

    Um, it works during daylight too. It's just more obvious at night.
  7. Detection/Magic = Experiment

    They are. Play a night battle in CM and it will become apparent very quickly.
  8. AFV Show & Tell

    Awwww, how cute!
  9. Detection/Magic = Experiment

    In order for the test to say anything useful about spotting time the time to spot for each individual tank would need to be recorded rather than just recording the fastest time out of several dozen tanks. More generally, Combat Mission systemically undervalues cover and concealment for infantry. This has been known for more than a decade. Things have been tweaked a bit more towards reality here and there over the years but it's never going to be exactly realistic since to some degree it is a deliberate design choice (from comments made by BFC) in order to keep the length of CM battles from approaching that of real battles and because strictly realistic spotting would cripple the AI since it does not know how to identify and area fire at suspected enemy positions (which is what constitutes the majority of real world shooting).
  10. The only way it could conceivably take that many shots to hit is if shot fall could not be observed. The cannon was plenty accurate enough to hit almost every time once range was dialed in. I find that figure suspicious, particularly since it gives an average of only 3 shots to hit in Korea, in which most of the tanks in use were the same tanks used in WW2, firing the same 76 and 90mm cannon.
  11. Ignore the out of range text. All on-map mortars show that for smoke missions when they are out of HE rounds. Plot the smoke mission and it should fire.
  12. How accurate *is* CMBS?

    In other words, they were not using Russian doctrine
  13. How accurate *is* CMBS?

    I don't think CM models different dispersion for different ammo types for the same cannon except to the extent that muzzle velocity differs.
  14. Panther gun damage

    Is that a problem? Optics are made of glass. Also, it's not actually possible to completely destroy the optics of a tank in Combat Mission. The gunner never loses his ability to spot and target.