Search the Community

After some uninstall/re-install/patch action I finally got a decent working install on Windows 10 (Pro). The main trick is the DDFIX 1.15.13 Mod. PROs I can now task switch and have no screen corruption while flying. everything runs very fast and smooth. I can tune a lot of the visuals with nVidia Control Panel CONs Task switching while in menu will result in a black screen, but mousing over will reveal click spots. I cannot get it to run in a higher resolution than 1024x768 (always get a complaint of "ERROR: GetFlyScreenMode:can't find any supported screen mode" when I try to set a higher res in cam.cfg) There can be screen flicker in aircraft panel areas and the mouse will create trails on certain gauges, both clear up with some view switching. Compatibility Mode doesn't seem to affect anything more than sound; without it the engine and effects seem to cut in and out. But my current setting of Windows XP sp3 seems to resolve all of that. When I get time I will try the Panel fix I've seen posted elsewhere to see if that clears up the flickering and mouse trails. I would very much like to be able to use native screen res of 1920x1080, but nothing I have tried has resulted in anything better than black/gray screens (FUMode=1 in ddfix.ini). Hope someone can help get us the rest of the way there. -kl

Just completed an excellent flight from St Louis to Dallas over MSE Missouri and Texas V3 using the PMDG 738 and ProATC-X. Details hidden below. I have the latest Windows10 v1709 installed w/the latest KB4051963. Was able to accelerate to 4x's during most of the flight but the weather was heavy throughout the flight! On approach, I went to the wingview and watched the landing from there. Got amazing fps and lots of VAS remaining even though I had a lot of addons running. Happy about that. Just wanted to show the flight is possible with FSX (boxed). If anyone is having issues seeing the Primary Flight Display and FMC's with the PMDG 737 in Windows 10, copy the PMDG Fonts in the FSX folder over to the Windows/Font folder. Do not replace any current fonts, just add the missing ones. I thought it was interesting too that FSUIPC did not have to trap any G3D errors. Usually, on long flights like this one (500 miles), FSUIPC has to trap 5-10 errors.

This is a new FSX install and Windows 10. I have Win 10 Creator's Update running FSX with Acceleration, several plane addons, and that's it. Everytime I exit FSX I get this notification. I've right clicked on the Properties of the FSX Shortcut and adjusted the compatibility mode (I tried Win 7 and Vista) but I still get this notification after I exit FSX everytime. Any idea how to get rid of this notification? Thanks.

Been away for a long time. Old Win 7 machine took a big dump and I lost everything. EVERYTHING! Now I'm getting a brand new top-end machine running Win 10, and I'll be re-installing FSX SE, ORBX, most of the A2A and PMDG inventory, and everything else...weather, FSUIPC, TrackIR, EZDok, etc., etc. Question is, how do I set up Win 10 to run FSX SE clean and proper? Do I worry about DX10? Is there a list of things to change in the OS like there was in 7? The new machine will run FSX and DCS World exclusively - no personal data, no e-mail, no browsers, no nothing. Just 4 TBytes of drives and 32 Gb of fast RAM and a NVidia card with lots of RAM, too. Someone out there must have a list of preps for this. Any input will be appreciated. I can't wait to get back I the air.

Windows 10 seeks to reduce power consumption and, hence save battery life, by switching off USB devices that are dormant and drawing 'excess' power. This can cause USB devices, such are Saitek panels and joysticks, to disconnect in flight leading to a loss of control inputs and displays. This thread describes 2 ways of over coming the automatic shutdown of USB devices. Method 2 is the best but should only be done if you are confident in your abilities. Method 1 Identify the VID/PID for the affected USB device(s). Using the LINDA Setup Joysticks page, find the line for the device and note the 9 alphanumeric value at the start of the line (eg. 06A30D050 for Saitek Radio Panel). The Vendor ID is the first 4 characters and the Product ID is the second 4 characters; the last digit is a count of the number of similar devices (eg. 06A30D050 --> VID=06A3 and PID=0D05). Open the Windows Device Manager. Click on Human Interface Devices. Now the slow bit. Right-click each USB Input Device and select Properties. If there is a Power Management tab, then click on Details tab and select Hardware IDs and identify the matching VID/PID for the device(s) of interest. Otherwise, try the next device. With the device identified, click on the Power Management tab. Untick the 'Allow the computer to turn off this device to save power' checkbox. Click OK. Repeat from step 4 for other devices. Method 2 CAUTION - This method requires direct manipulation of the Windows Registry. It should only be undertaken if you are confident in your abilities. No warranty is provided for those using this method. Be warned!! Identify the VID/PID for the affected USB device(s). Using the LINDA Setup Joysticks page, find the line for the device and note the 9 alphanumeric value at the start of the line (eg. 06A30D050 for Saitek Radio Panel). The Vendor ID is the first 4 characters and the Product ID is the second 4 characters; the last digit is a count of the number of similar devices. Open RegEdit. In the lefthand pane, locate the tab Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Enum\USB. Find the entry for the device(s) VID_{vid}&PID_{pid} (eg. VID_06A3&PID_0D05). Click on the arrow to the left. There will be one of more entries underneath (eg.7&3908cf29&0&3). Each refers to the number of times the USB device has been plugged into different USB ports. Click on each entry and then on Device Parameters. In the righthand pane, find and double-click on the entry EnhancePowerManagementEnabled. Change the value from 1 to 0 and click OK. Repeat from step 3 for each device. After carrying out the above methods, restart the PC and your Flt Sim. The USB should no longer switch off in use unless you change the USB port being used. Repeat the procedure if you do unplug and reconfigure your USB ports.

I put FSAUDIO.DLL in my Windows 10 windows\sysem32 folder just as I had in my Windows XP windows/system32 folderso the Tinmouse 737-200 would run in FSX. When I load a Tinmouse 737-20 in FSX on my Windows 10 system I get a ,message saying that FSAUDIO.DLL failed to load with error 0x7e and said to put FSAUDIO.DLL in the windows/system32 folder and to restart the appp, But, as I said, I had done that already.. Has anyone else had this problem? Actually, the Tinmouse 737-200 appears to load and run ok (so far as I can tell with it sitting at a gate). How do I fix the problem (or do I even need to)?

I've noticed that with Win10-64, that the FreeMeshX install executables do not function. Is this just me, or have any of you noticed it? Various compatibility modes and admin do not work for me.

I apologize if I'm in the wrong forum but I'm new to P3D and XPlane. I've been using FSX and now want to try P3D and Xplane also. I have an old system (i7, GTX 780, 8 GB RAM) which I plan to re-purpose as a flight sim only box running Win 10. I have two new SSD drives (250 and 480 GB) and one old 300 GB Velociraptor drive. I also just read Avsim's P3D guide unfortunately I did not find my answer to this question: Where do I install the OS, FSX, P3D, and X-Plane given the available drives which will give me the best performance in the next year or so (until I decide on which flight sim to use moving forward)? Does it make sense to install the OS on the Velociraptor drive, FSX and P3D on the 480 GB SSD drive, and X-Plane on the 250 GB SSD drive? Would removing the Velo drive and using just the two SSD drives be better performance wise should I decide to jump to a 64-bit flight sim? I currently have about 150 GB worth of FSX and DCS stuff in the Velo drive and the OS on a small 60 GB SSD drive. Thank you. Edit: I just read Ray Marshall's review of Aerofly in Avsim after I posted this. I guess I'll be trying Aerofly too before the year is out.

So from searching around, I know that there's no need to reactivate when reinstalling the aircraft or sim on the same Windows install, and I know that for a complete reinstall then I do need to return the license beforehand. What I'm not entirely clear on is how an in place upgrade from Windows 8.1 up to Windows 10 will affect the license, and therefore if I should be deactivating before doing so. I haven't actually done anything yet, as I'm doing a full disk backup before I touch anything because you can never have too many backups!

Has anyone been successful running in Win 10? I finally had to upgrade my system to be compatible with some upgrades for my professional tools. I successfully installed Fly!II (copied original directory over from my Windows 7 installation). After working around some graphics issues I got it to run nicely in "letter-boxed" form at its original resolution. However, the menus' text/fonts don't look very hot and overlays/pop-ups (like the GPS) come up empty (nice frame of the GPS, but with nothing on the display but a black screen). I have other simulators but would hate to lose Fly! - I had been running it about once a week. Any ideas?