Ted Striker

Just wanted to update this issue. Eaglesoft thinks they found the cause of this and are working on an update. For anyone else experiencing these crashes, until the update is released, they can be prevented by reloading the aircraft after the flight and aircraft are initially loaded. Ted

Pete, I appreciate what you have done so far and am impressed how much you were able to determine with the little information that was in the files I attached. I was just hoping that my narrowing the issue occurring to going from version 9.949 to 9.50 would give you a clue. I have attached a log from FSUIPC 4.949. I don't see anything different between it and 9.50 up to the line with .pln. In the flight that did not crash, 9.949, I flew the plane to the point that I knew it would not crash and then ended the flight manually. Anyway, do not waste anymore time analyzing this as I expect it is some access violation with a file in my system that I need to find. Between windows security, changes from windows updates, software theft protection routines, and over-zealous anti-virus software it doesn't take much to trip up a computer these days. When I get a chance I will run Process Explorer and Process Monitor in parallel with the sim and see if I get any clues. If so I will post them here. Thanks for spending the time on this, Ted FSUIPC4.949.log

Pete, I have attached the FSUIPC log file and event viewer details for the api.dll crash I got with FSUIPC 4.95. I also attached the FSUIPC 4.953 log file to my first post above. There isn't much in the log files. I did a search on the event id and exception code but did not come up with anything specific. Hopefully something in the event viewer details will mean something to you. Thanks, Ted FSUIPC4.95.log api.dll crash event viewer details.txt

I had a little time to do some more testing this morning. The Eaglesoft Citation X flies fine for me up through FSUIPC 4.949. With FSUIPC 4.95 and higher the sim stops functioning shortly after takeoff with an api.dll fault in the event viewer. When and if I get time I will dig into it a little deeper with Process Explorer and Process Monitor, but that is about the limit of my knowledge on the inner workings of windows processes. Ted

Thanks Pete. Understood on the no support for older versions. Unfortunately I have no other option with this plane at this time if it doesn't work with your latest FSUIPC and the latest NAV database. I'll let you know if I get any improvement. Ted

What's got me confused is that the latest FSUIPC works with the old data and the old FSUIPC works with the new data, but the new data and the new FSUIPC crashes. If Ed can't figure it out and he developed the CX then I probably won't have much luck either. At least I can still use the CX in FSX with the older FSUIPC. I have FSX, P3Dv2, and P3Dv3 on my system. Is there a way I can tell the FSUIPC installer not to update FSX when I run the installer to update P3D? Currently it updates all 3 which in most cases would be just fine. I'm not at my flight sim computer to look at the manual so if the instructions are in the manual you can just say that. Appreciate your feedback and assistance Pete, Ted

Thanks for the feedback Pete. I don't know what the cause of these crashes are other than the API.dll fault in the event viewer. All I know is that something is incompatible when the newer versions of FSUIPC, latest NAV DATA and the Citation X are installed together. I will try the FSUIPC 4.954c version. I don't know anything about the inner working of .dlls or memory management. Can you recommend a tool that I can use to investigate these memory access violations? Thanks, Ted

Pete, I have been experiencing a "the sim has stop working" error using the Eaglesoft Citation X also and may be able to add some helpful information. I installed the latest version of the CX into P3DV3 with the FSUIPC 4.95 and the latest airac cycle 1605. I was getting sim crashes at numerous airports. I concentrated on a departure from Las Vegas using the following flightplan for testing as I was getting consistent crashes right after takeoff seconds after reducing the throttle from TO to CLB. KLAS 25R BOACH6 HEC RIIVR2 KLAS I then updated to FSUIPC 4.953 but that did not solve the problem. At this point I did not know if it was my system, the updated Eaglesoft CX, the updated FSUIPC, or the latest NAV cycle. The only addons activated in P3Dv3 were the Citation X, FSUIPC, and the 1605 Nav Database. The error I was getting in the event viewer was a P3Dv3 crash due to the API.DLL. I have attached my FSUIPC log. Since an earlier version of the CX worked for me in FSX I installed all the above addons into FSX but I had the same sim crash due to api.dll From testing I discovered the following: 1) If I disabled FSUIPC in the XML.DLL the crash did not occur, however the FADEC no longer worked on the CX as it depends on FSUIPC 2) If I used the original Nov 2011 Nav database that comes with the CX with FSUIPC enabled the crash did not occur indicating that it might be a Nav cycle error. 3) The obvious difference between the two NAV databases is the first departure waypoint named ALTO that only exists on the latest database. I tried deleting this in the FMS flight plan and got an immediate crash. I restarted the sim and this time tried to modify the ALTO altitude constraint from 2580A to 1000A. The sim crashed rolling down the runway on takeoff. 4) Last but not least and probably the most significant, I removed FSUIPC 4.953 and replaced it with an older 4.853 version. The flight was fine with no crashes with the 1605 Nav database. This discovery and the other posts in this thread indicated to me that there may be a conflict with the CX and the latest versions of FSUIPC. I hope this is helpful and look forward to your thoughts on this. Let me know if you need anything else. Ted FSUIPC4.953.log