Howler

If I may - there's nothing wrong with loose ETAs as long as they are in the future. Push the ETA out further before you slip past it. The worst that happens is that you deliver "early" as in something intended for a month(s) down the road is out next week instead.
It's easier to be forgiven for delivering sooner. Sure, you'll have someone bitch that you said June but actually released it April 30th. But most will forgive.
The reverse isn't true as these, now, 23 pages of posts attest to.
All the best. Always.

Whining has more to do with no information, let alone a simple revised ETA, being provided. It's not rocket science - revise a slipped March deadline by providing a *timely* update of... July or October or early-2020 [pick a date]. Posting every other month that we're almost there isn't an effective way of communicating with your customers.
It's not that complicated. What you want to avoid is the mishandling of expectations. Said expectations being set initially, not by the customer, but by the developer.
It's not difficult... post an an update before you blow past the last one. Otherwise, you mangle expectations.
Anyhow, it is what it is. It's obviously more effective to be reactive rather than to be proactive with deliverables.
Plus, it's lot more fun to be wading through 22 pages of my useless posts than it would be to reference a locked thread of *timely* updates from the developer.
Now let's back to eating our young...

Whining has more to do with no information, let alone a simple revised ETA, being provided. It's not rocket science - revise a slipped March deadline by providing a *timely* update of... July or October or early-2020 [pick a date]. Posting every other month that we're almost there isn't an effective way of communicating with your customers.
It's not that complicated. What you want to avoid is the mishandling of expectations. Said expectations being set initially, not by the customer, but by the developer.
It's not difficult... post an an update before you blow past the last one. Otherwise, you mangle expectations.
Anyhow, it is what it is. It's obviously more effective to be reactive rather than to be proactive with deliverables.
Plus, it's lot more fun to be wading through 22 pages of my useless posts than it would be to reference a locked thread of *timely* updates from the developer.
Now let's back to eating our young...

Whining has more to do with no information, let alone a simple revised ETA, being provided. It's not rocket science - revise a slipped March deadline by providing a *timely* update of... July or October or early-2020 [pick a date]. Posting every other month that we're almost there isn't an effective way of communicating with your customers.
It's not that complicated. What you want to avoid is the mishandling of expectations. Said expectations being set initially, not by the customer, but by the developer.
It's not difficult... post an an update before you blow past the last one. Otherwise, you mangle expectations.
Anyhow, it is what it is. It's obviously more effective to be reactive rather than to be proactive with deliverables.
Plus, it's lot more fun to be wading through 22 pages of my useless posts than it would be to reference a locked thread of *timely* updates from the developer.
Now let's back to eating our young...

Whining has more to do with no information, let alone a simple revised ETA, being provided. It's not rocket science - revise a slipped March deadline by providing a *timely* update of... July or October or early-2020 [pick a date]. Posting every other month that we're almost there isn't an effective way of communicating with your customers.
It's not that complicated. What you want to avoid is the mishandling of expectations. Said expectations being set initially, not by the customer, but by the developer.
It's not difficult... post an an update before you blow past the last one. Otherwise, you mangle expectations.
Anyhow, it is what it is. It's obviously more effective to be reactive rather than to be proactive with deliverables.
Plus, it's lot more fun to be wading through 22 pages of my useless posts than it would be to reference a locked thread of *timely* updates from the developer.
Now let's back to eating our young...

Whining has more to do with no information, let alone a simple revised ETA, being provided. It's not rocket science - revise a slipped March deadline by providing a *timely* update of... July or October or early-2020 [pick a date]. Posting every other month that we're almost there isn't an effective way of communicating with your customers.
It's not that complicated. What you want to avoid is the mishandling of expectations. Said expectations being set initially, not by the customer, but by the developer.
It's not difficult... post an an update before you blow past the last one. Otherwise, you mangle expectations.
Anyhow, it is what it is. It's obviously more effective to be reactive rather than to be proactive with deliverables.
Plus, it's lot more fun to be wading through 22 pages of my useless posts than it would be to reference a locked thread of *timely* updates from the developer.
Now let's back to eating our young...

Whining has more to do with no information, let alone a simple revised ETA, being provided. It's not rocket science - revise a slipped March deadline by providing a *timely* update of... July or October or early-2020 [pick a date]. Posting every other month that we're almost there isn't an effective way of communicating with your customers.
It's not that complicated. What you want to avoid is the mishandling of expectations. Said expectations being set initially, not by the customer, but by the developer.
It's not difficult... post an an update before you blow past the last one. Otherwise, you mangle expectations.
Anyhow, it is what it is. It's obviously more effective to be reactive rather than to be proactive with deliverables.
Plus, it's lot more fun to be wading through 22 pages of my useless posts than it would be to reference a locked thread of *timely* updates from the developer.
Now let's back to eating our young...

Totally understand that Michael, and really appreciate the effort you and others put into testing for us all to enjoy the finished product. It can be really difficult balancing work and family, and finding time for this hobby can be extremely hard sometimes.
 
I really am appreciative of the work you and BFC do to bring us this very unique game, as mentioned several times before, my only wish is for a little communication. If there is a delay then fine, but if someone could just post a little line up saying something like 'run into problems with TO&E, no release before xxxx date' then that would satisfy me. Its just that beginning of March was mentioned and so i find myself checking everyday to see if there has been any news, when really a little message to say 'delayed at least a month' would have sufficed.
Obviously we have now had an update so im happy again for a while 😉
 
regards
 
slippy

Again... beating a dead horse....
Roadmap
deliverable A         date X deliverable B         date Y deliverable C         date Z Don't need to know details.
Absolutely prefer periodic updates  that are better than quarterly. We seem to be no farther ahead than we were when SF2 was released in December...
This wouldn't be a problem if this was known months ago. I'm not sure what to make of an update that is even less informative than the previous one issued last Jan/Feb.

Wow, looking at all these screenies of RT glory got me to do some more tweaking of my color, gamma, and saturation profiles. To fully enjoy the great work of our talented modders one must tinker with a host of various monitor, graphics card, and post processor frag settings, all of which impact each other... At first I wanted to pull my hair out but focusing on the skin or flesh tone color as a visual base made it a bit easier. So I started there. Still tinkering with the Nvidia digital vibrance and gamma settings as I'm using a base RGB icm setting on the old AOC 2560 monitor. It has a rep for being a bit washed out in color display. Anyway, I think I may have finally gotten to a point of being satisfied with the results. Eye candy for all.
 
 

A scenery shot and Heer closeup.
 

Again... beating a dead horse....
Roadmap
deliverable A         date X deliverable B         date Y deliverable C         date Z Don't need to know details.
Absolutely prefer periodic updates  that are better than quarterly. We seem to be no farther ahead than we were when SF2 was released in December...
This wouldn't be a problem if this was known months ago. I'm not sure what to make of an update that is even less informative than the previous one issued last Jan/Feb.

From a current PBEM as the Syrians defending against the Dutch. Veteran Syrian troops with lots of ATGMs have proven themselves to be quite capable.



Canadian armour unleashes on fleeing insurgents.

Again... beating a dead horse....
Roadmap
deliverable A         date X deliverable B         date Y deliverable C         date Z Don't need to know details.
Absolutely prefer periodic updates  that are better than quarterly. We seem to be no farther ahead than we were when SF2 was released in December...
This wouldn't be a problem if this was known months ago. I'm not sure what to make of an update that is even less informative than the previous one issued last Jan/Feb.

I'm curious, what game have you *ever* played that didn't have such bias?  There are limits to everything and everyone (yes, including the game designer) has an opinion. Why waste your time playing a scenario you don't enjoy. Skip it and play the next one. There's plenty of content to play through. Spare yourself the frustration.
 
Your point being what exactly? Ah, yes - it must be the game... the limitations... the fantasy...
Come back to it when your more comfortable with fine movement and the use of engineers within 'the realm of CM'.
Choose another scenario and come back to this one once you're more comfortable with the mechanics and their limitations. Again, there's plenty of scenarios that are more readily approachable.

😂😂 😂😂 Be funny if it was not all so disappointing and unnecessary though Michael, i can't think of another active game developer, that i follow,  that treats its loyal customers with such disdain, its really saddening and so easily solvable.

I knew I should have brought more ammo.

This thread is 19 pages long when it could've been simply a series a monthly posts from Steve outlining a road map with a simple date associated to each entry. The closer releases could even narrow it down to a day with the farthest ones to a simple year.  Like...
CMSF2 Canadian Campaign --- May 15, 2019
CMSF2 UK Campaign --- July 1, 2019
Patch CMBN   --- July 15, 2019
CMFI  Module - Rome to Victory --- Spring 2020
CMRT Module --- 2021
Lock the thread so we don't need to parse 19+ pages of off-topic posts. Do the introduction/PR work describing products in other thread elsewhere.
As someone said to me recently - it ain't rocket science and this isn't the 90's where customers are unaccustomed to the ways of computers. People nowadays appreciate a little transparency.
Personally, I don't want constant monthly patches. I prefer releases that are thoroughly vetted and ready when BFC says it's ready. I just don't understand how hard it is to simply assign (a made up)  date estimate to each entry in your already published product roadmap and auto-post the first of every month.
Anyhow, let's get back to this constructive thread where we eat our young...
 
 

Completely agree with this. The best way by far to clear a building is to blow it up. 
Rules of Engagement (ROE) change the tactics, techniques and procedures you are able to employ. Good ROE are designed to maximize a soldiers tactical flexibility in a given environment. Unfortunately, many ROE end up hurting the soldiers forced to work under their restrictive guidelines. Combat Mission accurately portrays this. In the mission you are describing, you have to modify your tactics given the restrictive ROE you must operate under. I wrote this post a while ago, which details one of the ways I try to take down a building if forced to manually clear it, though there are many other good points in the thread as well:
 

It's got nothing to do with rocket science. It's just common courtesy which, granted, seems to be not as common today.
You've chosen twice in this thread to be less than welcoming or helpful.
Learn... to.. let.. it...pass.
I won't be responding further as I have learned the above. I also don't have any particular axe to grind with you.
Be well,

This thread is 19 pages long when it could've been simply a series a monthly posts from Steve outlining a road map with a simple date associated to each entry. The closer releases could even narrow it down to a day with the farthest ones to a simple year.  Like...
CMSF2 Canadian Campaign --- May 15, 2019
CMSF2 UK Campaign --- July 1, 2019
Patch CMBN   --- July 15, 2019
CMFI  Module - Rome to Victory --- Spring 2020
CMRT Module --- 2021
Lock the thread so we don't need to parse 19+ pages of off-topic posts. Do the introduction/PR work describing products in other thread elsewhere.
As someone said to me recently - it ain't rocket science and this isn't the 90's where customers are unaccustomed to the ways of computers. People nowadays appreciate a little transparency.
Personally, I don't want constant monthly patches. I prefer releases that are thoroughly vetted and ready when BFC says it's ready. I just don't understand how hard it is to simply assign (a made up)  date estimate to each entry in your already published product roadmap and auto-post the first of every month.
Anyhow, let's get back to this constructive thread where we eat our young...
 
 

I hear you about the 19 pages.
Every time I see the ‘Holy blue dot of new posts’ appear I think this must be BFC posting about the actual patch instead of random banter I find instead. 
That does not please the Refresh Monkey God! 
I firmly believe this is the actual reason of the long wait.
So, please stop posting here gentlemen! Unless your offering to the Refresh Monkey God of course.

This thread is 19 pages long when it could've been simply a series a monthly posts from Steve outlining a road map with a simple date associated to each entry. The closer releases could even narrow it down to a day with the farthest ones to a simple year.  Like...
CMSF2 Canadian Campaign --- May 15, 2019
CMSF2 UK Campaign --- July 1, 2019
Patch CMBN   --- July 15, 2019
CMFI  Module - Rome to Victory --- Spring 2020
CMRT Module --- 2021
Lock the thread so we don't need to parse 19+ pages of off-topic posts. Do the introduction/PR work describing products in other thread elsewhere.
As someone said to me recently - it ain't rocket science and this isn't the 90's where customers are unaccustomed to the ways of computers. People nowadays appreciate a little transparency.
Personally, I don't want constant monthly patches. I prefer releases that are thoroughly vetted and ready when BFC says it's ready. I just don't understand how hard it is to simply assign (a made up)  date estimate to each entry in your already published product roadmap and auto-post the first of every month.
Anyhow, let's get back to this constructive thread where we eat our young...
 
 

This thread is 19 pages long when it could've been simply a series a monthly posts from Steve outlining a road map with a simple date associated to each entry. The closer releases could even narrow it down to a day with the farthest ones to a simple year.  Like...
CMSF2 Canadian Campaign --- May 15, 2019
CMSF2 UK Campaign --- July 1, 2019
Patch CMBN   --- July 15, 2019
CMFI  Module - Rome to Victory --- Spring 2020
CMRT Module --- 2021
Lock the thread so we don't need to parse 19+ pages of off-topic posts. Do the introduction/PR work describing products in other thread elsewhere.
As someone said to me recently - it ain't rocket science and this isn't the 90's where customers are unaccustomed to the ways of computers. People nowadays appreciate a little transparency.
Personally, I don't want constant monthly patches. I prefer releases that are thoroughly vetted and ready when BFC says it's ready. I just don't understand how hard it is to simply assign (a made up)  date estimate to each entry in your already published product roadmap and auto-post the first of every month.
Anyhow, let's get back to this constructive thread where we eat our young...
 
 

I'm working on a scenario about the Juno landings at Courseulles-sur-Mer. It will have a historic version as well as a couple of "what-if" variants. Most of the map is done and units in place, but I've hit a couple of snags and has the project on hold until the patch is released.