gatechfan_99

I figured it would be something stupid. Never occurred to me to update the motherboard drivers after Windows 10 started using the onboard sound seamlessly and that "auto-save" in VAFS. John Bradley AAL132

SOLVED!!!!! It was a combination of issues: 1. Didn't update my motherboard drivers. BIG rookie mistake. 2. Did some tweaking in the cfg file. Added a few lines like HIGHMEM=1 under graphics...stuff like that. 3. Figured that VAFS could also be a culprit. Turned off autosave and just completed a cross continental flight from KLAX to KMIA on the PMDG 777. However I flew this flight offline VATSIM. Hopefully this solved it. John Bradley AAL132

I had to laugh...That's hysterical. Ok...I did a system restore to sometime last week to reset the computer and I'm taking a few days break to figure out what's the problem is. I'm leaning toward it being an FSUIPC issue at the moment. John Bradley AAl132

Latest update 11:02 ET July 26. Now FSX is completely broken. What a frigging mess!! Looks like this weekend, I'll roll back to Windows 7 and be happy with it. I'm now getting SimConnect timing out errors and FSX simply won't open. John Bradley AAL132

Further update: Did what someone suggested that the freeze-ups with FSX had to do with multiple sound drivers, I went into Device Manager dand disabled all the nVidia drivers and rebooted. I did an OFFLINE flight using only ASN and the PMDG 777, using FS2Crew Voice from KLAX to PHNL. Flight went extremely smooth and experienced not a single freeze-up. FSX started with not a single issue. This afternoon....oh my God...Took FSX several times to start up and hold together after activating FS2Crew and VAFS. I'm starting to wonder if FSUIPC could be the problem. Finally got off the ground at Heathrow (where I use the UK2000 scenery demo) and seemed to have one freeze-up, but it was barely noticeable. I'm over STU now and will continue to track and see if the freeze-up takes place again. The biggest issue after startup is that the panel would disappear along with the surrounding scenery. Right now, when I do an external view, I don't see the aircraft all all. Just the spinning turbines and contrails. Totally weird. But I need to complete this flight to meet my minimum pirep for the month. Like I said, yesterday, I did an offline flight and had zero issues. 5:12 ET update: Started the freeze-ups again. Tried to save and restart, but FSX kept crashing. I'm going to install the Level D 767 and see if that can at eliminate the PMDG as the culprit. I'm really leaning on the problem to being FSUIPC at this point in time. John Bradley AAL132

Its turned into a fiasco for real Tempted to delete the WIn10 and reinstall! Turns out that when I'm doing a flight with the PMDG 777 with ASN, FSInn, and VAFS...after 45 minutes or so into the flight, it starts freezing for up to 15 seconds then resume for only 5-10 seconds and freeze up again. Unless there is some simple way to fix this, I'm afraid I'm going to be on Windows 7 for good. Any ideas where I can search for this problem? John Bradley AAL132

Follow up: I did a clean, fresh of Windows 10 and after getting everything up and running and reinstalling FS2Crew, I went through the Win10 Voice Recognition training, it has behaved much, MUCH better. Thanks!! John Bradley AAL132

Final followup: After a week of reinstalling everything...PMDG, ASN, FSBuild, GSX, London, and various freeware sceneries, I finally sat down to do my first VATSIM flight. Started FSX...then crash to desktop. Over and over and over. Took a few days of research and to realize the uiautomationcore.dll file needed to be moved to the root directory. Only problem is that the Win10's version is crap for FSX. I finally found a Vista version out there and placed into the FSX rood directory. Ever since then...no crashes to desktop. So far after a few test flights with the PMDG 777, its been seamless. Still working on my EZDok settings, but I feel confident that its going to work out fine after all under Windows 10. John Bradley AAL132

Ok, folks...I did the fresh install of Win 10 and took days to get everything back up and running with FSX. I have noticed that there are few issues. Mostly when I close FSX, it tends to crash instead of closing smoothly. Tried my first long-haul flight this afternoon and found I still had a pants-load of work to do. Such as getting FSBuild to copy to FSX, ASN, PMDG777 among others. Another issue that's been extremely annoying is not being able to put the FSX icon in the tile area. First of all, the icon didn't show up on the desktop. had to create a shortcut from the FSX folder. Then when I tried to tile it, it won't go further. Finally I gave up and pinned the FSX icon in the task bar. As far as performance goes...its been extremely smooth with the few flights I've done. I haven't done a long PMDG 777 flight just yet, but plan to tomorrow night. No stutters. FSInn loaded up pretty good after a few tweaks. I have EZDok installed and still messing with that. As with every clean install, it can be a PITA getting everything back up to snuff from before. Oh...I just remembered...While I was on the ground at KJFK with a lot of traffic, for the first time in a long time, I was able to see the WOI a/c while logged to VATSIM. That happened rarely with Win7-64 and I didn't worry too much about it. Thanks for the advice, guys... John Bradley AAL132

Thanks, fellas. I'll download the Windows 10 update files, save on a CD and try later. John Bradley AAL132

Didn't like it. Rolled it back to Windows 7. Decided since MS has seemed to fix a lot of the issues with Windows 10 and more and more people here are starting to like it and that the driver issues related with FSX and the various addons seems to be fixed. So..I started to take the plunge to upgrade to Windows 10. However I can't seem to get past the first reboot screen after it downloads the files and gets me to click on the EULA. It wants to reboot over and over and resume from there. I did that at least 20 times and it restarts Windows 7-64 at the exact same spot. "Windows 10 is ready to install. Click Restart to begin." Any ideas? John Bradley AAL123

I killed off my Yankee relatives. John Bradley AAL132

Did a flight tonite...And problem still exists. I skipped over the VREF XXX and skipped to Minimums 200 feet. But it thinks I'm saying Minimums 200 eight Tried different ways to say "feet" but its either "eight" or "set." John Bradley AAl132

Haven't flown since your reply.... Thanks for checking in. John Bradley AAL132