Collingwood
-
Posts
344 -
Joined
-
Last visited
Posts posted by Collingwood
-
-
OK thanks Michael, will wait for another patch then and go back to v 1.0. cheers
-
I've just patched (on Mac) to 1.01, and found something strange with a QB. I manually selected a mixed German force for a meeting engagement, 4 x StugIII and several platoons of infantry.
The problem is the Stugs refuse to obey any move orders. The infantry squads obey orders as usual, but the only movement I can get the stugs to perform is to change facing. It's like the crews are on strike.
I did get interrupted and had to save the game during deployment, before resuming it, but that wouldn't have affected anything would it? The armor isn't showing as being disabled or damaged at all.
I just tried a 2nd QB and this time got the computer to auto-select forces, and my armor moved out just fine, maybe something to do with the manual selection of forces in the first QB (?)
Has anyone else had this problem of armor not moving out? I spent so long setting the battle up, but gave up on it after 10 minutes of stationary armor.
-
-
Yep, I got your bug reports.
I'm still hunting for a 3000-equipped tester to help us out with that.Hi Phil, I have a MBP that arrived fresh one week ago, OSX 10.6.8, 8GB RAM, i7 @ 2.2GHz, Intel HD Graphics 3000 ... if there is any testing I can help with, happy to. Someone mentioned a crash-2-desktop on theirs, I have had a couple of those but that's in over a dozen hours of play.
cheers
-
Yay! Thanks very much Rambler. Nice work
-
I just uploaded it to the repository, and it's available for immediate download at GaJ's CMMods site
Great, but that link gives a page not found error, and I can't find your mod when searching via author or upload date
edit - link works now thanks!
-
Message for battlefront.com (Steve) - not on topic but not worth a new thread - your PM inbox is full Steve, so you can't receive any new PMs... cheers.
-
One of the reasons I like WeGo as well is relative spotting plays out more as I can't be the "God" spotter quite as much. You make your plans, hope for the best and try to sieze the opportunties you are presented. For 60 seconds you lose complete control of the action.
I love this aspect of the game too, relative spotting has greatly increased the unpredictability and drama of WeGo.
When it works it feels great, when it doesn't work you scream at your pixel truppen to not back into LOF of that AT gun you know is sitting in that treeline. (As I was doing yesterday as my Panther backed into LOF of a measly little 57mm AT gun that then provided my crew with additional ventilation holes.)
Last night the AI launched a perfectly timed mortar barrage in the space between a forest and a building I had ordered 3 squads to dash over to in separately timed runs. Squad after squad waited their turn to obediently run into the maelstrom and get chopped up in the rain of death. There was nothing I could do during that minute to tell them "Don't go yet! wait for the barrage to end!"
These are the uncontrolled moments when a battle can be lost, and I love it.
-
I don't know if this is a known issue - but last night I had the game consistently crash to desktop after a HE round from a Sherman accidentally destroyed a wooden footbridge. (The tank was not meant to be taking out the bridge but instead aiming at a building on the other side).
It took me a while to work out that's what was causing the crash during the action review phase. CTD occurred a few seconds after collapse of the bridge: changed orders to cease-firing with the tank, bridge remained intact, no more crash to desktop. Strangely enough a couple minutes later an enemy artillery round took out the same bridge (and nearly an entire squad) but this didn't crash the game.
I have saved the file in case it is helpful to the devs or testers. It was the OSX demo game, I have only just bought the full version so haven't had a chance to see if it still happens in the paid game.
Hardware if it helps any - MacBook Pro 2.2GHz Intel Core i7, OSX 10.6.8, 8GB RAM.
-
I've been waiting years for Battlefront to produce an OSX version of a game, and had almost given up. On a whim I checked the site recently and discovered a demo for CM:BN and was immediately hooked - as in start playing after dinner then realize it is after midnight and I have to get up in four hours time...
It was worth the wait for an OSX version. The demo alone was awesome, but my main reason for paying for the full version is to reward the developers for what would appear to be instantly the best wargame for OSX ever.
Thank you for making the game dual platform!
-
Hear hear, sticky this. Thank you dakuth! What a great tutorial/AAR. I had struggled for a couple nights with the demo until I watched this great video, and found my enjoyment and understanding of the game increased immensely - so much so that I decided to buy the game.
It was pleasant to hear a familiar accent too... cheers
I'm still hunting for a 3000-equipped tester to help us out with that.
QB Armor refuses to move
in Combat Mission Battle for Normandy
Posted
That's interesting, I patched to 1.01 and the startup screen showed 1.01, but I definitely didn't get any data in white lettering in the lower RH screen. So if I understand you correctly the missing fps info etc indicates that I did not have the latest patch despite downloading it a couple days after it was made available.
I will try re-downloading the patch and applying it to my fresh install of CMBN.
Is there any other way of telling from a downloaded patch that it is the "all new improved patch" ?