Erwin

Great mod. Are you going to combine this mod with the SYROPE mods? Korea is a lot more green and forested than CMSF terrain and with more water barriers.

Both Going to Town scenarios from the links above say DEMO in the title. So, no point d/l them into the full CMSF game scenario folder?

In terms of playability and fun, I agree about CMSF. There is more room for maneuver in more of the CMSF scenarios. CMBN feels claustrophobic and the scenarios seem mostly smaller, with most requiring straight ahead assaults with little opportunity for flanking maneuver. I would describe CMBN as more of a small scale/small map infantry wargame with armor very much in a supporting role. And some players here seem to prefer that. CM1 is more of a mech/armor game on large/huge maps with inf in support. CMSF is in the middle. Am hoping that the next CMBN modules, once we're out of the bocage, will open the game up to more maneuver and mech/armor fun. I hope we won't have to wait for the Eastern Front to see larger scenarios and campaigns. Of course the other tech issue is that CMBN is more resource hungry than CMSF, and LOT more than CM1. I get the feeling that only those fortunate to have high-end computers are able to tackle the few larger scenarios that are available in CMBN. Hopefully, BF can do something to optimize the engine so it can run more efficiently.

Many thanks. Between all the superb modders who upgraded the uniforms, the terrain and now the vehicles, CMBN looks like a new game. (Although I still think they all look a bit too sunny and should be a bit more dark and sinister, hehe...)

It would also be great to have some units gain experience between battles in a campaign. Or, the ability to give some high-performing units awards etc like in Silent Hunter. Now that we have such a greater detailed depiction of units, I have never understood the objections to this since battles could easily be weeks or even months apart. It would really make one identify with and care about one's men in a very "realistic" RL manner.

My saved setup definitely crashes when I try to load it. Is there an issue if I saved before patching and then tried to load the saved setup in the patched game?? I didn't have any tech issues with Utah Beach (it was even larger than FB I think and the slowness just got to me).

One thing CM teaches one is "never give up." So many times I thought I was losing only to having the situation radically turn around in the last ten minutes.

It's useful to save games at intervals so you can go back to that point and try for a different result to get to the alternative scenarios. (Hint: It's usually easier to get a "Lose" result.)

Possibly the tank got stuck in that position, and an enterprising PR wonk said, "Hey, get some troops on that thang and it'll make a great photo op!"

For what it's worth I was able to save my setup, but was never able to load the saved game. Either it won't work with the patched version of CMBN, or something else is up with this great-looking scenario. As an exercise try the Utah Beach monster scenario and see if you experience the same problems. I did not, altho' it was very slow to load. If you have problems with that it could be your computer hasn't the juice.

These mods just get better and better. And so many so suddenly. It's like the dam of creativity suddenly collapsed.

The question is why does the installer do something weird like double the last folder? I love the implication that it's somehow the users' fault hehe. It's obviously not something at least several of us here expected (like the Spanish Inquisition etc.).

This useful info ought to be sticky.

Thanks. For some reason the new .exe installed to a subfolder of the CMA folder rather than the main CMA folder. Pasting the contents of the new subfolder back into the main folder seems to have fixed the problem and 1.03 seems to be running fine now.

These are fabulous mods Aris. But, plz note that we really should not be able to see the hull through the bogie wheels so easily. Tracks are nearly always much more muddy/dirty.

One used to be able to destroy some vehicles/inf after creating a scenario in the first turn(s), then baking the game and let people play from there. That is one way to achieve a map with lots of destruction and death already in place. Is that no longer possible?

I had the same problem. In case this is helpful to others: I found that even though I had the correct path, the .exe file installed to a subfolder of the CMA folder instead of the main CMA folder. Moving the files in the subfolder to the main folder and replacing what was there fixed the issue and 1.03 CMA runs fine now.

Ok, you are correct, CMBN is not a good WW1 simulation. It's an amazingly wonderful, entertaining and yet frustrating sim that blends amazing detail with features that may or may not work properly, but one can't tell much of the time cos of inadequate documentation leaving so much room for "interpretation." Hence the vast amounts of discussion and opinionating on these forums. (Quite brilliant of the developers to come up with that formula actually.) And I say all of the above with genuine admiration and affection for the CM series.

Presumably a sound mod of a cloud of flies would be possible.

Re linking your machine to a TV, make sure you have a plenty long enough HDMI cable, so you're not stretching it like a trip wire. You will always regret not getting quite long enuff. (I got 25'.) Also, I found the best deal is to go online and buy direct from tech guys who make up the cables themselves. They are expensive from stores.

Beautiful work. Thank you.

If you check the BF Home page, it does not mention 1.03 is for the Mac.

I agree with all that was said. A common problem with the CM2 system scenarios is that just about every game involves the first 2/3 to 3/4 of the game spotting and figuring out where the enemy could be lurking (recon is fun, but uses very few units), then waiting (boring) while one calls in arty to kill em or smoke to disguise movement, followed by an intense last 20%-30% of the scenario when one actually gets to do fun stuff like "the attack" and gain the objectives. Sometimes, it feels like a (superb) WW1 game. But, it's an example of enhanced "realism" not necessarily creating enhanced enjoyment (for many of us). It's largely due to the fact that CMBN is much more of an inf game (with a little armor in support). Many of us enjoy armored/maneuver warfare with inf being in support. That may be the essential difference from CM1 in which it was easy for average systems to run pretty large armored scenarios on huge maps. I am looking forward to future modules which hopefully will open up the terrain and allow for more maneuver. But, I am concerned that with the much larger processing demands of CMBN, that we may still be stuck with relatively small maps and scenarios.

For what it's worth there does appear to be a problem with C2 at least with this campaign and it's being looked into. Blackcat: Re "making a fuss". It's just that without a decent manual one has no idea as to what is a feature or what is a bug. So, if mentioning that there are confusing/weird features in what is an otherwise superb game bothers you, then I do apologize for irritating you.

So... does that reflect reality in Normandy era US tank gunnery, or...?