tanker

No CTDs in the last 2 months. I have not really changed anything in my setup. I suspect the CTDs I experienced in the past were tied to a particular default scenery and/or approach.

Just finished the same flight, this time to RNAV rwy 29 instead of RNAV rwy 17l. No CTD, everything worked perfectly.

I flew the same route and approach with a different aircraft today and got the same CTD at about the same time and location. I'm thinking a default scenery error? RAM, VRAM, CPU and GPU all checked ok. Will try again later with a different approach

I have had about 3 CTDs out of a dozen flights since SU12. Any advice would be appreciated System: I7=9700K GPU Geforce RTX 2070 Super MB MSI 2390 16 GB RAM CTD happens about 40 minutes into flight. Last occurrence with Carenado PA44 IFR KDAY to KSDF with PMS50 GTN Default scenery From Event Viewer: Log Name: Application Source: Application Error Date: 4/9/2023 6:15:55 AM Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: Dale5 Description: Faulting application name: FlightSimulator.exe, version: 1.31.22.0, time stamp: 0x00000000 Faulting module name: FlightSimulator.exe, version: 1.31.22.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x0000000004f52410 Faulting process id: 0xcd4 Faulting application start time: 0x01d96ac408829f12 Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.31.22.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Faulting module path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.31.22.0_x64__8wekyb3d8bbwe\FlightSimulator.exe Report Id: d1b4d4f0-b1b0-4da0-b1f9-377add4fac3b Faulting package full name: Microsoft.FlightSimulator_1.31.22.0_x64__8wekyb3d8bbwe Faulting package-relative application ID: App Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2023-04-09T10:15:55.8814040Z" /> <EventRecordID>74467</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>Dale5</Computer> <Security /> </System> <EventData> <Data>FlightSimulator.exe</Data> <Data>1.31.22.0</Data> <Data>00000000</Data> <Data>FlightSimulator.exe</Data> <Data>1.31.22.0</Data> <Data>00000000</Data> <Data>c0000005</Data> <Data>0000000004f52410</Data> <Data>cd4</Data> <Data>01d96ac408829f12</Data> <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.31.22.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data> <Data>C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.31.22.0_x64__8wekyb3d8bbwe\FlightSimulator.exe</Data> <Data>d1b4d4f0-b1b0-4da0-b1f9-377add4fac3b</Data> <Data>Microsoft.FlightSimulator_1.31.22.0_x64__8wekyb3d8bbwe</Data> <Data>App</Data> </EventData> </Event>

Thanks! I will check AI assists Dale

I checked all my devices, including the keyboard, and could not find a binding issue. I emptied the community folder, deleted the 337, and restarted MSFS. Re-installed the 337. Still having the extreme pitch up problem. All the default and other Carenado aircraft work normally. Thanks for the suggestions, just haven't found the problem yet. Dale

The autopilot indicates that it is off, but it does act like it is on. I will check all the bindings on my devices plus any assignments on FSUIPC. Thanks, Dale

I'm having pitch control problems with the Carenado 337. At rotation speed it pitches up and no amount of forward pressure on the yoke will force the nose down. Both engines operating normally, full prop pitch and mixture, autopilot off, Trim is checked at takeoff setting, 1/2 tank of fuel, cg in limits Yoke assignment checked, elevator appears to be working in outside view All other aircraft, including Carenado, are working normally Any suggestions would be most welcome

Same here

I think you may be on to something. I make my flight plans using Lil Nav, then import to MSFS. I'll experiment with staying away from J routes. Dale

On a flight from KSAV to KJAX, IFR victor airways, default scenery, default Baron, ATC instructs me to climb to FL 280! The fllight plan was filed for 6000 ft. I tried requesting a lower cruising altitude, but was denied. Finally cancelled IFR, and proceeded VFR. Is this a problem with the scenery or with ATC? I miss the old Radar Contact ATC. Dale

Thanks! I found 2 files for the PA44 (one appeared to be compacted). I deleted both and downloaded again, and it worked.

I tried to download the latest Carenado PA44 update in the MSFS Marketplace. It seemed to download ok, but then hung up on "decompressing". I tried deleting the aircraft and did a fresh download. It shows the aircraft as installed, latest version, but when I try to select the PA44, it's not there. Now I can't delete the aircraft and try again. Any ideas?

I have been flying IFR in P3D4, using Radar Contact, an old program, no longer supported. RC4 is by no means perfect, but seems far more realistic to me than MSFS 2020. When RC4 assigns an approach, it gives you the ILS frequency and gives you the option to take vectors to the final approach or to fly the full approach. The voices are mechanical sounding and there is no support for taxi or VFR flight. What's needed is the best of RC4 combined with the MSFS ATC.

Thanks again Ray, your suggestion solved the problem.