ACTIVE 2S1 & CTD

[JoseCFII]

I was wondering if there was a fix for the CTD that occur with 2S1 installed? I know it a freeware, but it's one great airport and I would love to use it regularly.

Thanks,

Jose

[Wolter van der Spoel]

Hi Jose,

not sure what the issue is at your end, I have 2S1 installed and active and have no issues with it, for sure since the latest lib files addressed the issues in that area, so there must be sumtin else going on at your end

[JoseCFII]

Here's a description of the crash:

Log Name: Application

Source: Windows Error Reporting

Date: 10/13/2011 10:14:01 AM

Event ID: 1001

Task Category: None

Level: Information

Keywords: Classic

User: N/A

Computer: JOSE-PC

Description:

Fault bucket , type 0

Event Name: APPCRASH

Response: Not available

Cab Id: 0

Problem signature:

P1: fsx.exe

P2: 10.0.61637.0

P3: 46fadb14

P4: ai_player.dll

P5: 10.0.61637.0

P6: 46fadb57

P7: c0000005

P8: 00037489

P9:

P10:

Attached files:

These files may be available here:

C:\Users\JOSE\AppData\Local\Microsoft\Windows\WER\ReportQueue\AppCrash_fsx.exe_4f2a8ca88d3377cc13f07a88f3ca622a06f7b61_0e8c6291

Analysis symbol:

Rechecking for solution: 0

Report Id: 98b0645f-f5a5-11e0-909b-8c89a51b5fa1

Report Status: 6

Event Xml:

<Event xmlns=&quot;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="2011-10-13T14:14:01.000000000Z" />

<EventRecordID>3686</EventRecordID>

<Channel>Application</Channel>

<Computer>JOSE-PC</Computer>

<Security />

</System>

<EventData>

<Data>

</Data>

<Data>0</Data>

<Data>APPCRASH</Data>

<Data>Not available</Data>

<Data>0</Data>

<Data>fsx.exe</Data>

<Data>10.0.61637.0</Data>

<Data>46fadb14</Data>

<Data>ai_player.dll</Data>

<Data>10.0.61637.0</Data>

<Data>46fadb57</Data>

<Data>c0000005</Data>

<Data>00037489</Data>

<Data>

</Data>

<Data>

</Data>

<Data>

</Data>

<Data>C:\Users\JOSE\AppData\Local\Microsoft\Windows\WER\ReportQueue\AppCrash_fsx.exe_4f2a8ca88d3377cc13f07a88f3ca622a06f7b61_0e8c6291</Data>

<Data>

</Data>

<Data>0</Data>

<Data>98b0645f-f5a5-11e0-909b-8c89a51b5fa1</Data>

<Data>6</Data>

</EventData>

</Event>

I tried it twice and crashed twice. I deleted 2S1 and now it does not crash over Seattle. I hope this helps.

[cvearl]

I fly in and out of it alot. With ENB I would CTD there more often for some reason. But sadly I have removed ENB and have had no CTD's since.

First thing I would do is reinstall current version of 2S1 followed immediately with checking that FTX Central was still on NA and then I would rerun the PNW.004 patch and then I would again check if the FTX Central was still NA and if not set it to NA again. Lastly I would then load the most recent Libraries for NA.

Start a flight in the default cub there and do some patterns. This is usually my routine when I have an airport misbehave in some way.

C.

[JoseCFII]

I fly in and out of it alot. With ENB I would CTD there more often for some reason. But sadly I have removed ENB and have had no CTD's since.

First thing I would do is reinstall current version of 2S1 followed immediately with checking that FTX Central was still on NA and then I would rerun the PNW.004 patch and then I would again check if the FTX Central was still NA and if not set it to NA again. Lastly I would then load the most recent Libraries for NA.

Start a flight in the default cub there and do some patterns. This is usually my routine when I have an airport misbehave in some way.

C.

I'll let you know if it works with your suggestions.

Thank.

Jose