Running CFS3 in Windows 10: solved for now

Hi All,

Just installed stock CFS3 to Win10 Home system via the 2 original disks, applied the patches followed the instructions for the exe file settings and all is working perfectly. the only extra step I took was to add the 4gb memory patch to the exe file.

now to attempt ETO and Ankor's shaders..

regards Rob.

System specs.

Model
PRY-INF2-1070
Processor Brand
Intel
Processor Type
Core i7
Processor Model
8700
Processor Speed (GHz)
3.20
Processor Max Speed (GHz)
4.60
Cooling System
Fan
Installed RAM
16GB
RAM Type
DDR4
Primary Storage Capacity
2TB
Storage Type
HDD
Additional Storage Capacity
256GB
Additional Storage Type
SSD
Wireless Networking
IEEE 802.11ac, Bluetooth 4.0
GPU Chipset Manufacturer
NVIDIA
GPU Chipset
GeForce GTX 1070
Graphics Card Memory
8GB
Monitor 1
LG 32” Class QHD gaming monitor 2560x1440 144Hz
Monitor 2
LG 22” Flatron 1680 x 1050 60Hz
Operating System
Windows 10 Home
System Type
64 bit
System Peripherals
Thermaitake – Ttesports gaming keyboard and mouse.
Joystick
MS Sidewinder 2 (no force feedback)
Flight Sim Peripherals
CH rudder pedals, CH throttle quadrant, CH Yoke, TrackIR-4.
Sound
MSi 5.1-7.1 using Razor Headset.
 
Hi All,

ETO installed and working well. C:\Microsoft Games\CFS3 ETO Expansion edited the bat files to match directory, no discernable issues with switching era's etc noticed yet.

I do have one problem across both current installs of CFS3 though. The F7 key doesn't seem to be recognised, which means I cant select bomb aimer view. all the other 'F' keys are working as they should. Has anybody else experienced this?

regards Rob.
 
I find I've had to hold the key longer than usual; especially as I have day and night bomb sights so need to press it 2x for night ones. I don't think it is the keybiard as no other issues and have the same issue with F7 binding on my joystick.
 
Hi All,

F7 key issue fixed. with the update of trackIR software to version 5 there is a tick box for each program button (F7, F8, F9, F12) called trap. If you untick this option you have the ability for other keybindings to use the key in question, I can now get to bomb aimer view.

So have a perfect multiple install of CFS3 working on windows 10. Ankor shaders (Nov 17 2017 build) working in stock CFS3 - WOW.....

regards Rob.
 
Capt. Winters said:
Hi All,

F7 key issue fixed. with the update of trackIR software to version 5 there is a tick box for each program button (F7, F8, F9, F12) called trap. If you untick this option you have the ability for other keybindings to use the key in question, I can now get to bomb aimer view.

So have a perfect multiple install of CFS3 working on windows 10. Ankor shaders (Nov 17 2017 build) working in stock CFS3 - WOW.....

regards Rob.
Click to expand...

hi Rob, I agree, stock CFS3 is unrecognisable now with Ankors latest shaders. Even some of the stock textures look great if you have a hi-res monitor. The firetrucks and the bog standard opel Blitz have hitherto unseen variations and subtle changes in the skins in UHD. Not to mention even the stock effects! That is why I uploaded the upgrade of stock, it all looks great on a WQHD 34" monitor, Win 10 64 bit.
 
I had a complete loss of computer about 6 weeks ago. Sadly, most of my CFS3 development work was lost in the process. I've got things running again finally with the newest version of Win 10 installed.

An install of CFS3 is running, but it is being relentlessly capped at 50 fps by something in Win 10 (I've eliminated all the other possible sources). With last Fall's version of Win 10, running at 77-100 FPS in G-Sync was never even an issue.

I've done a bunch of Internet searching to no avail. Either the answer is that you can't outfox Windows from doing this, or the known tricks like disabling fullscreen optimizations don't seem to work on my system. I have Game Bar turned off, but there is no longer any way to disable Game Mode.

Has anyone else seen this, and figured out a workaround? I'd hate to think my high speed monitor is going to have to run at half speed all the time.

*** After hours of messing around it started working normally without doing anything in particular to stop it. :dizzy: ***
 
Of course I get up this morning to see that Win 10 1803 has decided it needed to do a monthly update after I went to bed last night, and the 50 FPS lock is back... :dejection:

I can see that the game starts okay, and then a few seconds after the User Interface comes up the monitor framerate drops from 99 to 50.

I went into the registry and added a DWORD command to disable Game Mode, and in the Windows Gaming Control Panel I can see that it's now turned off. Still no joy so the problem must be caused by something else.

It does not happen in my 3D benchmarking tool, so this seems to be something peculiar to CFS3.
 
That's why i'm sticking with Win 7 64bit ! No issues... get to choose Win updates. Run at 91 fps. Ever thought about running dual Windows programs ?
 
I used to have a dual boot system, but lost that capability when I changed computers a few years ago, and the MB wouldn't let me boot off the DVD to load the OEM operating system disks I had.

So it turns out that the cfs3.xml in the Default folder had the maxFPS set at 77. In the past this always worked with no problem, and helped to reduce micro-stutters. Evidently now Win 10 misinterprets it. Settings less than 50 work as requested, but anything over 50 gets set to half my 100 MHz monitor's refresh rate (ignores V-Sync).
 
MajorMagee said:
So it turns out that the cfs3.xml in the Default folder had the maxFPS set at 77. In the past this always worked with no problem, and helped to reduce micro-stutters. Evidently now Win 10 misinterprets it. Settings less than 50 work as requested, but anything over 50 gets set to half my 100 MHz monitor's refresh rate (ignores V-Sync).
Click to expand...

Just seen this post. My guess would have been cfs3.xml. But I didn't know about the strange business of halving the refresh rate.....I tend to set cfs3.xml to my monitor's (pathetic) refresh rate of 60Hz. When I press Z it tells me that it is working fine, giving me around 58-59 Hz.
 
Hi All,

with stock CFS3 I get 270fps all day long, stock CFS3 with Ankors shaders applied I get a consistent 60fps. my ETO install with Ankors shaders again gets a consistent 60fps. my cfs3.xml files have a max fps set to 0. Is it possible that the shaders are somehow talking to Win10 and this is the cause of the capped fps in game?

regards Rob.
 
There is a line in AnKor's d3d8.ini that can force you to 60 FPS if that's what your monitor runs at.

; -1 - Off; 0 - Default; 1 - VSync On
VSyncMode=1

You can set this to -1, and see if your FPS goes up.
 
Hi All,

Thanks Andy, changing that value from 0 to -1. I now have an average FPS of 190 with shaders applied.

regarsd Rob.
 
Yeah! that is the same for me. It will be interesting to see what it is with large formations and lots going on.
 
CFS3 in Win 10 stopped Working.

I had CFS3 running beautifully in win 10 after following Hairyspin's instructions.

Now it will not run at all. I think a windows update caused the problem.

I uninstalled followed Hairyspin's instructions again but still no joy.

Has anyone any clues?

Thanks
 
Are we talking about one of the monthly patches, or a full blown version update?

I'm still at version 1803 because of the system wipe-out I suffered last October.
 
You must log in or register to reply here.
Back
Top