cletus_zuber
Members +
Hello All,
I thought I would relate my recent experience installing CFS3 and most of the extensions in the sticky above, into a brand-new Win 11 machine.
My old computer up and died a couple days ago, (whilst flying somewhere around Malta), just went black and would not power back up. I figured it was gone for good as it was pretty old, I got it new, don’t recall what year, but it came with Win 7, and it was taxed hard, especially when running with shaders, FPS in the teens. So I hauled down to Best Buy and ended up with a mid-range Lenovo that I could afford.
First thing was to install the vanilla game. like I did last time, and with Power ISO, mounted it to the virtual disc drive. BUT it would not install. Clicking the Setup just threw an error no matter what I tried. So I just broke open all the CAB files and installed the contents in a folder called CFS3 on my desktop. The game plays fine. I later renamed and moved the folder to the stock location (x86), but the Patch and mission builder still would not install, both say they can’t find the install. More on this later. So the vanilla remains unpatched, with no discernible effect.
Next up was PTO Solomons-Following the instructions in the download, it installed and played no problem. (By no problem, I mean after running multi-cfs, cfs config, etc.) It comes with a working mission builder which I swapped over to the vanilla, there’s an MB folder in Uires that needs to be swapped over also, if you didn’t know. I have details of how I found this out if interested.
Next were the 2 new standalones, RS Pearl and China. These being self-contained worked out of the box. Correct me if I’m wrong, but it appears you do not even need a cfs vanilla with these?
Then on down the line, BoB Alpha, Daiwilletti’s Version 2.1 update, MAW, MAW 1943 and lastly ETO.
I had to do tweaks on each as various errors popped up when running the install for the first time.. Some of the fixes include, checking and unchecking Run as Admin, Compatability mode, unchecking Read Only, tweaking security settings etc. unchecking read only on the install folder and applying that to all files stopped most crashes on startup. I did not install any of the pre-packed App Data stuff, I let the game build its own.
I had to download and install DirectX for the shaders. MAW 1943 crashed so hard it killed windows!, I ended up running in safe mode, then the game worked fine after that. With ETO I installed all the updates up to 1.5 and added shaders before I even tried to run the game. It took 3 crashes and one low res startup, but now it works fine.
I can’t run any of the zappers as the thing came with McAffe installed, I’ll be able to do that after the trial expires in 30 days.
So that’s it, if you want some more details on what errors I got and what fixes worked, just ask.
Hope this helps someone in the future!
PS: FPS is great with the new machine, a whole new world!
I thought I would relate my recent experience installing CFS3 and most of the extensions in the sticky above, into a brand-new Win 11 machine.
My old computer up and died a couple days ago, (whilst flying somewhere around Malta), just went black and would not power back up. I figured it was gone for good as it was pretty old, I got it new, don’t recall what year, but it came with Win 7, and it was taxed hard, especially when running with shaders, FPS in the teens. So I hauled down to Best Buy and ended up with a mid-range Lenovo that I could afford.
First thing was to install the vanilla game. like I did last time, and with Power ISO, mounted it to the virtual disc drive. BUT it would not install. Clicking the Setup just threw an error no matter what I tried. So I just broke open all the CAB files and installed the contents in a folder called CFS3 on my desktop. The game plays fine. I later renamed and moved the folder to the stock location (x86), but the Patch and mission builder still would not install, both say they can’t find the install. More on this later. So the vanilla remains unpatched, with no discernible effect.
Next up was PTO Solomons-Following the instructions in the download, it installed and played no problem. (By no problem, I mean after running multi-cfs, cfs config, etc.) It comes with a working mission builder which I swapped over to the vanilla, there’s an MB folder in Uires that needs to be swapped over also, if you didn’t know. I have details of how I found this out if interested.
Next were the 2 new standalones, RS Pearl and China. These being self-contained worked out of the box. Correct me if I’m wrong, but it appears you do not even need a cfs vanilla with these?
Then on down the line, BoB Alpha, Daiwilletti’s Version 2.1 update, MAW, MAW 1943 and lastly ETO.
I had to do tweaks on each as various errors popped up when running the install for the first time.. Some of the fixes include, checking and unchecking Run as Admin, Compatability mode, unchecking Read Only, tweaking security settings etc. unchecking read only on the install folder and applying that to all files stopped most crashes on startup. I did not install any of the pre-packed App Data stuff, I let the game build its own.
I had to download and install DirectX for the shaders. MAW 1943 crashed so hard it killed windows!, I ended up running in safe mode, then the game worked fine after that. With ETO I installed all the updates up to 1.5 and added shaders before I even tried to run the game. It took 3 crashes and one low res startup, but now it works fine.
I can’t run any of the zappers as the thing came with McAffe installed, I’ll be able to do that after the trial expires in 30 days.
So that’s it, if you want some more details on what errors I got and what fixes worked, just ask.
Hope this helps someone in the future!
PS: FPS is great with the new machine, a whole new world!
Last edited by a moderator:
