Hey guys,

 

i'm having a problem, after spending many hours today re-installing my fsx.

I have started fsx several times during installation of different addons, now suddenly this shows up:

 

Scenery read error, attempting to open a nonexistent directory d:/fsx/terrain

 

I have, as said, been reinstalling for many hours, and now it suddenly wont work.
When i start fsx up, this error pops up, and then it crashes and shuts down before i even get in to the menu.

 

I really really don't want to re-install it again. Please help guys!


Oh, and by the way, this error occured after i downloaded and installed some liveries for the PMDG MD-11.
It started during the second or third livery.

 

 

 

Thanks
Kim.

What is happening is you used the same scenery.cfg you had in your old installation.  That scenery is no longer installed or no longer in that directory.  You can open up the Scenery Library and relink all of the scenery or, your best bet is to download SceneryConfigEditor (see the link to this utility in the AVSIM CTD Guide).  The sceneryconfigeditor will look for errors in your installation and offer to fix them for you. 

 

For your PMDG error, you'll need to go to the PMDG MD11 Forum.

 

Best regards,

What is happening is you used the same scenery.cfg you had in your old installation.  That scenery is no longer installed or no longer in that directory.  You can open up the Scenery Library and relink all of the scenery or, your best bet is to download SceneryConfigEditor (see the link to this utility in the AVSIM CTD Guide).  The sceneryconfigeditor will look for errors in your installation and offer to fix them for you. 

 

For your PMDG error, you'll need to go to the PMDG MD11 Forum.

 

Best regards,

Log Name:      Application

Source:        Application Error

Date:          19.09.2013 19:50:24

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Computer:      Kim-PC

Description:

Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3

Faulting module name: visualfx.dll, version: 10.0.61472.0, time stamp: 0x475e180e

Exception code: 0xc0000005

Fault offset: 0x00020bcb

Faulting process id: 0x1620

Faulting application start time: 0x01ceb560aef7be15

Faulting application path: D:\FSX\fsx.exe

Faulting module path: D:\FSX\visualfx.dll

Report Id: f57e67ec-2153-11e3-9601-ecfe01de8435

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="2013-09-19T17:50:24.000000000Z" />

    <EventRecordID>23335</EventRecordID>

    <Channel>Application</Channel>

    <Computer>Kim-PC</Computer>

    <Security />

  </System>

  <EventData>

    <Data>fsx.exe</Data>

    <Data>10.0.61472.0</Data>

    <Data>475e17d3</Data>

    <Data>visualfx.dll</Data>

    <Data>10.0.61472.0</Data>

    <Data>475e180e</Data>

    <Data>c0000005</Data>

    <Data>00020bcb</Data>

    <Data>1620</Data>

    <Data>01ceb560aef7be15</Data>

    <Data>D:\FSX\fsx.exe</Data>

    <Data>D:\FSX\visualfx.dll</Data>

    <Data>f57e67ec-2153-11e3-9601-ecfe01de8435</Data>

  </EventData>

</Event>

 

 

 

This is what i'm getting.

And also, i tried to rebuild the fsx.cfg, and now fsx actually starts up, but as soon as i hit ''free flight'' it crashes again..

You need to read the AVSIM CTD Guide.  Your crash was caused by the visual FX module which is used to display an FSX effect.  Here's a quote from the AVSIM CTD Guide:

 

"Visualfx.dll – The visualfx.dll is used to display an FSX effect.  An effect needed for an aircraft or scenery may not be located in the Effects folder and, when the effect is called by the program, it cannot be found and FSX crashes.  The CTD occurs mostly with aircraft not properly installed and/or the default flight (shown in the [userinterface] Situation= line in your fsx.cfg) may be corrupted when a new default flight is set up.  The solution in this case is to rename your fsx.cfg to fsx.orig, restart FSX and let the fsx.cfg rebuild.  It has also been fixed by returning the default textures into the main texture folder.  This can be done through a backup or conducting a FSX repair installation."

 

Hope this helps.

 

If you have any further problems, please download and run AppCrashView as this program provides more details about your crash.  The link to AppCrashView can be found in the CTD Guide.

 

Best regards,