Hi Steve,

  Just received ver 2.2 from John at ORBX for testing FTX airports.  After installation into the default location I used the desktop icon to launch the application.  I get an error message "DX 10 Controller.exe has stopped working", and have to cancel.  I don't see any error log.

 

I'm using Win7 x64.   Do I have to switch FSX to DX10 Preview before trying to start the Scenery Fixer?

 

Thanks, Rob Abernathy

There is nothing you need to do, it should just run.

 

I have had a few issues with icons in the past but I thought all those had been dealt with. Can you test for me by running it not using the desktop link but by going to the installation directory and double clicking the exe. If it doesn't run then try running dx10toolbox which is in the same directory and doesn't have an icon to see if that is ok.

Hi again Steve,

   I tried your suggestions and neither one worked for me.  Ran the DX10 Controller.exe directly from the installed folder and got the same error.  Then I ran the DX10ToolBox.exe and get this error msg............ FSX Install Dir not set. (0)  System Error was 2

  I've read through the manual but I'm not getting the Fixer to run at all yet.

Did you install the Microsoft C Runtime? - its slightly non obvious with that installer - you have to let it "run dx10controller" but actually it installs c++ - I never send that one without the manual. If not you can run it manually its in the VC directory underneath the installation directory.

 

Ignore that, it wouldn't give that error. Do you get any error in control panel-> event logs then in that tool Windows Logs-> application

Hi,

  Yes, I've discovered the Event Logs!   I just ran the DX10Controller.exe and found a fresh error logged.  Here's the contents:

 

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

- <System>

<Provider Name="Windows Error Reporting" />

<EventID Qualifiers="0">1001</EventID>

<Level>4</Level>

<Task>0</Task>

<Keywords>0x80000000000000</Keywords>

<TimeCreated SystemTime="2014-05-07T14:22:11.000000000Z" />

<EventRecordID>44348</EventRecordID>

<Channel>Application</Channel>

<Computer>Robert-PC</Computer>

<Security />

</System>

- <EventData>

<Data>231942287</Data>

<Data>17</Data>

<Data>APPCRASH</Data>

<Data>Not available</Data>

<Data>0</Data>

<Data>DX10Controller.exe</Data>

<Data>0.0.0.0</Data>

<Data>53609671</Data>

<Data>ole32.dll</Data>

<Data>6.1.7601.17514</Data>

<Data>4ce7b96f</Data>

<Data>c0000005</Data>

<Data>00028eed</Data>

<Data />

<Data />

<Data>C:\Users\Robert\AppData\Local\Temp\WER8FAA.tmp.WERInternalMetadata.xml</Data>

<Data>C:\Users\Robert\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_DX10Controller.e_e5aaa6b3df4b44f6f9ccbddd73f133d6647872b_ec489b2e</Data>

<Data />

<Data>0</Data>

<Data>f821d308-d5f2-11e3-add0-f46d04e1713a</Data>

<Data>0</Data>

</EventData>

</Event>

 

 

And under the General heading:

 

Fault bucket 231942287, type 17
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: DX10Controller.exe
P2: 0.0.0.0
P3: 53609671
P4: ole32.dll
P5: 6.1.7601.17514
P6: 4ce7b96f
P7: c0000005
P8: 00028eed
P9:
P10:

Attached files:
C:\Users\Robert\AppData\Local\Temp\WER8FAA.tmp.WERInternalMetadata.xml

These files may be available here:
C:\Users\Robert\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_DX10Controller.e_e5aaa6b3df4b44f6f9ccbddd73f133d6647872b_ec489b2e

Analysis symbol:
Rechecking for solution: 0
Report Id: f821d308-d5f2-11e3-add0-f46d04e1713a
Report Status: 0

Hunting around I found one other person reported the same issue in March

 

I posted this and heard nothing back - so I don't know whether it fixed the error!

 

Do they have an old version of Microsft Access installed? - Google shows references to ole32 crashes in other applications caused by Microsoft Access Custom Icon Handler

 

 

There is a hot fix for ole32 causing crashes but I cannot be sure its the same issue.

http://support.micro....com/kb/2541119

Hi Steve,

  Just to update, I visited MS support and did an update for my Window 7 installation ( just over 300 MB!), but that didn't solve it.   So, I downloaded the hotfix in you link and installed it.  It broke my Windows and I had to go to a restore point to get it back working again.  It looks like I'm just out of luck on using the Scenery Fixer.

Hi Rob

 

I have sent you a PM

Hi Steve,

 

 I just bought you product and I'm also having this very same problem...... any help i can get would be great Thank you. (W7+ 64 bit) 

Can you open your dx10.ini file using notedpad -

 

its in the directory

 

<Your user>\AppData\Local\Dx10SceneryFixer

 

at the top it should look something like this

 

[DX10SceneryFixer]

Rebuild=0

Mode=0

RebuildGeneral=0

RebuildMisc=0

RebuildTerrain=0

AutoExit=1

SecondSystem=1

DiagnosticsIcon=1

FsxRunningCheck=1

 

 

Change the line FsxRunningCheck=1 to FsxRunningCheck=0

 

Then let me know if the controller then runs - as I cannot reproduce this problem I cannot guarantee that it will fix it.

Well,  I clicked on that folder (\AppData\Local\Dx10SceneryFixer) and there is another folder named "Working" and that folder  is empty. I have no idea what went wrong at the moment of install  :Worried: Everything seemed to be ok. 

ah - as the controller hasn't run it wont be there yet for you.

 

Can you create an dx10.ini file in that directory like this then

 

[DX10SceneryFixer]

FsxRunningCheck=0

 

and then try running the controller for me

Like this?      https://drive.google.com/file/d/0B00XhcZUJ7jkUWttOUdlZV9WZUE/view?usp=sharing 

                     https://drive.google.com/file/d/0B00XhcZUJ7jka013d3VtanhHLWc/view?usp=sharing

 

I tried with no luck. thank you for taking the time to help me. 

I have a new version for you to test in that case.

Can you pm me an email address please?