Dane Watson

OK, I went ahead and restored from my backup all of the xxx.dat files in folder 0.4.0 and it resolved my problem - so hopefully that was the right thing to do. Please let me know if there was another way to resolve what seemed to be a corrupt file. Also I do notice that sometimes when I load a new saved flight, after flying a different flight, ChasePlane hangs and zooms out from the camera position - it's not a big deal as I just close it and restart it and all is OK again - just passing this on.

Also wondered if I could restore from my backup the xxx.dat files would that bring my presents back?

One particular aircraft has corrupted camera presets - is there a simple way to reinstall them rather than deleting and recreating each one over again? The aircraft no longer shows up in the choices to import so I cannot import them back in.

Good to know...

I understand now. I have cycle 1802 from Navigraph. I need to update my old cycle to the latest.

One of the Notes for new features states... Some new features like the MORA grid, display of FAF, MAP and others need either an AIRAC cycle from Navigraph later or equal to 1810 or the included AIRAC cycle. I would like to turn these options on but they are greyed out. I am using the included AIRAC cycle 1802 - should they turn on?

I do not believe it has anything to do with ChasePlane. My original posting on CP was me going through a process of elimination. I still have this problem but it is ONLY with one aircraft - Carenado C208B and ONLY when I launch the saved flight from the Prepar3D Scenario screen, it does not CTD when I launch from within The Prepar3D Load Scenario screen. I and the P3D Lockheed Martin forum have spent many postings and checking to try and solve this issue - no luck. I have now approached Carenado with this problem. Here is my post with Lockheed Martin - P3D v4.3 - CTD at loading one aircraft - http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=130995 This problem is really strange.

You should contact Carenado. I think I may do that as well. I actually never had any problems with my C208B Grand Caravan or any of my other 5 or 6 other Carenado aircraft.

Thanks Bob, I just tried your suggestion but no luck. This is so frustrating and I really do not want to delete all my data and saved files and start over just for one aircraft - and to think it only happened after I installed and then uninstalled REX Wx Radar. The other thing that is strange which I cannot figure out is after I load a different saved flight and then either go into the P3D Load menu (or the FSUIPC Load Menu) and Load this C208B aircraft it loads perfectly well. But from scratch it causes P3D to hang and go to CTD. I guess with no solution I will have to load the C208B from within FSUIPC or P3D Load Menu.

I am experiencing a very strange problem that I have tried to fix but am now out of options - hopefully someone can offer some help. This problem ONLY occurs when I go to launch my Carenado C208B Grand Caravan from the Prepar3D Scenario menu - it does not matter if loading it from a Saved Flight or from picking the C208B from the Vehicle menu. There is no problem if I load a different Saved Flight (different aircraft) and once loaded I then pick the C208B from the vehicle menu or load it from the C208B Saved Flight - no CTD. I have had this aircraft for many months and never had an issue. This problem only started after loading REX Wx Radar and then uninstalling it due to some issues. I have uninstalled the C208B and reinstalled, I have done a P3D Repair for Client, Content, Scenery - not sure what else to try. Here are the Windows Event Viewer Logs for two separate CTD's: Faulting application name: PREPAR3D.EXE, version: 4.3.29.25520, time stamp: 0x5b2c3263 Faulting module name: api.dll, version: 4.3.29.25520, time stamp: 0x5b2c32fc Exception code: 0xc0000005 Fault offset: 0x0000000000015591 Faulting process id: 0x3094 Faulting application start time: 0x01d455443f9fc8e2 Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\PREPAR3D.EXE Faulting module path: C:\Program Files\Lockheed Martin\Prepar3D v4\api.dll Report Id: fa55a9c1-5c3e-4511-9608-2f2f78c9b3b9 Faulting package full name: Faulting package-relative application ID: EDIT: There was one other Windows Event Viewer report that I missed on my initial post... Faulting application name: Prepar3D.exe, version: 4.3.29.25520, time stamp: 0x5b2c3263 Faulting module name: facilities.dll, version: 4.3.29.25520, time stamp: 0x5b2c31d4 Exception code: 0xc0000005 Fault offset: 0x000000000001fa71 Faulting process id: 0x20e8 Faulting application start time: 0x01d45605e7804f10 Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\Program Files\Lockheed Martin\Prepar3D v4\facilities.dll Report Id: 14cc1655-5de6-4b8f-ba1a-990d896df801 Faulting package full name: Faulting package-relative application ID: ------------------------------------------------------------- Faulting application name: Prepar3D.exe, version: 4.3.29.25520, time stamp: 0x5b2c3263 Faulting module name: ntdll.dll, version: 10.0.17134.254, time stamp: 0xa5a334d4 Exception code: 0xc0000005 Fault offset: 0x000000000005a80b Faulting process id: 0x4f4 Faulting application start time: 0x01d45544975c8496 Faulting application path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 5d715eed-5c88-4364-9fdc-97048cccabcc Faulting package full name: Faulting package-relative application ID:

Thanks Keven, I will review further - just going thru process of elimination.

Every so often I get a P3D Not Responding message and then a CTD. I am trying to eliminate possibilities. This last time it occured when I was zooming out of the aircraft looking ahead at a landmark using my ChasePlane preset axis for zoom. Just wondering if this may have been a ChasePlane issue? Here is the Windows Log Report. The program Prepar3D.exe version 4.3.29.25520 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel. Process ID: 34ac Start Time: 01d44a4ecb67a61a Termination Time: 54 Application Path: C:\Program Files\Lockheed Martin\Prepar3D v4\Prepar3D.exe Report Id: 5137ac7c-55f6-47f7-bdc6-9b9918a0183a Faulting package full name: Faulting package-relative application ID:

Thanks Steve, I now understand

Hi Steve, thanks for your input. I am intrigued but also a bit confused at your method as stated above. Would you be so kind as to explain again with maybe some examples as I am not quite understanding. In my case I create a flight plan in LNM and then save it to a pln but then I also export it to GTN format. When in the aircraft I then import that GTN plan into my GTN750 but if there are waypoints that are not in the GTN AIRAC 1611, then GTN will lock the plan until you edit or remove the waypoints causing the issue. Could you explain your method again please and thank you.

Hi Dave, Well first let me say that Alex is really the guy that can give you all the expertise with this, but let me give you my little bit of knowledge. The GTN750 is the problem and not Little NavMap (LNM) as there is no way to update the GTN AIRAC as it is stuck at 1611. Therefore some waypoints from from LNM will cause GTN to be unhappy. It is a real nuisance but what I do is get the coordinates from LNM and then create new User Waypoints in GTN with whatever name you wish and then save those waypoints to your GTN User Waypoints Catalog. Alex - maybe you could expand a bit more on this for Dave. It sure would be great if there was somehow a way to auto save the LNM waypoints to the GTN waypoints catalog (for the ones that GTN does not like)