First...the knee board would not scroll through pages. Then it started blinking

Then IYP failed

Shortly after that EZDOK views froze. I could still change planes, locations or reset a flight but still the above

Hours later I restored to a point BEFORE going to DX10:

Tried to start FSX. The start screen appeared for about 15 secs then closed.

I had already replaced all my pre-DX10 cfgs and Nvidia Inspecter settings

Also replaced the Shaders Folder

First error message was about EZDOK, I reinstalled it. Still no FSX

Checked all logs (FSUIPC, LINDA, etc ) all were good.

Finally checked log.log in FSX and got the following:

 

full path: D:\Flight Simulator X\
redirecting CreateDevice
initiredirecting CreateDXGIFactordevice->GetBackBuffer failed
redirecting CreateDevice
initialising shader environment
D3DXCreateEffectFromFile failed
try to use "D:\Flight Simulator X" for shader files

 

What else can I do to fix this?  As far as I recall, everything has been reset to the DX9 configuration.

I really like DX10 and am going to try it again but need a "clean" FSX working in DX9 first.

Help appreciated.

Neal H

 

 

 

 

 

 

 

 

 

Good Morning Neal;

 

Sounds like you've done all the groundwork - rolling back to an earlier date; letting fsx create a clean, "untweaked" fsx.cfg, deleted the user shader and shader10 folders, etc..

 

The odd thing to note is that the message is suggesting that something is reading a script, and it can't interpret the FSX path, as the top line is not enclosed in quotation marks but the recommended action is exactly that. Possibly the exe.dll is corrupt? This is not an uncommon problem, and will stop FSX in it's track if it's bad.

To check this, download and run Microsoft's XML NotePad 2007. This is the picture you should see if it is working properly: Any time there's a path name that's broken (with a space between individual words - like Flight ^ Simulator ^ X ), the script cannot read it, and so throws up an error. The way to fix that is to enclose the name with quotation marks, like so:- "Flight Simulator X".

 

Lastly, (assuming the above didn't fix it), having multiple problems may be an indication that something in the operating system is broken - either by a Windows Update, a new addon, or a new software installation, and it's most likely a DirectX issue - possibly one of the Visual C++ 20xx Redistributable support apps, or one of the Dot Net Framework files is corrupt.

 

A repair, using the FSX disks will work, but it's a pain, so I would suggest checking what is shown in the "Add-Remove" or "Uninstall a Program" window, making a note of them (and the version), uninstalling the newest, and then  browsing to the Microsoft site, downloading and re-installing each until they're all done or it's fixed.

Isn't log.log the SweetFX log file?  Those messages look like SweetFX log entries.  Maybe try removing SweetFX and see what happens?

That sounds like a great idea. It should ring a bell somewhere, because this is a pretty common occurrence just lately...  :(

Running out of VAS would be my guess. try disabling some unused sceneries?

UPDATE: Thanks for the suggestions friends. I tried each (several times). It seemed that FSX could load just so far and then either freeze or close. I could not get past the start screen.

The real culprit was/is a "sidebyside"error simprop.dll. which was reported in Events Viewer.

I tried every fix I could find including a couple of Microsoft scans from the command prompt window.

Paul, Everything in the dll.xml matched your correct one. I even disabled all add-ons in the xml.dll.

No luck

All the usual tricks...new fsx.cfg, deleting logs, uninstalling anything that wasn't essential, restoring Windows to an earlier date and trying all the above again.

There were only two options left:

1. Toss the PC from a moving vehicle somewhere on the Interstate or

2. Wipe the FSX disk and software disk clean and reinstall everything EXCEPT Windows

Not being a spendthrift nor litterer, option two is the only viable one for me.

So, it is back to another week in the FSX rebuild hangar.

 In real aviation, FSX would be called a "Hangar Queen".

Regards to all and remember: ALL aircraft engines sound "strange" over large bodies of water.

NealH

The only way to fix the SimProp.dll error is to do a repair of FSX.  Just reinsert the FSX disk and select Repair when Autorun gives you the options.  If you have Acceleration installed, you will have to run a repair using that disk too.  If you have just SP2 installed, then you will need to repair SP1 and then SP2.  Yes, it will wipe out your Fsx.cfg, dll.xml, and working scenery.cfg so you might want to back them up first.

 

Best regards,

Jim