Cat_Dad

Retired military. I have been flight simming since working on the F-4E and F-111D simulators in the Air Force. Also made people glow in the dark managing a diagnostic radiology department. Finally worked as a aircraft dispatcher. Terry

Jim, Glad you got it working now. Maybe Santa will bring me a 4K too. Terry

Jim, I do not believe you are going to get max 4k resolution with that particular connection. You will need a HDMI cable with enough speed to carry the signal. Also you will need to plug it into the correct port on the computer and tv. You can do a google check for 4k HDMI requirements and or there are some posts here at AVSIM that explain the requirements for getting those nice 4K pictures. Hope this helps Terry

I cannot say yes or no to does windows 10 leave files behind. I tried to go back to windows 7 pro after 7 months and windows 10 would not allow me to load/boot from the 7 disk or from inside windows 10 it's self. It would turn off the mouse and keyboard which are both USBs. Finally took it into the shop where it was built and they removed both smaller ssd's and replaced them with one larger one plus put the computer back to Windows 7 Pro. While running windows 10, after a period of time, more things stopped working on FSX til finally it would not even reload due to missing/mismatched files. Since FSX is so old, the newer windows 10 must not have needed those older XP and 7 files. Terry

Update: Jim, Thought maybe the problem was gone after doing a complete remove and replace the FSX program. Moved it from the F drive to the C drive. Every thing still is default except changed Wide Screen from False to True and added HighMem.Fix =1. Flew bothe the default C-172 and taxied the 737. When I tried to move the terrain mesh from default to max and then the terrain res from 38M to max then that is were it died and gave me the same old report.below. Log Name: Application Source: Application Error Date: 6/22/2016 12:59:55 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: User-PC Description: Faulting application name: fsx.exe, version: 10.0.60905.0, time stamp: 0x44fd0a92 Faulting module name: uiautomationcore.dll, version: 7.2.10586.212, time stamp: 0x56fa2107 Exception code: 0xc0000005 Fault offset: 0x0004d233 Faulting process id: 0x2724 Faulting application start time: 0x01d1cca521cbeeaf Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe Faulting module path: C:\WINDOWS\SYSTEM32\uiautomationcore.dll Report Id: 707ebc01-1d16-445d-af53-7bab10a21aeb Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-06-22T16:59:55.079900400Z" /> <EventRecordID>19749</EventRecordID> <Channel>Application</Channel> <Computer>User-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.60905.0</Data> <Data>44fd0a92</Data> <Data>uiautomationcore.dll</Data> <Data>7.2.10586.212</Data> <Data>56fa2107</Data> <Data>c0000005</Data> <Data>0004d233</Data> <Data>2724</Data> <Data>01d1cca521cbeeaf</Data> <Data>C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe</Data> <Data>C:\WINDOWS\SYSTEM32\uiautomationcore.dll</Data> <Data>707ebc01-1d16-445d-af53-7bab10a21aeb</Data> <Data> </Data> <Data> </Data> </EventData> </Event> Does the ui dll in FSX have to match the one in Win10 and if so where do I find it in win10? Terry

Jim, Did as you suggested and removed the ui dll from FSX. Doing so it would not even start so put back and program starts again but dies when aircraft is taking off. Also ran the MS Dotnet repair tool. Looked like it did something but sill stops program after running that program too. This is the latest error msg data. Log Name: Application Source: Application Error Date: 6/22/2016 9:18:58 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: User-PC Description: Faulting application name: fsx.exe, version: 10.0.61355.0, time stamp: 0x4643ee0a Faulting module name: uiautomationcore.dll, version: 7.2.10586.212, time stamp: 0x56fa2107 Exception code: 0xc0000005 Fault offset: 0x0004d235 Faulting process id: 0x10e0 Faulting application start time: 0x01d1cc8859cf4ffb Faulting application path: F:\FSX\fsx.exe Faulting module path: C:\WINDOWS\SYSTEM32\uiautomationcore.dll Report Id: 1609bc38-6dba-4a6a-a799-df2dbe5896c6 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-06-22T13:18:58.671367200Z" /> <EventRecordID>19607</EventRecordID> <Channel>Application</Channel> <Computer>User-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61355.0</Data> <Data>4643ee0a</Data> <Data>uiautomationcore.dll</Data> <Data>7.2.10586.212</Data> <Data>56fa2107</Data> <Data>c0000005</Data> <Data>0004d235</Data> <Data>10e0</Data> <Data>01d1cc8859cf4ffb</Data> <Data>F:\FSX\fsx.exe</Data> <Data>C:\WINDOWS\SYSTEM32\uiautomationcore.dll</Data> <Data>1609bc38-6dba-4a6a-a799-df2dbe5896c6</Data> <Data> </Data> <Data> </Data> </EventData> </Event> From the control panel uninstall window, I have only Net framework 1.1 showing. Also have MS Visual C++ 2005 through 2013. Also a MS ASP.Net MVC 4 Runtime. Supposedly, Win10 is up to date when I went to the update window and did a manual forced update. Would not the Net framework be part of that and or the monthly Tuesday updates? Almost ready to go back to Win 7 pro except I would have to wipe the entire computer and then put up with MS nagging to update or now possible buy Win 10. I have limited vision and this does not seem like fun at this pres tent time. Thanks for helping out and hope I can find a more simple fix short of going back to Win 7. Terry PS: When I reloaded FSX this morning, I was not able to move it to the C drive as planned. When I deleted it the last time, using the uninstall feature only uninstalled the SP2 and not the entire FSX program. Since I could not remove it any further, I removed the folders which appears to have been the wrong move. Think I will try to remove FSX this time via the installation disk program of fix/remove. Then at least I can put everything on one SSD and maybe I will stop getting the above error?

This is an updated version of my first post of the error log below. Basically, is the log telling me it cannot find FSX files on my F drive and the config files that get placed on the C drive? As stated in the first initial post, The program has worked fine in this config up until now. Even when I completely removed all of FSX to include the setting files and reloaded it all on the c drive, I still was getting the same program halts. Hope this helps. Terry Log Name: Application Source: Application Error Date: 6/21/2016 10:13:27 PM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: User-PC Description: Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3 Faulting module name: uiautomationcore.dll, version: 7.2.10586.212, time stamp: 0x56fa2107 Exception code: 0xc0000005 Fault offset: 0x0004d233 Faulting process id: 0x1c94 Faulting application start time: 0x01d1cc2b1aa3eedc Faulting application path: F:\FSX\fsx.exe Faulting module path: C:\WINDOWS\SYSTEM32\uiautomationcore.dll Report Id: 5d8b65cf-221c-446a-a839-5decd610f331 Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2016-06-22T02:13:27.985099900Z" /> <EventRecordID>19227</EventRecordID> <Channel>Application</Channel> <Computer>User-PC</Computer> <Security /> </System> <EventData> <Data>fsx.exe</Data> <Data>10.0.61472.0</Data> <Data>475e17d3</Data> <Data>uiautomationcore.dll</Data> <Data>7.2.10586.212</Data> <Data>56fa2107</Data> <Data>c0000005</Data> <Data>0004d233</Data> <Data>1c94</Data> <Data>01d1cc2b1aa3eedc</Data> <Data>F:\FSX\fsx.exe</Data> <Data>C:\WINDOWS\SYSTEM32\uiautomationcore.dll</Data> <Data>5d8b65cf-221c-446a-a839-5decd610f331</Data> <Data> </Data> <Data> </Data> </EventData> </Event> PS:Most of the program halts come when trying to move the aircraft from one airport to another. Sometimes when switching aircraft. Also unable to view data in the call sign flight number box when selecting a aircraft. Going to reload FSX on the C drive. Was on my F drive with tons of open space and C is getting over half full Even though they are SSD's do not want to overload the C drive. and hurt computer performance. Also updated about 10 drives with the drive update program.

For almost a year, I have been running FSX in windows 10 with very few problems. Now I am lucky to get FSX to stay running maybe once or twice out of a dozen starts. Nothing has changed in my system except for NVIDA driver updates (GTX 980) and the automatic Microsoft updates. I have zero add-ons and run default aircraft. Have added the MS FSX SP1 and 2. FSX runs on it's own SSD as it always has. Have reloaded FSX several times with no fix to the problem. Even tried running FSX on the C drive and still the same results. The computer is a I 7 4790 @ 3.6 GHZ, 16 MB ram, GTX 980, Win 10 Pro 64, Ver 1511, build 10586.420. Again the FSX use to run just fine up until about a month ago. Even tried rolling back two or three versions of the vido drivers just to see if they might have changed something. The answer was no. Any ideas on how to fix this? Terry

Current TV and monitors are all limited by how much "DATA" can be delivered to them. There are several different HDMI cables and right now if you have the standard 1.4 hdmi cable your 4k TV will only support 30 Hz. If you have the newer hdmi 2.0 cable, it can transmit enough data to display at .60 Hz. Then there is another cable (not hdmi) that can handle 4 k and up right now. Some of the higher end tV/monitors have these and that might be wheat you are seeing , thinking they are a strange hdmi plug. This link explains all of this much better than I can. http://www.trustedreviews.com/opinions/hdmi-2-0-vs-1-4 Hope this helps. Terry

Thanks for the engine link. Unfortunately, I was not able to log into the site to down load it. Terry

Thanks for the heads up on the 737-800 sounds. Funny thing though, the 747 in FSX does not sound anything like the 737 it is suppose to be imitating.. I wonder why and how that overly loud base/background cockpit and exterior noise can be changed. Terry

Has anyone ever noticed that the default 747-400s in FSX have only one sound level? (Loud). Are there any adjustments or add on sound files that are more realistic? Setting all of the sound sliders in FSX to zero does no good when flying the 747. Terry

Thanks for the heads up on the flight report. It has been quite a whale (35 years) since I have flown the F-4C aircraft and the F-4E simulator. After watching several of the videos that are linked to yours (the F-4E video) a lot of the numbers and procedures have started to come back. I do remember they use to train the student pilots to use the rudder to roll when in a high AOA condition. I also remember that we had a ARI (aileron rudder interconnect) that did a good job of keeping things under control but you still could not fly with your feet flat on the floor either. We had a "Hard Over" rudder failure we would give usually on short final or when the instructor wanted the crew to punch out. I seem to remember if you were quick enough to hit the paddle switch on the stick, you then could reach over and pull the ARI C/B and regain control. We had 7 C/Bs in the front seat and several hundred back seat. I spent a entire night shift trouble shooting a INS write-up along with a retired sim tech without any idea why it would not work. We knew our mainframe computer that ran the entire sim, the interface system,and the INS box in the cockpit were all good. While leaning over the side of the cockpit setting it up for our daily pref light inspection, I noticed one of those two hundred thirty C/Bs pulled out. That is why the INS would not work. Pushed it back in and signed off the 781 forms and we we good to go. The only way you could view most of those C/Bs was to stand on your head so I do not know how they pulled it in flight unless they ran the seat all they way down to the cockpit floor. Have you ever noticed how many of the switches and levers in the cockpit are a specific shape? When you are busy flying the jet (looking outside) you do not want to have to put your head down/inside to do something like switching fuel tanks, operating the flaps or selecting guns or missiles. I am not sure if the modern day aircraft still have this feature or maybe it is done now with computers. Terry PS: Is the F-4 payware or freeware? I have not seen it in the AVSIM library before. I am flying the T-45 freeware they have and it would be nice to fly some heavier iron.

Nice video. Good mix of formation flying and inside the cockpit. The marking on the jet looks like it was from the weapos school at Nellis AFB. Terry

No not a flight engineer. Too blind for a Air Force flight physical even though I was a civilian instructor pilot (FAA). I take it the tail strikes on the 141s were after they stretched it into the B model? Terry