NEW v1.11 GAME FEATURES
Corrected crashes related to barbed wire units.
Corrected a rare crash/hang problem in WeGo "blue bar" calculation.
Corrected the occasional failure of "buddy aid" to retrieve useful ammo from fallen comrades, and accidentally to adopt their targeting orders.
Corrected a problem that sometimes made fortifications too hard or too easy to spot.
Panther "shot trap" on the lower turret mantlet (potentially) deflects shots downward into the hull as expected.
British 95mm HEAT shell has correct amount of internal explosive (reduced from before).
Corrected a problem in WeGo mode that sometimes caused vehicle passengers to rotate forward when they should not.
TCP/IP "chat" text is easier to see clearly.
Teams that are part of a squad properly retain their setup positions from the editor.
SPW 250/10 and 251/9 halftrack loaders perform correctly when vehicle is buttoned.
Wood bunkers are a bit tougher to knock out.
Corrected a problem that sometimes gave on-map artillery the ability to shoot through intervening terrain.
Corrected a problem that sometimes incorrectly restricted on-map artillery from firing smoke missions.
Targeting a TRP directly using the mouse works correctly.
Corrected a problem that occasionally caused a destroyed building to have "floating" rubble.
Prone soldiers on a slope angle their bodies correctly.
Bolt-action rifles properly show the spent casing ejected when the bolt is operated.
Corrected an issue with command & control values being promptly updated when splitting a squad.
Tiny explosions don't damage tank tracks so much.
Corrected some AI issues that caused soldiers to move away from their teams, or caused the team to be "stuck" and not move when they should.
In the editor, hedges allow co-placement of trees like bocage does.
Light wounds to crew are slightly more likely to cause AFV bailout.
Corrections made to Luftwaffe and Waffen SS camouflage helmets.
Updated graphical shaders.
Updated vehicle models (Commonwealth module): Wespe, PzII Lynx, Marder I, King Tiger, Jagdpanther, Cromwell, Churchill.
On the Mac side, there were Mac specific graphical and stability fixes:
Fixed "blockheads" problem.
Increased performance significantly for most Macs.
Fixed some bugs that were keeping Combat Mission from starting on some Macs.
Improved compatibility with some integrated Mac video cards.
Fixed "flickering icons" for most Macs.
Fixed some Mac-specific crash bugs.
NEW v1.10 GAME FEATURES
This patch will update your CMBN game to v1.10, which includes many enhancements and improvements. Below is a list of some of the new v1.10 game features.
Soldiers make better use of demo charges against vehicles at close range.
When vehicles bog down, it's now more likely to be temporary.
Corrected a problem where gunners would sometimes aim too low and repeatedly hit intervening ground short of the target.
Computer-player troops automatically take additional stored weapons and ammo with them when dismounting from vehicles.
Halftrack gunners will "sit" when the vehicle buttons up.
Dispersion pattern of mortar shells is more realistic.
Dismount command may be given to multi-unit groups.
In campaigns, units won't go into the next battle without a leader due to a previous casualty.
Enemy mortars are a little easier to spot when they fire.
Corrected a problem where frame rate could affect the cover offered by buildings.
Vehicles are more likely to button up when they take a crew casualty.
Computer player is more effective at breaching walls and bocage.
It's more difficult to suppress the occupants of a bunker.
Targeting an enemy unit by clicking its icon works properly when some LOS is blocked.
Corrected a problem that caused deployed soldiers to move around too frequently, especially inside trenches and buildings.
Corrected some problems with soldiers moving across narrow bridges.
Corrected a problem that caused halftracks sometimes to refuse to move across wall breaches.
Pre-battle intelligence icons don't slowly fade during setup.
Scenarios load faster when 3D Texture Quality option is set to Balanced or any faster option. If you notice any decrease in visual quality, simply increase this option one level higher in quality.
New editor feature lets you move flavor objects around more easily. In map preview, ALT-click on a flavor object (Option-click on the Mac) and the next map click will place the (previously) ALT-clicked object at the location of the second click.
Single barbed wire units remember their facing in the editor.
In the editor, when units are purchased they will try to set up by default inside friendly setup zones if the zones have already been created.
Made changes that should reduce the occurrence of Out of Memory crashes.
Allowed for the use of up to 4GB of RAM, dependent on the user's operating system and settings.
Corrected a problem where units driving near ditches would bog too easily.
THX for the head-up :)
actually i was expecting the 2.0 patch (with a $10 price tag) that brings Normandy to Italy standarts ... its overdue!)
A big thank you to Bismarck for the heads up, and a big thank you to Battlefront for supporting their product so well. 8)
I'm confused, I thought the 2.0 patch was next thing on the list for CMBN? Is it just me or why would anyone buy CMBN until the 2.0 version is released? I might buy one of these games if I knew what the hell I was buying and the future expansions & upgrades (purchased required) were for them! Still nothing official on the future expansion plans for CMFI, will the future expansions take us to 1945 or just end in 1944 ???
Quote from: SgtRock on December 07, 2012, 12:39:47 PM
I'm confused, I thought the 2.0 patch was next thing on the list for CMBN? Is it just me or why would anyone buy CMBN until the 2.0 version is released? I might buy one of these games if I knew what the hell I was buying and the future expansions & upgrades (purchased required) were for them! Still nothing official on the future expansion plans for CMFI, will the future expansions take us to 1945 or just end in 1944 ???
Facebook: "The v2.0 Upgrade for Normandy (not a patch, it's not gong to fix any issues, rather add new features, namely those from the v2.0 engine that is already included in CM:Fortress Italy) is not far out. Fingers crossed for a release next week!"
De aware that the patch may create a subfolder -Battlefront/Combat Mission Battles for Normandy/Combat Mission Battles for Normandy- that kills the install. Just delete the second folder in the path.
Quote from: Bismarck on December 07, 2012, 01:39:48 PM
De aware that the patch may create a subfolder -Battlefront/Combat Mission Battles for Normandy/Combat Mission Battles for Normandy- that kills the install. Just delete the second folder in the path.
I must be lucky :D. For once I didn't have Norton 360 screw up my install and delete the main .exe as it did with CMFI v1.01 (and that was a pain to fix - thanks Symantec! >:().
Quote from: Bismarck on December 07, 2012, 11:29:30 AM
Bolt-action rifles properly show the spent casing ejected when the bolt is operated.
How cool is that! 8)
Quote from: Boggit on December 07, 2012, 02:04:26 PM
Quote from: Bismarck on December 07, 2012, 01:39:48 PM
De aware that the patch may create a subfolder -Battlefront/Combat Mission Battles for Normandy/Combat Mission Battles for Normandy- that kills the install. Just delete the second folder in the path.
I must be lucky :D. For once I didn't have Norton 360 screw up my install and delete the main .exe as it did with CMFI v1.01 (and that was a pain to fix - thanks Symantec! >:().
How did you fix it? I just patched CMFI to 1.01 and had my exe deleted as well. I uninstalled the game this morning and was going to try reinstalling at some point soon.
Quote from: Ubercat on December 07, 2012, 09:14:22 PM
Quote from: Boggit on December 07, 2012, 02:04:26 PM
Quote from: Bismarck on December 07, 2012, 01:39:48 PM
De aware that the patch may create a subfolder -Battlefront/Combat Mission Battles for Normandy/Combat Mission Battles for Normandy- that kills the install. Just delete the second folder in the path.
I must be lucky :D. For once I didn't have Norton 360 screw up my install and delete the main .exe as it did with CMFI v1.01 (and that was a pain to fix - thanks Symantec! >:().
How did you fix it? I just patched CMFI to 1.01 and had my exe deleted as well. I uninstalled the game this morning and was going to try reinstalling at some point soon.
I did an explanation on the problem and how to get around it and sent it to Battlefront Support. I think there is a link on the website somewhere for it. But as it's you Ubercat :), I'll save you time and cut and paste from the note I have on my PC, viz:
**WARNING** Norton 360 notes for Battlefront CNBN: Commonwealth Bundle
Here is the precise workaround that your
customers need to use to avoid Norton deleting the CMBN Commonwealth files
at download and subsequently at installation. I've tested it through bitter
experience and this solution works:
If your customer has Norton installed they must first set up a download
folder for the game and an install folder for when the bundle has
downloaded.
Then go to the Norton 360 menu screen and click:
1. Settings
2. Antivirus
3. Scans and Risks
4. Under "Items to exclude from scans" click configure
5. Click Add and then browse the install and apply it
Do the same for the download folder
6. Under "Items to exclude from Auto-Protect and SONAR Detection" click
configure
Click Add and then browse the install and apply it
Do the same for the download folder
That's it. You can now download and install.Ubercat, I hope that solves the problem for the download. I should add that with the CMFI experience I had, I needed to re-install to get the .exe file back, then go through the same process as above for the Combat Mission game folder, since the .exe was still being deleted when I applied the patch. In the end I copied the .exe elsewhere whilst I tried to fathom this out. I know how frustrating you'll have found this. 8)
BTW I'd hasten to add that this is a Norton 360 issue and not a Battlefront one. I complained to Symantec about this on the first occasion I had the problem. I gather that Martin at Battlefront's support did so as well. Battlefront.com are "approved" as a safe site by Symantec, yet gamers have this problem due to the "reputation" program Norton runs. It clearly doesn't make much distinction between good and bad. To help the Battlefront game community, I'd suggest you complain to Symantec in the hope that if they get enough complaints, then they might actually listen.
Thanks!
So for the install folder, I should probably just create the same folder that the game itself would be creating to install itself to. And then during the install, Norton would exclude that folder from skullduggery.
I have CMFI on disk, so in that case I'm guessing the D/L folder would just be for the patch?
That is good news that the version 2.0 is not far off. I would like to purchase Normandy + Commonwealth bundle. But only once the 2.0 features is added.
Only thing it Battlefront don't do Xmas sales, or do they?
Which CM will get the NA theater?
I don't think there has been talk about a NA theatre yet.
Next up is Market Garden for CMBN. AFAIK there has been no talk about IF or WHAT other modules are going to entail (CMFI or CMBN). Feel free to correct me if I am wrong.
Quote from: Staggerwing on December 08, 2012, 12:07:11 PM
Which CM will get the NA theater?
someone has done a great Tunisia patch, but i havent heard anything at all pointing toward Africa
The original CM3 had some Tunisian and Sicily scenario's which were pretty good.
I was hoping more for entrenched Aussies, Semoventas, and helmets with black feathers, that sort of thing.
Quote from: Boggit on December 08, 2012, 09:27:30 AM
Quote from: Ubercat on December 07, 2012, 09:14:22 PM
Quote from: Boggit on December 07, 2012, 02:04:26 PM
Quote from: Bismarck on December 07, 2012, 01:39:48 PM
De aware that the patch may create a subfolder -Battlefront/Combat Mission Battles for Normandy/Combat Mission Battles for Normandy- that kills the install. Just delete the second folder in the path.
I must be lucky :D. For once I didn't have Norton 360 screw up my install and delete the main .exe as it did with CMFI v1.01 (and that was a pain to fix - thanks Symantec! >:().
How did you fix it? I just patched CMFI to 1.01 and had my exe deleted as well. I uninstalled the game this morning and was going to try reinstalling at some point soon.
I did an explanation on the problem and how to get around it and sent it to Battlefront Support. I think there is a link on the website somewhere for it. But as it's you Ubercat :), I'll save you time and cut and paste from the note I have on my PC, viz:
**WARNING** Norton 360 notes for Battlefront CNBN: Commonwealth Bundle
Here is the precise workaround that your
customers need to use to avoid Norton deleting the CMBN Commonwealth files
at download and subsequently at installation. I've tested it through bitter
experience and this solution works:
If your customer has Norton installed they must first set up a download
folder for the game and an install folder for when the bundle has
downloaded.
Then go to the Norton 360 menu screen and click:
1. Settings
2. Antivirus
3. Scans and Risks
4. Under "Items to exclude from scans" click configure
5. Click Add and then browse the install and apply it
Do the same for the download folder
6. Under "Items to exclude from Auto-Protect and SONAR Detection" click
configure
Click Add and then browse the install and apply it
Do the same for the download folder
That's it. You can now download and install.
Ubercat, I hope that solves the problem for the download. I should add that with the CMFI experience I had, I needed to re-install to get the .exe file back, then go through the same process as above for the Combat Mission game folder, since the .exe was still being deleted when I applied the patch. In the end I copied the .exe elsewhere whilst I tried to fathom this out. I know how frustrating you'll have found this. 8)
BTW I'd hasten to add that this is a Norton 360 issue and not a Battlefront one. I complained to Symantec about this on the first occasion I had the problem. I gather that Martin at Battlefront's support did so as well. Battlefront.com are "approved" as a safe site by Symantec, yet gamers have this problem due to the "reputation" program Norton runs. It clearly doesn't make much distinction between good and bad. To help the Battlefront game community, I'd suggest you complain to Symantec in the hope that if they get enough complaints, then they might actually listen.
You can also just turn off the auto protect function for as long as you take to do it. This is what deletes the file. The reputation feature of their system has cause me more headaches than it solved. I would be interested to know just how many people have to log a use of the file for it to be safe. the system only acts on a file at the time its being written to disk not after.
All you need to do is go into norton latest scans look for quaritine or something like that files and then restore. Done and done.
Quote from: Bison on December 08, 2012, 04:37:48 PM
All you need to do is go into norton latest scans look for quaritine or something like that files and then restore. Done and done.
Only sometimes the Norton rubbish doesnt send it to quarantine at all - it deletes it completely so you cant find it. the explanation being that given the system has no idea what the file is the safest course for it is to completely remove all trace of the file. It did this with the commonwealth file on the 1.10 update - had to reinstall the whole thing.
It's diffinately possible but I know is that is all it took to recover the .exe files. I also had to do the same thing with MS essentials.
Quote from: Bison on December 08, 2012, 04:50:03 PM
It's diffinately possible but I know is that is all it took to recover the .exe files. I also had to do the same thing with MS essentials.
Yeah - nortn seems to have a mind of its own. Frankly I hate it but have a three year subscription. I am sure it also slows down my browsing.
Quote from: Bismarck on December 07, 2012, 01:39:48 PM
De aware that the patch may create a subfolder -Battlefront/Combat Mission Battles for Normandy/Combat Mission Battles for Normandy- that kills the install. Just delete the second folder in the path.
I got it and it all worked and I actually saw some of the fixes in action: better models, troops properly aligned with slopes.
British Battalion HQ tanks seem pretty lucky. I had a Churchill Battalion HQ tank with a 75mm gun knock out a Jadgpanzer with a quick flank shot and then get the Marder in one test I tried. At least that showed that 3 models were improved visually.
Quote from: Ubercat on December 08, 2012, 09:53:11 AM
Thanks!
So for the install folder, I should probably just create the same folder that the game itself would be creating to install itself to. And then during the install, Norton would exclude that folder from skullduggery.
I have CMFI on disk, so in that case I'm guessing the D/L folder would just be for the patch?
I'm in the same situation. I'd make sure that you do this for the CM/CMFI/ folder. D/L to the folder an execute it from there. If Like me you store patches for reuse - make sure that when you store the patch you exclude it from scans etc to avoid inadvertently having it delete during a general virus scan.
Quote from: Zulu1966 on December 08, 2012, 04:46:41 PM
Quote from: Bison on December 08, 2012, 04:37:48 PM
All you need to do is go into norton latest scans look for quaritine or something like that files and then restore. Done and done.
Only sometimes the Norton rubbish doesnt send it to quarantine at all - it deletes it completely so you cant find it. the explanation being that given the system has no idea what the file is the safest course for it is to completely remove all trace of the file. It did this with the commonwealth file on the 1.10 update - had to reinstall the whole thing.
This happened to me first time round, before I worked out a fix for the thing. Bloody annoying! >:(