Running CFS3 in Windows 10: solved for now

You're talking about Combat Flight Simulator 1 and there is another forum for that sim on SOH where Ivan and the rest of that merry gang should be able to answer your questions.
 
I recently decided to update my CPU (core i7-7700k 4.2 OC to 4.7) and MB (ASUS Strix Z270H Gaming), but hesitated because I had gone from Win 7 to Win 10 using the free update on my old machine (AMD Phenom II x4 955 Black 3.2 OC to 3.8), and was concerned that it would invalidate my Activation. My son had done a similar update, and now has a MS nag notice to reactivate that he can't make go away.

After a bit of research I found this:
https://www.windowscentral.com/how-re-activate-windows-10-after-hardware-change

I went ahead and set up the Microsoft Account and linked my Activation to it before I changed any hardware. After that all went smoothly, and I had far less trouble with losing my program install settings than I did during the major OS updates (Anniversary and Creators) Microsoft pushed out this past year.
 
A new Problem

Hi guys,
I got a new computer and installed the newest windows 10 version on it.
Have been running win10 with cfs3 in the past without any problems.
Installed the game, pasted the .exe to desktop. gave it xp service pack 3 compatibility.
ran the config
Started the game and it works.

Then i wanted to go play online...........
Opened multiplayer options tab
changed the connection type to T1
clicked okay.......
Crash

BTW the oleacc.dll i had already deleted

Changing anything in the multiplayer options tab results in crash after clicking okay (connection type, or country, or Player name, or pilot)
attachment.php




If I open the multiplayer tab for joining a game it also crashes
attachment.php


reinstalled the game 20 times now (on ssd program files (x86) on D:\ now straight into the root directory of C:\ nothing helps
switched off firewall, switched off antivirus. made all exclusions, nothing helpsView attachment dxdiag.txt

On my other computer win10 wouldn't update properly but CFS3 always ran fine there.
Unfortunately i wiped that win10 installation and did a clean install so my wife can use that computer.

Now i figured, on that computer it always ran fine so it must be a hardware problem, no worries, i will install the game there so at least i can still play online games on sunday.

@#$^&*(*&^%$$ after wiping and installing the latest win10 on the old computer it has the exact same problem.

The game runs fine but multiplayer doesn't

dxdiag.txt tells me this

+++ WER6 +++:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0


Problem signature:
P1: cfs3- multi player win7.exe
P2: 3.1.0.30203
P3: 3e3ebe85
P4: COMMON.DLL
P5: 0.0.0.0
P6: 3e3ebd1c
P7: c0000005
P8: 0000f079
P9:
P10:




+++ WER7 +++:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0


Problem signature:
P1: cfs3- multi player win7.exe.exe
P2: 3.1.0.30203
P3: 3e3ebe85
P4: gundll.dll
P5: 0.50.152.1
P6: 3d9cf6c1
P7: c0000005
P8: 00030668
P9:
P10:




+++ WER8 +++:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0


Problem signature:
P1: cfs3- multi player win7.exe.exe
P2: 3.1.0.30203
P3: 3e3ebe85
P4: gundll.dll
P5: 0.50.152.1
P6: 3d9cf6c1
P7: c0000005
P8: 00030668
P9:
P10:




+++ WER9 +++:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0


Problem signature:
P1: cfs3- multi player win7.exe.exe
P2: 3.1.0.30203
P3: 3e3ebe85
P4: cfs3- multi player win7.exe.exe
P5: 3.1.0.30203
P6: 3e3ebe85
P7: c0000005
P8: 0034ba18
P9:
P10:


Please, if anybody has a clue what it could be?

Antivirus exclusions done
Firewall exclusions done
Router ports opened

2300-2400
86663-86667
dmz activated in wired ip 192.168.1.67

Must be something in win10 that screws it up

my realtime protection on my antivirus showed 3 files while the crash happened
C:\Windows\System32\Tasks\Microsoft\Windows\SoftwareProtectionPlatform\SvcRestartTask
dx diag
timestamp nvidia

Maybe this can help one of you online whizkids in the community

Any help is very very very much appreciated

Cheers

Hanko
 

Attachments

  • multiplayer options.jpg
    multiplayer options.jpg
    27.2 KB · Views: 36
  • multiplayer tab.jpg
    multiplayer tab.jpg
    36.2 KB · Views: 35
joining the win10 crowd with a new rig.
The vanilla install went flalesly, the other installs of six different versions are not so good ; I get a config overide error on all of them even afther making shure the compatibility setting where as edited and the game was run as administrator.
Any suggestion would be welcomed
 
Hairyspin, before I do this should I delete something in the appdata folder of the games and should I re-eniciate the multicfs3 ?
 
You could delete from the appddata and then run yr multicfs3 and re run the config file; all as admin.
 
thx everyone

It's the newest version of win10

Did a new install win10 2016, same problem

Just did a reinstall win10 64 2015

and...............

YEEEEEEHAAAAAAW, BACK TO NORMAL

When i started multiplayer windows asked to install one small program like some playerthing, now i forgot to remember the name. age........hahaha
Anyway, windows asked to install the player i clicked yes and Voila

Thx everyone that tried to help,

Really appreciate it
 
Almost there; when I remove Ankors shaders from the games they run well but if I attemp to put them back in the game d3d8 and shaders30 are ok but not d3d8.dll that causes the game from not running "config override fie is either corrupt or missing" . Tried running the config file and updating it but no success. So I cannot get the Ankors shaders to work.
 
I had a bit of trouble with the Creators Update that installed itself last night. The game still ran once I reinstalled the User files in \AppData\Roaming\Microsoft, but all of my Anti-Aliasing was disabled.

I tried new video drives, reinstalling DX9c, and a wide range of other control panel settings changes both in the game and in the NVCP all to no effect. What I finally found to work was using NvidiaProfileInspector to set the AA Compatibility bits. In the past this was not needed, and the value could remain at the default 0x00000000. Now it needs one of several that end with 40, 41, or C1.

40
41
240
1040
1241
F0C1
100C1
20041
401241
401840
4412C1

There are subtle effect differences between each one, but generally they fall into the three main groups defined by the last two digits. Right now I've settled on the last one, as it's biased toward darkening the edges its aliasing.
 
So after spending hours installing ETO, for some reason "windows can't find cfs3.exe. This only happened after updating TO 1.50. Everything worked perfect till 1.5
Having only limited time to do my hobby, (you know, work, wife ect.) I'm loath to start all over again when I'm sure I followed everything to the letter.

Win 10
i7 6700
GTX 980
 
Never mind, I'm stupid and all is well. You chaps have a fine weekend while I go set everything up now. Love this sim! ( notice I said sim not game ;)
 
Hello everyone and thanks to all the guys who took the time to post how to get CF3 working in Windows 10.

For me though, I couldn't for the life of me get mine to work. I had to replace my hard drive recently and rather than just re-installing from the external drive which had the back ups, I did a clean install with the most up to date version of Windows 10, having read that I wouldn't have to buy a new one because it reads the Digital Signature from my motherboard.

I read all the posts over and over thinking I missed something and the only thing that wasn't clear to me (my limited knowledge) was a post from Mongoose which mentioned an unmentionable patch. I searched everywhere on here to see if someone had posted it somewhere but unsuccessfully, maybe I'm just thick. I couldn't see his photobucket photo so maybe it was there.

It was the bit about replacing cfs3.exe which I didn't get wholly.

Quote:- 1/ Install CFS3 from your original CDs (or DVD if you're lucky). Make life easier by not installing to the default folder, use something like C:\CFS3 and avoid UAC problems later. Don't run the sim yet!
2/ Apply the 3.1 and 3.1a patches. Don't run the sim yet!
3/ Replace cfs3.exe with the unmentionable patch but don't run the sim yet!

I'm not completely software illiterate but my general knowledge is limited, however when a solution drops into my lap BINGO! :wiggle:

So, there was me thinking that if I downloaded 3.1 and 3.1a and more importantly the NoCd patch (which I found online and I think is the unmentionable patch, not really sure) I would just pop it straight into the main files of the programme which I happen to put onto my D drive. Sure it goes in there OK and it opens and unzips fine but it still didn't work. I stupidly expected it to fix itself and that it would automatically replace and fix the correct extensions. Then I read somewhere that you cannot have two of the same .exe files in the same folder, they don't work.

So here's what I did for those of you who still can't get it to run.

I followed Mongooses instructions once again (thank you Mongoose and hairyspin for this Topic) but this time I saved the NoCd file separately to my D drive as a stand alone folder and opened it. I unzipped it again to my D drive (I have my HD partitioned to C for the OS, D for games and other programmes and E,F and G for anything else like photos, music etc.). I then took the pretty pictured file out of the D drive (same as the one arrowed in the pic) and copied it to the same file (arrowed) in the Combat Flight Simulator 3 programme folder.

attachment.php


I now have a working Sim having changed the Compatibility settings.

Thanks again guys and I hope this post helps others.
Cheers for now.
 

Attachments

  • exe1.png
    exe1.png
    33.7 KB · Views: 73
I'm running in Windows 10

Thank to you all, follow the earlier posts and ran great, I did the patch, no cd, direct9 and install at C: The only problem it doesn't recognise my Phantom Hawk joystick, so a bit stuck on calibrating and programming the joystick buttons, the SIM just hangs and I've use task manager to kill it
Trevor, wanttobeapilot
 
Hello!

Well hello gents! I just had my Win7 rig checked tonight and the mobo is gone caput. Ah well... time to order a new rig. I think I will go for another i7 nvidia setup and get an external cd-rom as the only one I saw on Best Buy was almost as old as my liquid cooled rig from 2012. I will follow the procedures listed here in the next couple weeks. Wonder if my avatar still works?

Cheers! :ernaehrung004:
 
I had a bit of trouble with the Creators Update that installed itself last night. The game still ran once I reinstalled the User files in \AppData\Roaming\Microsoft, but all of my Anti-Aliasing was disabled.

I tried new video drives, reinstalling DX9c, and a wide range of other control panel settings changes both in the game and in the NVCP all to no effect. What I finally found to work was using NvidiaProfileInspector to set the AA Compatibility bits. In the past this was not needed, and the value could remain at the default 0x00000000. Now it needs one of several that end with 40, 41, or C1.

40
41
240
1040
1241
F0C1
100C1
20041
401241
401840
4412C1

There are subtle effect differences between each one, but generally they fall into the three main groups defined by the last two digits. Right now I've settled on the last one, as it's biased toward darkening the edges its aliasing.

This still applies, but I discovered another work around.

If you set NoMultisampling=0 in d3d8.ini, and apply in game Multisampling (8X) through cfs3config.exe, and use "Enhance the Application Setting" versus "Override any Application Setting", then you can still apply custom anti-aliasing settings like SGSSAA to reduce shimmering through Nvidia Profile Inspector. Doing it this way produces almost exactly the same effect as using the compatibility bits I listed above.
 
Back
Top