Daveoreno

I don't know if other people are still having crashes but I think I might have found a quick and easy fix for the CTDs so I thought I'd post in this old thread in case it is useful for other people.
I got a new PC last summer with windows 10 and the game has kept crashing on me with a CTD with an uncanny regularity ever since. The game has always been rock solid and super stable before. It wasn't the end of the world because I only experienced these crashes after 2 hours, 2 hours and a half of play. But it was every session and it was bugging me a little.
I tried all the suggestions in this thread, toying with nvidia settings, having the exe in admin mode, excluding it from the anti virus etc. But no luck. I was about to try different drivers for my graphic card as a last resort because I don't particularly like updating these all the time just to gain 1-2 fps when all the other games I play work fine.
Then I right clicked on the game exe to access the properties and set it to launch in windows 8 compatibility mode. I have tested it for a week to make sure it wasn't just a fluke. I have had zero crashes since I did that.
 

I am a stalwart supporter of BFC, been playing the games for longer than I can remember. I made a modest contribution to the development of CMFI some years ago.
Yes, waiting for the patch has been unusually testing, but this game system has so many facets that even though I played less I still had a lot of fun making maps and designing scenarios, not to mention fun testing them.
 
These guys are a small team of extremely dedicated enthusiasts. They give 100%. I still haven't found anything remotely approaching their product for the kind of game play I appreciate. I have total confidence in their judgment and integrity. And I don't begrudge them for one minute the long gestation of this patch, or the confusion over exactly when it will be released.
Thank you Steve, thank you Charles, thank you everyone else who put their time and effort in bringing these games to us.
I've gone through a rough patch that has lasted nearly ten years so far. If and when I get back on my feet, I will be glad to lend a hand again. I hope it will be soon (can't give a precise date though... sorry, I couldn't resist that :-) ). In the mean time, I don't mind saying that playing your games has often been the only source of fun and relaxation for me, and a good way to avoid going mad during the long spells when real life got held up in limbo.

Definitely. That they don't even bother to take a few minutes to write a few lines about why the "before March" release did not happen is really bad.

i have said it before and i understand a lot of people do not agree, but their public relations absolutely sucks 

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...
 
 

Hmmm... do you think it is a good idea to do that? It is one thing if you communicate this here and I totally see your reasoning, but if you include these campaigns in an unfinished state, you are technically releasing a faulty or buggy product. Not every customer browses the forums and will be able or willing to get this information. I'd be careful with that from a marketing perspective.

You did a wonderful job in commenting every part of my comment that wasn´t that significant but somehow missed the keystone:
"I am pretty sure that the information that end of July won´t see a release was available to the devs way earlier than that so why not take some seconds an post a simple: " Due to the temporal unavailability of crucial staff we unfortunately won´t see a release in End of July but still need some more weeks before release, we will keep you updated, thanks for your support." In my opinion this is the most obvious way to handle this situation. either way its definitely better than just letting a release date passing by with no communication at all. "
What are your thoughts on this?
Mattis

I am pretty new to this forum but must also admit that despite all the hardships that Battlefront must face as a small developer, certain aspects of their communication policy is somewhat that I personally wouldn´t commend.
I am fine with release dates that don´t get met, it is a hard thing to do to predict completion and future obstacles and we all surely don´t want Battlefront to lower their quality standards by leaving bugs unattended or by cutting features just to met the date, like many triple A devs do these days.
So normally it wouldn´t be a big deal for me when the first announcement date on end of July wasn´t achieved due to unexpected holidays of personnel. However I see no real excuse (feel free to correct me here) that we weren´t informed before the 31st of July. I am pretty sure that the information that end of July won´t see a release was available to the devs way earlier than that so why not take some seconds an post a simple: " Due to the temporal unavailability of crucial staff we unfortunately won´t see a release in End of July but still need some more weeks before release, we will keep you updated, thanks for your support." In my opinion this is the most obvious way to handle this situation. either way its definitely better than just letting a release date passing by with no communication at all.
Sure for me there was not much lost despite some wasted time doing bf website checks for release info. However I still perceived this behavior as somewhat disprespectful.
I am certainly sure many will disagree here with this perception with is totally fine so please don´t flip the master arm already and lets keep things civil. Especially because I still support Battlefront as one of the few developers bringing us one of the most authentic wargames ever made and wish them best luck with the upcoming release.
Mattis 

Speaking as a long time lurker who never posts....(ooops. Dang).  I’m sure there are many people around the world that play CM games and never post on here, and would love to see this game grow. And what better way for it to grow than to go the steam route. I love the fact that I can access all my steam content (and play) on any computer that I sign into steam with. 
I am also perfectly happy going the stand alone battlefront route, I just wish that this game could continue to grow. The updates and new content seem a tad slow in coming, and a huge expansion of the customer base could change that. I for one always have my cash ready if and when, that lucky year finally comes.
As far as the discussion that the fine people on this site have been having, clearly your straw pole does indicate a decisive answer.
Dave

Speaking as a long time lurker who never posts....(ooops. Dang).  I’m sure there are many people around the world that play CM games and never post on here, and would love to see this game grow. And what better way for it to grow than to go the steam route. I love the fact that I can access all my steam content (and play) on any computer that I sign into steam with. 
I am also perfectly happy going the stand alone battlefront route, I just wish that this game could continue to grow. The updates and new content seem a tad slow in coming, and a huge expansion of the customer base could change that. I for one always have my cash ready if and when, that lucky year finally comes.
As far as the discussion that the fine people on this site have been having, clearly your straw pole does indicate a decisive answer.
Dave

Game mechanics of a Separatist’s Base Camp: All active base camps have a stationary security element.  An active camp has at least one maneuver unit assigned.  The unit leaves camp, conducts operations and then returns. On the next scheduled reinforcement turn, the unit receives reinforcements, in the base camp, that are assigned to the same AI group. The unit then conducts additional operations. A Separatist (red) exit zone is in the camp but is blocked by a combination of no-go terrain and barbwire. The Separatist maneuver unit’s movement paths cross the exit zone.  While the exit zone is blocked the Separatists path finding AI goes around the exit zone. 


US/Ukrainian forces can eliminate the camp by destroying whatever forces are present and then destroying the barbwire. 


The barbwire is the key.  Because after the barbwire is destroyed all future Separatist maneuver units & reinforcements will enter the exit zone (never reaching Order #4) eliminating the camp as a source of Separatist units.  The only reliable way US/Ukrainian forces can remove the barbwire is with demo charges. This compels the player to enter and clear the camp instead of calling in arty from a distance.


There are also inactive base camps.  The inactive base camps are present since the player may, in addition to the three types of intelligence provided, use a 4th source of intelligence. The fourth source would be IMINT (Imagery Intelligence) used by flying the camera low over suspected base camp locations. So to confirm an active vs inactive base camp will require boots on the ground.  Another more realistic and cool way to attempt to make the ID would be through the use of the one provided drone.  Then send in a QRF!  
@IICptMillerII @Bil Hardenberger @Gumshoe @SLIM @Combatintman @Oleksandr Just FYI. 
Bil I tagged you because IIRC you were SIGINT back in the day?  Or had some connection to Intel anyways. 
 
 
 

Ok I think its time to release this beast for public consumption. Below are the recent adjustments and fixes based on playtester suggestions.
1. I have found the save game issue and fixed. I had  some " : " in the file name it did not like. The " : " has been destroyed and you should be able to save in the middle of a mission.
2. Added additional time to all missions as requested.
3. The troops of SRY have been corrected and now include Lille Fiskerby's beloved Sherman Fireflies. (Thank you Lillie for pointing that out.)
4. Also added a few more historical names to CO's of various units. Still could not find enough info to name all of them.
5. Corrected briefings where changes were made.
6. Made force adjustments in some missions based on tester suggestions. Some additions and some reductions. But the OOB is still historically accurate for all the missions based on my research.
7. Added setup zone to one mission that was omitted.
8. Made a few terrain adjustments to improve LOS in some missions.
9. Adjusted some VP parameters in a few missions.
Thank you to all the playtesters who helped me with this campaign.
If any other issues come to light please let me know through this thread or PM and I will correct. Hopefully most everything is right now. This was a huge undertaking and my first truely historical campaign so I hope it proves enjoyable.
IMPORTANT: Before downloading please reread the opening section of this thread for the campaign details. This will not be for everyone. Its big, maps are big, everything is big so it may task older systems. It will require patience and management. But if you stick with it you will play through a little known but important battle of WW2.
Here is the link to the main download
https://www.dropbox.com/s/2qw0u84mojuz40v/Operation Clipper.zip?dl=0
Put the modfolder into your dataz and delete the .cam file.
Here is the link to the updated .cam file
https://www.dropbox.com/s/884hj2mo7ullzgy/Operation Clipper.cam?dl=0
Place this into your campaign directory
I hope you enjoy.
Michael