|
|
Post by aeroart on Dec 3, 2015 20:50:02 GMT -5
Does anyone know of a "NoCD-like" solution that will allow Combat Flight Simulator to run under Windows 10?
Art
|
|
|
|
Post by Tom/CalClassic on Dec 4, 2015 11:13:22 GMT -5
I haven't heard of one. If there isn't, you would need to remove the Windows update before flying, then (if desired) restore it when finished.
|
|
|
|
Post by Johan Dees on Dec 4, 2015 15:01:51 GMT -5
|
|
|
|
Post by aeroart on Dec 5, 2015 21:37:13 GMT -5
Saved it to a CD. Thank you, Johan.
Art
|
|
|
|
Post by jimmyfingers on Dec 13, 2015 15:21:25 GMT -5
I'm have a different Windows 10 problem: installed W10 and seems okay, although not faster than W7. But, I have lost all the external and VC textures form the CC aircraft and some others converted from FS9. THe pay ware aircraft (A2A B377 and CS707) seem okay for the most part. Any ideas?
|
|
|
|
Post by Tom/CalClassic on Dec 14, 2015 1:05:00 GMT -5
Turn off DX10 Preview?
|
|
|
|
Post by jimmyfingers on Dec 14, 2015 8:21:22 GMT -5
Thanks Tom--yup--tried it both ways. But I think I found the problem: I have a 64 bit system and was running FSX 64bit in Win 7. For what ever reason, Win 10 is starting FSX in 32bit. Not sure how to fix this. And this may explain why I lost all the textures from the CalClassic airplanes. I'm asking the tech guru on the DeltaVA website for some help too. I am flying everyday this week so this will be a long term project. Regards, Jim
|
|
|
|
Post by Tom/CalClassic on Dec 14, 2015 13:35:39 GMT -5
I thought FSX (and all MS FS programs) are 32 bit programs and will run as such on 64 bit systems. But I know next to nothing about hardware, sorry.
|
|
|
|
Post by jimmyfingers on Dec 14, 2015 20:04:29 GMT -5
Well- it has run on my 64bit Win 7 but not Win 10. Still looking. Take care.
|
|
|
|
Post by jimmyfingers on Dec 14, 2015 21:54:25 GMT -5
So--one of our DVA pilots suggested this:
"I didn`t had[sic] no problem at all while switching to WIN10, but using Prepar3D. Try to remove everything in the folder: C:\Users\FSX\AppData\Roaming\Microsoft\FSX\Flight Simulator X (Backup into Desktop first) and fireup again FSX and let it create the files again. After that you may add your FSX.CFG into if everything opens fine. Also turn all the way down your UAC permission (You might want to search on that one)."
I cut all the files out of the FSX App folder and moved them to another folder. I rebooted FSX and it all came up right away. I forgot that the default display settings make my NVidia GTX ill so I had to mess with that, and I had to reset all the control axes and keys, etc. But the airplanes, textures and sounds are all seem to be working 4.0. I'm sure I will have to do quite a bit of re-tweaking along the way but this was a very simple solution to a potentially ugly situation. Not sure what the "UAC permissions" are: I couldn't find them. But it does not seem to matter at this point.
So far, with Windows 10, the computer boot up and web is noticeably faster and the buttons, keys, presentation and structure is pretty good, especially since it looks and acts like the Surface we are using for the paperless cockpit at Delta.
Yay for Thiago Braga!
Cheers!
|
|
