Daiwilletti
Charter Member
After Grover1's post about .dlls I did a wee experiment.
I'm running Win 10, using the Ubisoft version of cfs3.exe for all my seven or eight installs, so it seems to run fine.
BUT I've been noticing that its been ages since I won a campaign. The latest campaign is 1944.xml from ETO 1.50. After invading Normandy in June 1944 as recently posted, the campaign bogged down with a month of fighting simply to get through Paris. Sadly I think Paris is now rubble...
However the main thing is that in the .cmpstat files created after every campaign mission, the Success Mod parameter is always negative. (these files can be read with notepad and record the current state of the campaign, including all the AI wingmen stats and frontline condition etc. the files are found under Username/Documents/CFS3 Install Name/Campaigns/etc).
So I've tried a wee experiment and turned Windows Defender off before flying a campaign mission.
WOW, what a difference! All sorts of new activity started to occur. It may be a coincidence because the mission coincided with one of those periods specified in the 1944.xml where new squadrons appear (around 1 September 1944?), but the frontline moved quite a bit and the SuccessMod parameter was not nearly so negative.
What is the point of this? Well for those using Win10 as their OS and Windows Defender as their anti-virus, it may be that they notice a difference by turning off Windows Defender before starting CFS3, particularly for campaign play.
I'm running Win 10, using the Ubisoft version of cfs3.exe for all my seven or eight installs, so it seems to run fine.
BUT I've been noticing that its been ages since I won a campaign. The latest campaign is 1944.xml from ETO 1.50. After invading Normandy in June 1944 as recently posted, the campaign bogged down with a month of fighting simply to get through Paris. Sadly I think Paris is now rubble...
However the main thing is that in the .cmpstat files created after every campaign mission, the Success Mod parameter is always negative. (these files can be read with notepad and record the current state of the campaign, including all the AI wingmen stats and frontline condition etc. the files are found under Username/Documents/CFS3 Install Name/Campaigns/etc).
So I've tried a wee experiment and turned Windows Defender off before flying a campaign mission.
WOW, what a difference! All sorts of new activity started to occur. It may be a coincidence because the mission coincided with one of those periods specified in the 1944.xml where new squadrons appear (around 1 September 1944?), but the frontline moved quite a bit and the SuccessMod parameter was not nearly so negative.
What is the point of this? Well for those using Win10 as their OS and Windows Defender as their anti-virus, it may be that they notice a difference by turning off Windows Defender before starting CFS3, particularly for campaign play.