FSX and Win10

#1
This winter season I thought I would get into FSX for the first time and adapt my scenery. I'm on Win10 though and come across an issue and wondered if any had same problem.

It is a clean install of win10 on new machine. FSX base game will load and run. FSX+SP1 will load and run, but FSX+SP2 comes up with a message saying Directx is incompatible and it refuses to start.

Win10 comes with DX12. I have installed runtime libraries (2010)pack, and also run a directx9.0c installer, but still get the message. Uninstalled and reinstalled fsx too.

Get the same problem if I try FSX standard plus accelerator.

Nvidia graphic drivers are up to date. Windows update up to date.

Wondered if the clever bods here had any ideas to try.
 
#3
Directx is there as FS2004 and base FSX+SP1 work fine.

Done all the following, many times

Run the Directx9.0c installer found by unpacking SP2 msi

Installed the full installer of runtime libraries 2010 as recommended by Microsoft.

Checked all 'dll are in system32 and syswow64 as recommended by microsoft.

Updated video card driver.

Checked latest win10 update has been done
 
#5
Here I was asking about the game itself, not the SDK. I have solved the game refusing to start because of DX incompatibility by removing the d3dx9_xx.dll's from both syswow64 and system32 folders then running the runtime_libraries_2010 directx installer from microsoft again. It put them back in the folders and, as they were missing this time, must of registered the fact with windows as now the game starts fine.

The link above is to do with SDK install. A whole other issue I have asked about in sdk forum as I do not have access to deluxe discs.

Coming to the FSX party late as you can tell.
 
#6
Just another guess. Did you install as admin. I mean right click run as admin. Sometime just admin IDs just don't work right. Also have you checked your windows event log and the directx logs.
 
#7
Well, I have FSX installed with Windows 7 in one PC and with Windows 10 in another. BOTH crash when I try to use the Menus or try to change airports or time/season after going on free flight, even by "End flight". There are zillions of other people with the same problem all over the Net, with and without Acceleration, fresh installs, etc., etc. FSX wasn't a superior product to begin with, as it didn't work until Microsoft came up with SP1, then SP2, and both turned into SP1a. There are many suggestions about running in compatibility with Vista, with Windows 7, as an administrator, and checking the box "Preview DirectX 10" in Settingns, and a few others, such as UIAutomationCore.dll. Nothing works, so far.

Working on scenery with this issue is a royal pain, of course.

If anyone knows of a solution, gosh, it would be great.

Fern
 
#9
that happen to me when change to W8.1, with Windows 7 fsx worke well, open the menú and change the time and get the crash. but right you mention it lately I have not had any problem with these issue ¡?
 
#10
Hi, Heretic
The Event Viewer shows:
Faulting application: fsx.exe
Faulting module name: uiautomationcore.dll version 7.2.10240.16515
Exception code: 0x000 0005
Fault offset: 0x00064d53
Faulting process id: 0x1aac
Faulting application starting time: 0x01d12316253d7a5e

I have seen the uiautomationcore.dll thing mentioned in the Net in more than one place, but the "solutions" were never clear, so I decided not to mess with it.

I have it in \System32 (this is Windows 10)

Do you have any suggestions?

Thanks!

Fern
 
#11
Well, I seem to have found a solution at fsxeu.com. They have a replacemente uiautomationcore.dll that fixed the problem. I was reluctant (.dll files can be deadly) but fsxeu seems to be a very reputable place. Anyway, it worked, at least so far (a good run, lots of Menu action, no crashes). If it comes back, I'll report.

In the meantime I wish Microsoft stopped giving those empty answers in their "community" and "TechNet", things like "try safemode" or "uninstall and install in compatibility mode", etc. There are thousands of reports of this issue, and fsxeu is the only place with an actual solution.

Thanks, all

Fern
 

Heretic

Resource contributor
#12
Glad you got it fixed.

MS only posts these genericm solutions because it would be way too much effort to do detailed troubleshooting with everyone having the a problem.
It's best just to use Google and try to find a solution yourself.
 
#13
Well, Heretic, I'd agree with you IF this was a generic problem affecting a non-Microsoft piece of software. When it affects FSX which, admittedly, is no longer Microsoft's, and Outlook, one of their current money makers, I believe that it is their corporate obligation to look for the problem. They dismiss it, instead.
 
#14
Well, Heretic, I'd agree with you IF this was a generic problem affecting a non-Microsoft piece of software. When it affects FSX which, admittedly, is no longer Microsoft's, and Outlook, one of their current money makers, I believe that it is their corporate obligation to look for the problem. They dismiss it, instead.
FSX is a 9-year old game developed for XP SP 2 and Vista. It's whistling in the wind to expect Microsoft to still have any corporate obligation to support FSX -any more than it has for other obsolesent games.
 
Top