Ultradave

We had M561 Gama Goats for our artillery prime movers. People would swear you can't get one stuck, 6x6, super low gear, articulated, swimmable. 
We proved them wrong. 🤣  Getting that one unstuck would have greatly exceeded the time limit of a CM game.
Not to say one couldn't be done in the time frame of a game, but in most cases, a lot of your units on the map are under observation/fire. It would be a dicey situation. 
Dave
PS - mostly Goats were pretty awesome, that double low range 6x6 drive could handle almost anything. Almost.
https://en.wikipedia.org/wiki/Gama_Goat
We need them in whatever CW module covers having Abn troops 🙂  Just because they are weird.
 

We had M561 Gama Goats for our artillery prime movers. People would swear you can't get one stuck, 6x6, super low gear, articulated, swimmable. 
We proved them wrong. 🤣  Getting that one unstuck would have greatly exceeded the time limit of a CM game.
Not to say one couldn't be done in the time frame of a game, but in most cases, a lot of your units on the map are under observation/fire. It would be a dicey situation. 
Dave
PS - mostly Goats were pretty awesome, that double low range 6x6 drive could handle almost anything. Almost.
https://en.wikipedia.org/wiki/Gama_Goat
We need them in whatever CW module covers having Abn troops 🙂  Just because they are weird.
 

Thanks. More than 70km2 of maps to fight over in this Battle Pack. I'm still creating two more smaller maps for two scenarios. Using a lot of BIGOT maps from 1944 and aerial photos for reference. Some master maps will have variants that will also be provided with the historical German Fortifications placed and ready to go. (<-- That took a while...)
As per last year's bones on the pack, geographically the fighting is focused on the Utah Beach area itself and the area heading south towards and beyond Carentan. All scenarios/campaigns occur between 00:05 hours on 6th of June through to the evening of the 13th of June. Don't expect all of them to be brutal slog fests, particularly the D-Day ones where the Allies at times had significant advantages. I'm going for more of a focus on narrative and experiencing that first week coming off Utah Beach rather than slug fests designed for competitive tournament play. (Master Maps are there if you want to create your own matches though). If you play the pack chronologically and come out the other end content and with a greater appreciation of the challenges the forces faced, then I've done my job.  
The content in this part of the Normandy theatre, though popular, couldn't be created by BF as part of the CMBN base game given the absence of Fallschirmjager and Waffen SS forces in the WW2 titles at the time.

CMFB Downfall module is an instant buy.
CMBN Utah Beach BP is an instant buy.
CMFI BP1 is an instant buy.
CMCW BAOR module is an instant buy.
Already registered for @Mr.X's CMRT BP.
And almost forgot, @Paper Tiger CMSF2 Gung Ho! Campaign and his updated Road To Montebourg Campaign.
Looks like I'm going to have to clear my busy social calendar for the rest of the year! 🤣

I had a section chief who, after a phone call with Naval Reactors told us, "10 years from now he won't remember you were late, but he WILL remember if you were wrong, forever." 
My favorite boss I had in 38 years at EB. Of course we always tried our best to hit the deadlines, but not at the expense of being correct. It was nuclear submarine reactor plant design, after all. Incorrect is not an option.
Dave

There will be a patch, which isn't issued yet, then it will work. The content isn't in the current FB install. 
I think there may have been this language confusion with a previous release. The language seems to be written assuming the patch had already been issued.

Dave

There will be a patch, which isn't issued yet, then it will work. The content isn't in the current FB install. 
I think there may have been this language confusion with a previous release. The language seems to be written assuming the patch had already been issued.

Dave

I had a section chief who, after a phone call with Naval Reactors told us, "10 years from now he won't remember you were late, but he WILL remember if you were wrong, forever." 
My favorite boss I had in 38 years at EB. Of course we always tried our best to hit the deadlines, but not at the expense of being correct. It was nuclear submarine reactor plant design, after all. Incorrect is not an option.
Dave

I had a section chief who, after a phone call with Naval Reactors told us, "10 years from now he won't remember you were late, but he WILL remember if you were wrong, forever." 
My favorite boss I had in 38 years at EB. Of course we always tried our best to hit the deadlines, but not at the expense of being correct. It was nuclear submarine reactor plant design, after all. Incorrect is not an option.
Dave

This fixed my problem completely. All units are now named correctly. Thanks for the efforts in resolving this. 

I had a section chief who, after a phone call with Naval Reactors told us, "10 years from now he won't remember you were late, but he WILL remember if you were wrong, forever." 
My favorite boss I had in 38 years at EB. Of course we always tried our best to hit the deadlines, but not at the expense of being correct. It was nuclear submarine reactor plant design, after all. Incorrect is not an option.
Dave

It's not. HE rounds don't get converted to Smoke in real life. And there *should* be enough fuzes for all the rounds, regardless of what types. We usually had extra fuzes. I think this is on the list of things to fix somewhere. I'll try to search for it.
Dave

Both Jeff Smith and I tested this. I checked several scenarios and so did he, and it fixed the problem. Also, the "new" 1.07 .brz really isn't new and untested. It's just the one from the Windows version and that has been working fine. There was just something corrupted about the Mac installer. I wouldn't worry. If it doesn't work, well, it didn't work before. 🙂
If you are still on 1.06, then do this:
Relabel the CW directory to "Combat Mission Cold War - 1.06" or something like that , just so it's not the default installation name.
Download a fresh 1.07 CW full installer
Install using defaults. 
Don't even try to run it yet, but replace the 1.07 .brz file with the new one.
Now you can run it.
If it doesn't work, just delete that whole installation and go back to using 1.06 (it will work).
Dave
 

Yes, to 1-4. Entries are categorized by game, by severity, (like game-breaking down to minor graphics or QOL). There's also a way to indicate it applies to all games. And the "by game" is broken down by version, so that when a new patch is being tested, bugs can be categorized specifically to the new version. 
I don't think anyone posts an issue that would apply to number 5. Usually, in the beta forum there is some discussion if it's an oddball or potentially either non-fixable or working as designed prior to posting, but pretty much the beta testers know when they reproduce something that they just go post it without a bunch of back and forth discussion, maybe just a heads up that "I found these 5 issues and posted a Mantis report for each", so there isn't duplication. 
Then there is a robust search tool, to go look at status, or use keywords and choices to see if something is already posted. 
Hope that helps.
Dave

It's not. HE rounds don't get converted to Smoke in real life. And there *should* be enough fuzes for all the rounds, regardless of what types. We usually had extra fuzes. I think this is on the list of things to fix somewhere. I'll try to search for it.
Dave

In other news, I owe you a turn. I'll get right on it!!
Dave

Yes, to 1-4. Entries are categorized by game, by severity, (like game-breaking down to minor graphics or QOL). There's also a way to indicate it applies to all games. And the "by game" is broken down by version, so that when a new patch is being tested, bugs can be categorized specifically to the new version. 
I don't think anyone posts an issue that would apply to number 5. Usually, in the beta forum there is some discussion if it's an oddball or potentially either non-fixable or working as designed prior to posting, but pretty much the beta testers know when they reproduce something that they just go post it without a bunch of back and forth discussion, maybe just a heads up that "I found these 5 issues and posted a Mantis report for each", so there isn't duplication. 
Then there is a robust search tool, to go look at status, or use keywords and choices to see if something is already posted. 
Hope that helps.
Dave

Any large scale paradrop these days requires much more complete local air superiority than used to be the case to have a chance of success. And the term local is much broader than say, 30 years ago during the Cold War. 
1) You have to have enough fighter support to prevent enemy fighters from breaking through to your transport planes.
2) You have to suppress local AA defenses. Even in the Cold War period extensive deployment of MANPADS was just beginning. 
3) You have to suppress long range AA missile systems. That means a *huge* effort at SEAD in advance of the airdrop, due to the long range of many of today's AA missiles. 
Neither Ukraine or Russia have the assets to do this right now, especially Ukraine, but I seriously doubt Russia can do it either. My opinion is that the US would have a very difficult time of it if we were fighting in that theatre. 
Dave

Apple is eventually eliminating support for OpenGL. My guess would be there is no further work going on at Apple to do anything to better accommodate OpenGL graphics, so what's there is all there will be. I will say my new-ish M2 MacBook Pro with all its graphics processors does pretty well. The difference to my old one (2018 i5) is staggering. The map is rendered much farther out and camera movement is nice and smooth. Even the initial setup of "The Citadel" in CW is useable (couldn't move the camera before with the old MacBook Pro.
Dave

Note the pictures lower in the article of the NON burned out vehicles with MSF in large red letters on the hoods and the MsF logo and name along the side. Plenty large enough to see. These are recognized worldwide, never change, and the burned out vehicles at the top are that way BECAUSE the IDF came back after the fact and destroyed them... at the clinic MsF runs, which is a known location. 
So no. No passes. No excuses. Note also that MsF took 2 weeks to make sure their accusations were accurate.
Dave

Quoting myself because I finally remembered to go look again for the account, detailed here in a statement by MsF. There seems no doubt here that they were deliberately targeted, on more than one occasion, and their mission and also evacuation obstructed. 
I'm surprised this did not get more press than it did at the time. Perhaps because when they issued this statement they had carefully investigated it themselves for 2 weeks so it was "old news". 
I'd be very surprised if anyone accused MsF of having any agenda, or harbouring any Hamas sympathizers. They do good work all over the world, often in danger to themselves, and they are CLEARLY recognizable. Everyone knows who they are without ambiguity. 
Well, I'm giving it press, I guess, for what that's worth. Again it falls in the category of making things worse, not better.
https://www.doctorswithoutborders.org/latest/msf-convoy-attack-gaza-all-elements-point-israeli-army-responsibility
Dave

I did see those vehicles lower down when I was reading. They look like they were the ones tore up by a bulldozer.
That's horrible and an attempted cover up makes it worse.  I want to hear what the IDF has to say for itself.  War is bad but attacking doctors on purpose... That's just horrible. Why??? And I just don't see the motive.  What could possibly cause them to do that?  That makes Israel look like Hamas, the ones they are supposed to be fighting against.

Note the pictures lower in the article of the NON burned out vehicles with MSF in large red letters on the hoods and the MsF logo and name along the side. Plenty large enough to see. These are recognized worldwide, never change, and the burned out vehicles at the top are that way BECAUSE the IDF came back after the fact and destroyed them... at the clinic MsF runs, which is a known location. 
So no. No passes. No excuses. Note also that MsF took 2 weeks to make sure their accusations were accurate.
Dave

Quoting myself because I finally remembered to go look again for the account, detailed here in a statement by MsF. There seems no doubt here that they were deliberately targeted, on more than one occasion, and their mission and also evacuation obstructed. 
I'm surprised this did not get more press than it did at the time. Perhaps because when they issued this statement they had carefully investigated it themselves for 2 weeks so it was "old news". 
I'd be very surprised if anyone accused MsF of having any agenda, or harbouring any Hamas sympathizers. They do good work all over the world, often in danger to themselves, and they are CLEARLY recognizable. Everyone knows who they are without ambiguity. 
Well, I'm giving it press, I guess, for what that's worth. Again it falls in the category of making things worse, not better.
https://www.doctorswithoutborders.org/latest/msf-convoy-attack-gaza-all-elements-point-israeli-army-responsibility
Dave

Note the pictures lower in the article of the NON burned out vehicles with MSF in large red letters on the hoods and the MsF logo and name along the side. Plenty large enough to see. These are recognized worldwide, never change, and the burned out vehicles at the top are that way BECAUSE the IDF came back after the fact and destroyed them... at the clinic MsF runs, which is a known location. 
So no. No passes. No excuses. Note also that MsF took 2 weeks to make sure their accusations were accurate.
Dave