SapperHarvey
-
Posts
15 -
Joined
-
Last visited
Posts posted by SapperHarvey
-
-
As far as I know, this game is set in 2008, before the M320's were widely issued. And the OCP uniform was issued only a few years ago if I recall correctly.
-
Haha, yeah apologises guys. IanL, you're right on the money, I was on mission 2 of the Task Force Thunder campaign, and just couldn't pull myself away
Was about to start mission 3..
-
Yeah, it's easily the fastest loading CM game for me, takes about 20 seconds to load into a battle. Some of the other WW2 titles take 3-4 minutes to load for me.
-
Ah, I had ALT+P originally before I edited it, lol. PIATpunk is right, its ALT+P. I always enable both of them on first start up of a new CM game. Another useful one I use, if I remember right, is Alt+M for brighter lighting during night battles if you find it a bit hard to see.
-
ALT+Z my man. You can check the hotkeys for various commands by clicking "MENU" in a battle and click "Hotkeys"
-
2 hours ago, Ultradave said:
I tried this and in the Mac version this happens with Passage to Wilcox and Alamo, but with the other scenarios, the shaders are on. This is true whether quitting and starting an new scenario in game or starting the game fresh and entering a scenario. Can you check whether your experience matches mine and is it on a PC or Mac?
Yeah, I can confirm this, Shader option works fine on the Marine beach landing and the British scenario, but the Alamo and Passage to Wilcox scenario has the shader option bug. It's apparently a bug with certain scenarios, some work, some don't. Again, not a big deal, just never noticed it before on other CM games I own and thought I'd mention it.
-
Same here, I'd definitely buy an updated version of CM:A.
-
Noticed that even with the shaders option set to ON, they are automatically off when entering a battle, have to manually turn them on with ALT-R.
Noticed in the Alamo scenario, that when setting the TPz Fuchs trucks to open up they will only stay open for a few minutes or so, even without being fired upon or having any enemy contact so you have to keep telling them to open up to use the MG3's.
-
Just a (?) minor bug report (?) I've noticed even when I have the shaders option set to On in the options, they are automatically off when I enter one of the battles, I have to manually turn them on with Alt-R. No big deal , just thought I'd report that.
-
Legends!
-
I remember playing this campaign, and this map, both of which have been really well done. Hopefully I'm not spoiling anything for anyone, but be aware of the Church steeple off in the distance, in the middle of town. I lost my recon units in the same general area.
-
Alright, can confirm everything is working fine now. I used the full 4-6 GB sized installers, uninstalled all of my CM games and started fresh. The 4.0 big bundle key worked on everything except CMRT which I then used my original key on and it worked.
Am I correct in assuming my old campaign saves will no longer work?
Thanks again Battlefront, was great to wake up on Christmas to this. Hopefully a CMSF or CMA rebuild to 4.0 is in the works!
@JUAN DEAG I got that same flashing problem, but only when I tried to run as Admin. Just double clicking brang up the prompt. Can't think of what would be blocking it besides anti virus.
-
I think that could be the case Cobetco, because if you run the versioncheck shortcut inside the Dir it comes up saying " Funny, your version wasn't yet released ;-)" so I guess we have to wait a day or two maybe..
-
Yeah, getting the same error on CMBN, have used the patch and reinstalled with the 4.0 full installer, same thing. about to try CMFB and see if it gives the same error.
Btw theres a file inside the install directory called "Activate New Products" which brings up the licence prompt, get an "invalid serial number" after putting in my licence key.
hummm patche 4, I need your opinion
in Combat Mission Battle for Normandy
Posted
Can someone point me in the direction of the 4.01 full installers? All I can find is the 4.0 full installer and the 4.01 patch for the various games.
I've also experienced some of this weird behaviour since installing 4.01. In the CMBN campaign "Kampfgruppe Engel" I noticed on the 3rd battle, the one where you have to recover the Tiger II and then do a fighting withdrawal off the map, I put a pre-start 81mm mortar (Harass, medium ammo expenditure) barrage on a hedgerow a few fields forward of the Tiger where I assumed there'd be US Infantry. So after the first few turns my infantry platoon was at the opposing hedgerow and after a few seconds spotted roughly two US infantry squads (casualties had been taken from the mortar barrage) which looked like they were cowering out in the middle of the field between the two hedgerows, where they were of course mowed down within seconds by my infantry.
I thought 'that is strange' and reloaded the mission and did the same thing again, but did not put a mortar barrage down on the US hedgerow, and when I arrived at the opposing hedgerow, there were no US infantry out cowering in the middle of the field, I then fired on the US hedgerow, to where I received return fire from roughly two squads of infantry.
I then started up my CMBN 3.xx version of the game and replayed the campaign up until this point again, and tried doing the same thing, both with the mortar barrage and without. This time the US Infantry did not route out towards my side of the map and into an open field and cower after the barrage, they stayed and either cowered/took cover behind the hedgerow or they retreated back towards the Tiger II (towards their own side of the map)I did not notice it on the first two battles of the campaign, although it is harder to see what the enemy is doing and how they're reacting to you in those fights.
I've also noticed squads seem to bug out a lot quicker when they're under fire, compared to CM 3.xx, just in general, different armies across different campaigns across different CM games, no specific situation or scenario.
That's all I've noticed as far as 'odd behaviour' goes since the patch.