Has anyone ever had any issues with the orbx AU airports causing d3d9.dll crashes to the desktop (due to the objectflow entries in the dll.xml)? I was gold till I installed one or two AU airports.. removing the entries fixes the issue... For now I've just kept the entries out of the dll.xml file. It happens on an alt enter.

orbx AU airports causing d3d9.dll crashes to the desktop

 

Do you have the ENB Series module installed? That has a special d3d9.dll in it that is put into your main FSX directory (if not, it's located in your system32 folder). Just asking as this module does not work for everyone and you'll have to look around for the best module that's compatible with FSX. You'll have to rename or remove the d3d9.dll and the enb.ini.

 

Best regards,

Jim

 

 

Do you have the ENB Series module installed? That has a special d3d9.dll in it that is put into your main FSX directory (if not, it's located in your system32 folder). Just asking as this module does not work for everyone and you'll have to look around for the best module that's compatible with FSX. You'll have to rename or remove the d3d9.dll and the enb.ini.

 

Best regards,

Jim

 

Unfortunately I don't. The faulting path is sys32. Still thinking maybe it's a windows 8 issue though more testing is needed

on win 7 i cant replicate the crashing.. i'm using 12.6 of the ati driver though, not 12.8 like on win 8.. i'm going to install some more AU airports see if it starts, if not, i may try to take the "win 7 fsx drive contents" and put on my win 8 fsx drive (moving the old) and using the config files from win 7 and see what happens.

on win 7 i cant replicate the crashing.. i'm using 12.6 of the ati driver though, not 12.8 like on win 8.. i'm going to install some more AU airports see if it starts, if not, i may try to take the "win 7 fsx drive contents" and put on my win 8 fsx drive (moving the old) and using the config files from win 7 and see what happens.

 

The problem may be Microsoft.net 3.5 which is not automatically installed on Windows 8. Some of the FTX/Orbx programs were developed with Microsoft.net 3.5 (they even have a download for it on their website). Here's how to get it installed for Windows 8 - http://msdn.microsoft.com/en-us/library/hh506443.aspx. Microsoft.net 4.5 is installed with Windows 8 but it is not backwards compatible with previous versions.

 

Best regards,

Jim

The problem may be Microsoft.net 3.5 which is not automatically installed on Windows 8. Some of the FTX/Orbx programs were developed with Microsoft.net 3.5 (they even have a download for it on their website). Here's how to get it installed for Windows 8 - http://msdn.microsof...y/hh506443.aspx. Microsoft.net 4.5 is installed with Windows 8 but it is not backwards compatible with previous versions.

 

Best regards,

Jim

 

It wasn't that.. Microsoft .net 3.5 was auto installed and/or selected by me as I develop a bit, so I made sure initially all that was installed. I double checked. I also tried putting the d3d9.dll 2010 file from the windows 7 system32 in place.. this time the crash mutated into a ntdll.dll error.

 

I'm now trying to restore the fsx drive files that worked under 7 and the roaming and programdata folders as well, will see how that goes, though i'm not holding my breath here.

I've confirmed this is a Windows 8/orbx issue.

 

On Windows 8, bare bones.. I ran the fsx setup, then fsx acceleration..

 

Tested alt enter and windows mode etc, no creashes.. (no ati driver installed thus far either)

 

then Orbx AU Blue..

It auto prompted to install .net 3.5 and then i reran the orbx au blue. The setup completed.

 

I then ran orbx melbourne 2.0..

 

Ran fsx.. random airport.. alt and enter to go window and instant crash on d3d9.dll.

 

So at this point this proves to me there is a compatibility issue with the orbx ftx objectflow entries in the dll.xml that dont play nicely with windows mode or alt enter to exit full screen etc.

 

This is leading me to think i may just dual boot and have a windows 7 FSX OS partition for the time being, as i can always port my user cfg files over to 8 if this ever gets a fix. It would be a shame to be flying for a long duration flight and have another app pop up to cause the entire flight / experience to crash in an instant.

 

I had this info in another thread located here If there is anyone who can rename that thread title.. i think a more appropriate title may be "Windows 8 x64 + Orbx ObjectFlow causing CTD on alt enter".

I just downclocked from 4.7 to a stable 4.5 on my I5 2500k.

Got tired of the BSODs from running 4.7ghz