A2A Piper Cherokee PA 28-180 CTD

[realkewl 3]

Hello,

 

Just thought I check and see if anybody is having this issue. After owning A2A Piper for about a week I decided to take a long flight 4+ hours.

 

Twice now after about 3 hours my sims CTD.

 

I have not had any other 3rd party aircraft do this. I also own A2A C172 and have taken long flights.

 

I have tried to get in touch with A2A, via forum and email. But no luck. Forum registration has issues and I cannot get someone to reset my password, I emailed them about this issue...and still no luck.

 

I'm thinking it's an overheating problem...but not sure. First time it CTD...second time it just rebooted.

 

Thanks,

Ray

[Jim Young 2,356]

You need to post an AppCrashView report (see the AVSIM CTD Guide located to the right of this forum under Hot Spots). If you are getting the Blue Screen of Death (BSOD), then that would be a hardware issue. In that case you should go to the following link and download Blue Screen View and post the results here.

 

When you fly for longer than 4 hours in just one session, you probably ran out of memory as you only have 4GB's of VAS and it depletes fast if you have your sliders up high. The FSUIPC.log (located in your FSX Modules folder) will usually tell you after a flightsim session whether you are close to running out of memory (you have to check the log after each crash as it resets when you restart FSX).

 

Best regards,

[realkewl 3]

Hey Jim,

 

How do you read the log file (FSUIPC.log) to check if you're running out of memory. Just did another long flight in the Flight1 King Air B200. I'm getting AppHangs haven't had one of these in about a year. Today got three of them.

 

Had one this morning about 3 hours into a 4 hour flight. TXKF-CYYT...made it within an hour then it froze.

 

Decided to restart but this time going CYYT - LEST froze in about 15 minutes.

 

Checked for a uiautomation.dll in FSX, found it, removed it, rebuild libraries. Restarted CYYT-LEST and about 3.5 hours into flight and froze.

 

I'm wondering if the Flight1 android app has anything to do with this. I'll test again in the morning same flight but with out running the android app.

 

These are some weird issues.

 

Thanks so much,

Ray

[Jim Young 2,356]

How do you read the log file (FSUIPC.log) to check if you're running out of memory.

Startup FSX and then enter the Addon Menu and select FSUIPC. Once FSUIPC is open, click on the Logging Tab and enter 024C under Offset and select S32 under Type. Select where you would like to have the usage displayed. The FS Window is for Full Screen sessions. The FS Title Bar is for Windowed Mode. AVSIM recommends you also check the Normal log file as this provides you information on how much VAS you had to start out with and then it logs usage throughout your flight.

 

The VAS usage is displayed in Kilobytes (KB’s). The value represents the amount of VAS left so, the lower the value, the more VAS being depleted. The max amount of VAS allowed in computers with 64 bit Operating Systems is 4GB’s. This is shared with other applications running in the background on your computer. For 32 bit Operating Systems, the max amount of VAS allowed for FSX/P3D is 2GB’s but this can be expanded to 3GB’s with a switch like the /3GB switch.

 

To convert the KB’s to the amount of GB’s, you should use one of the Byte converters on the Internet like the following: http://www.whatsabyte.com/P1/byteconverter.htm . You will never see 4194304 KB’s displayed as this equals 4GB’s. You might see around 3GB’s (3145728) remaining when you first start up FSX/P3D but that would be unusual. Do not be too concerned with the amount of VAS remaining when you first start up.

 

Restarted CYYT-LEST and about 3.5 hours into flight and froze.

This is definitely indicative of depleting VAS. There is no way you can fix this other than lowering your settings. FYI Autogen is the biggest VAS hog (this was fixed in P3D). See the AVSIM FSX Configuration Guide located to the right of this forum under Hot Spots for proper settings (for most computers) and other recommendations for saving memory.

 

Best regards,

[realkewl 3]

Thanks Jim

[rototom 198]

I've stopped buying anything for FSX. It's an ageing platform and this problem will continue to escalate with most new addons. We have many great addons for FSX, but when you run them in a sim that is 8 years old, they might not be so great. For me, it's too much of a risk to spend money and not know if I'll get to the end of my flight. And since I can't solve the problem by throwing more hardware at it, I'm stuck with paying something for nothing.

[Jim Young 2,356]

We have many great addons for FSX, but when you run them in a sim that is 8 years old, they might not be so great. For me, it's too much of a risk to spend money and not know if I'll get to the end of my flight. And since I can't solve the problem by throwing more hardware at it, I'm stuck with paying something for nothing.

Most FSX addons are compatible with the latest sim - P3DV2. The sim is almost exactly like FSX - http://www.prepar3d.com/product-overview/. So, if you want to continue simulating flight, it would be wise to upgrade any older system for the best performance. Most members have no problems using FSX and FSX addons. Plus FSX runs great but is limited by the Windows Operating System from maximum performance as Windows limits virtual address space for every 32 bit application to 4GB's. So far X-Plane has gone to 64 bit and there are rumors that P3D will be converted to 64 bit soon. Unfortunately, the addons will have to be converted too and that may take some time.

 

Best regards,