samik Posted May 21, 2016 Report Share Posted May 21, 2016 I purchased the Eaglesoft Cessna Citation X recently and was advised to purchase a registered version of FSUIPC along to have a fully functional fadec. I followed the advise and purchased a registered FSUIPC 4 and set up the joystick and throttle. Both are working fine with a throttle idle of 24% N1. I applied the axeswrongrange = yes, as advised in some online fora. My problem is that with the ES Cessna aircraft, FSX crashes to desktop randomly. Recently the crashes have become too frequent and happen right on the ground while setting up FMS. I have read some posts about this issue and understand it is related to corrupt weather files. So I deleted the .WX files from document folder as well as the waether. bin file from appdata\roaming folder as advised. However this did not solve the problem and FSX crashed at the very next flight on ground. I am producing below excerpts from the log file for the events that happened during the crash. Please help me with this issue so that I have a good return on the investments I made on these two apparently top class softwares related to flight sim. Pls do not keep me waiting at moderation and I request a response at the earliest. Regards, Samik ********* FSUIPC4, Version 4.949p by Pete Dowson ********* fsx.exe version = 10.0.61637.0 Reading options from "C:\FSX\Modules\FSUIPC4.ini" Running inside FSX on Windows 7 Module base=616E0000 User Name="samik gupta" User Addr="samik66@yahoo.com" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 1125 System time = 21/05/2016 18:12:11 1125 FLT path = "C:\Users\samik\Documents\Flight Simulator X Files\" 1141 ------ Module Version Check ------ 1141 acontain.dll: 10.0.61637.0 1141 api.dll: 10.0.61637.0 1141 controls.dll: 10.0.61637.0 1141 fs-traffic.dll: 10.0.61637.0 1141 G3D.dll: 10.0.61637.0 1141 language.dll: 10.0.61637.0 1141 sim1.dll: 10.0.61637.0 1141 visualfx.dll: 10.0.61637.0 1141 weather.dll: 10.0.61637.0 1141 window.dll: 10.0.61637.0 1141 ---------------------------------- 1547 Trying to connect to SimConnect Acc/SP2 Oct07 ... 1563 FS path = "C:\FSX\" 2031 ---------------------- Joystick Device Scan ----------------------- 2047 Product= MetalStrik 3D 2047 Manufacturer= MetalStrik 3D 2047 Vendor=0583, Product=B011 (Version 1.0) 2047 Serial Number= MetalStrik 3D 2047 Product= Wireless Device 2047 Manufacturer= Lite-On Technology Corp. 2047 Vendor=04CA, Product=006F (Version 0.53) 2047 Serial Number= Lite-On Technology Corp. 2047 ------------------------------------------------------------------- 2078 LogOptions=F0000000 0000001F 2078 ------------------------------------------------------------------- 2078 ------ Setting the hooks and direct calls into the simulator ------ 2078 --- CONTROLS timer memory location obtained ok 2094 --- SIM1 Frictions access gained 2110 --- FS Controls Table located ok 2110 --- Installed Mouse Macro hooks ok. 2110 --- Wind smoothing fix is fully installed 2110 --- G3D.DLL fix attempt installed ok 2110 --- All links checked okay 2110 ------------------------------------------------------------------- 2110 SimConnect_Open succeeded: waiting to check version okay 2110 Trying to use SimConnect Acc/SP2 Oct07 14219 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 14219 Initialising SimConnect data requests now 14219 FSUIPC Menu entry added 14297 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 14297 *** EVENT: Cntrl= 66078 (0x0001021e), Param= 2016 (0x000007e0) ZULU_YEAR_SET 14297 *** EVENT: Cntrl= 66077 (0x0001021d), Param= 142 (0x0000008e) ZULU_DAY_SET 14297 *** EVENT: Cntrl= 66075 (0x0001021b), Param= 12 (0x0000000c) ZULU_HOURS_SET 14297 *** EVENT: Cntrl= 66076 (0x0001021c), Param= 42 (0x0000002a) ZULU_MINUTES_SET 14297 C:\FSX\FLIGHTS\OTHER\FLTSIM.FLT 14297 C:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR 14969 READ1[6792] 3304, 4 bytes: 10 00 49 49 ..II 14969 READ1[6792] 3308, 4 bytes: 08 00 DE FA .... 14969 Memory in use: 754Mb, Avail=3342Mb 15453 READ1[6792] 290C, 4 bytes: 38 00 00 00 8... 15453 READ1[6792] 320C, 4 bytes: 38 00 00 00 8... 15563 READ1[6792] 8320, 1 bytes: 02 . 15563 READ1[6792] 0B63, 1 bytes: 00 . 15563 READ1[6792] 3306, 2 bytes: 49 49 II 15563 READ1[6792] 0238, 10 bytes: 00 00 00 00 00 00 00 00 00 00 .......... 15563 READ1[6792] 3C00, 256 bytes: 43 3A 5C 46 53 58 5C 53 69 6D 4F 62 6A 65 63 74 C:\FSX\SimObject 15563 73 5C 41 69 72 70 6C 61 6E 65 73 5C 41 69 72 63 s\Airplanes\Airc 15563 72 65 61 74 69 6F 6E 5F 35 38 32 53 4C 5C 41 69 reation_582SL\Ai 15563 72 63 72 65 61 74 69 6F 6E 5F 35 38 32 53 4C 2E rcreation_582SL. 15563 41 49 52 00 00 00 00 00 00 00 00 00 00 00 00 00 AIR............. 15563 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ ******************************************************************************************************************************************************** 588735 READ1[6792] 3500, 24 bytes: 43 37 35 30 00 00 00 00 00 00 00 00 00 00 00 00 C750............ 588735 00 00 00 00 00 00 00 00 ........ 588735 READ1[6792] 3D00, 256 bytes: 45 61 67 6C 65 73 6F 66 74 20 43 69 74 61 74 69 Eaglesoft Citati 588735 6F 6E 20 58 20 32 2E 30 20 4E 38 30 30 45 53 00 on X 2.0 N800ES. 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 READ1[6792] 3148, 24 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 ........ 588735 READ1[6792] 3130, 12 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 ............ 588735 READ1[6792] 313C, 12 bytes: 4E 38 30 30 45 53 00 00 00 00 00 00 N800ES...... 588735 READ1[6792] 0240, 2 bytes: E0 07 .. 588735 READ1[6792] 023E, 2 bytes: 8E 00 .. 588735 READ1[6792] 023B, 1 bytes: 0C . 588735 READ1[6792] 023C, 1 bytes: 33 3 588735 READ1[6792] 0238, 1 bytes: 0E . 588735 READ1[6792] 0239, 1 bytes: 33 3 588735 READ1[6792] 023A, 1 bytes: 39 9 588735 READ1[6792] 0248, 2 bytes: 01 00 .. 588735 READ1[6792] 0D70, 40 bytes: 4C 75 61 20 46 53 50 53 00 00 00 00 00 00 00 00 Lua FSPS........ 588735 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 588735 00 00 00 00 00 00 00 00 ........ 588735 READ1[6792] 0D6C, 4 bytes: 00 00 00 00 .... 588735 Exception 15 "WEATHER_UNABLE_TO_GET_OBSERVATION", Ref 6133, Index param -1 on Weather request type 5 588735 WX Error: Exception 15, WX request type 5, Lat=48.9958, Lon=2.5544, Alt=0.0m 588735 WRITE0[6792] 310A, 2 bytes: 08 00 .. 588735 READ0[6792] 332E, 2 bytes: 00 00 .. 588735 READ0[6792] 3330, 2 bytes: 00 00 .. 588735 READ0[6792] 3332, 2 bytes: 00 00 .. 588735 WRITE0[6792] 088C, 2 bytes: 01 00 .. 588735 WRITE0[6792] 0924, 2 bytes: 01 00 .. 588735 READ0[6792] 7B92, 1 bytes: 00 . 588735 WRITE0[6792] 7B92, 1 bytes: 00 . 588735 READ0[6792] 7B9B, 1 bytes: 00 . 604563 Weather Read request (At Aircrft) to area 4: Lat=49.00, Lon=2.55, Alt=121.0, Req=2 604563 Weather Read request (Nr Station) to area 5: Lat=49.00, Lon=2.55, Alt=0.0, Req=1 606063 System time = 21/05/2016 18:22:15, Simulator time = 14:51:58 (12:51Z) 606063 *** FSUIPC log file being closed Minimum frame rate was 3.5 fps, Maximum was 4.3 fps Minimum available memory recorded was 1669Mb Average frame rate for running time of 244 secs = 3.8 fps G3D fix: Passes 17626, Null pointers 0, Bad pointers 0, Separate instances 0 Maximum AI traffic for session was 87 aircraft Memory managed: 59 Allocs, 59 Freed ********* FSUIPC Log file closed *********** Link to comment Share on other sites More sharing options...
Pete Dowson Posted May 21, 2016 Report Share Posted May 21, 2016 26 minutes ago, samik said: Pls do not keep me waiting at moderation and I request a response at the earliest. I always respond as soon as I'm able, but also sometimes I am holiday, and if it is something no one else can handle then you would have to wait! Quote ********* FSUIPC4, Version 4.949p by Pete Dowson ********* The version of FSUIPC you are using is out of date and no longer supported. Please update to the current supported version, 4.953. Do this before your next report, please. Meanwhile, your log is very large because appear to have turned on most of the optional logging. PLEASE DO NOT. Turn them all off before you supply another log. After that you do not even need to visit the Logging TAB, as the log is always made and if there are problems they will be logged. Looking at the end of the log as posted: Quote 606063 *** FSUIPC log file being closedMinimum frame rate was 3.5 fps, Maximum was 4.3 fpsMinimum available memory recorded was 1669MbAverage frame rate for running time of 244 secs = 3.8 fpsG3D fix: Passes 17626, Null pointers 0, Bad pointers 0, Separate instances 0Maximum AI traffic for session was 87 aircraftMemory managed: 59 Allocs, 59 Freed********* FSUIPC Log file closed *********** This shows that FSUIPC closed normally, and to do so it mst have been told that FS was closing normally. There is no crash before FSUIPC closed. One thing I would note here is that the frame rates reported of 3.5-4.3 averaging 3.8 are dismal and unflyable, but maybe that was simply because the system was initialising all that time. You appear to have closed FS deliberately after just 4 minutes or so. If you want help with a crash You always need to show 1) the Windows crash details, which give the module and location. If you don't capture this at the time, on screen, you can get it from the Windows Event Viewer, and 2) an FSUIPC4.LOG from the session with the crash, not one related to a normally closed session like the one above. Pete Link to comment Share on other sites More sharing options...
samik Posted May 22, 2016 Author Report Share Posted May 22, 2016 Hi Pete Thanks for your response. I updated to the latest version of FSUIPC and again tried a flight on the ES Cessna Citation X. FSX stopped working within 2 minutes of take off. Please advise next step for me. Regards Sam ********* FSUIPC4, Version 4.953 (18th May 2016) by Pete Dowson ********* fsx.exe version = 10.0.61637.0 Reading options from "C:\FSX\Modules\FSUIPC4.ini" Running inside FSX on Windows 7 Module base=1A3C0000 User Name="samik gupta" User Addr="samik66@yahoo.com" FSUIPC4 Key is provided WIDEFS7 not user registered, or expired 641 System time = 22/05/2016 20:25:07 641 FLT path = "C:\Users\samik\Documents\Flight Simulator X Files\" 641 ------ Module Version Check ------ 641 acontain.dll: 10.0.61637.0 641 api.dll: 10.0.61637.0 641 controls.dll: 10.0.61637.0 641 fs-traffic.dll: 10.0.61637.0 641 G3D.dll: 10.0.61637.0 641 language.dll: 10.0.61637.0 641 sim1.dll: 10.0.61637.0 641 visualfx.dll: 10.0.61637.0 641 weather.dll: 10.0.61637.0 641 window.dll: 10.0.61637.0 641 ---------------------------------- 1078 Trying to connect to SimConnect Acc/SP2 Oct07 ... 1125 FS path = "C:\FSX\" 1609 ---------------------- Joystick Device Scan ----------------------- 1625 Product= MetalStrik 3D 1625 Manufacturer= MetalStrik 3D 1625 Vendor=0583, Product=B011 (Version 1.0) 1625 Serial Number= MetalStrik 3D 1625 Product= Wireless Device 1625 Manufacturer= Lite-On Technology Corp. 1625 Vendor=04CA, Product=006F (Version 0.53) 1625 Serial Number= Lite-On Technology Corp. 1625 ------------------------------------------------------------------- 1672 LogOptions=00000000 00000001 1672 ------------------------------------------------------------------- 1672 ------ Setting the hooks and direct calls into the simulator ------ 1672 --- CONTROLS timer memory location obtained ok 1719 --- SIM1 Frictions access gained 1719 --- FS Controls Table located ok 1719 --- Installed Mouse Macro hooks ok. 1719 --- Wind smoothing fix is fully installed 1719 --- G3D.DLL fix attempt installed ok 1719 --- All links checked okay 1719 ------------------------------------------------------------------- 1719 SimConnect_Open succeeded: waiting to check version okay 1719 Trying to use SimConnect Acc/SP2 Oct07 15516 Running in "Microsoft Flight Simulator X", Version: 10.0.61637.0 (SimConnect: 10.0.61259.0) 15516 Initialising SimConnect data requests now 15516 FSUIPC Menu entry added 15609 C:\FSX\FLIGHTS\OTHER\FLTSIM.FLT 15609 C:\FSX\SimObjects\Airplanes\Aircreation_582SL\Aircreation_582SL.AIR 195031 C:\Users\samik\Documents\Flight Simulator X Files\IFR Arlanda to Kastrup.PLN 212266 Weather Mode now = Theme 247281 C:\FSX\SimObjects\Airplanes\Eaglesoft Citation X 2.0\CitationX.AIR 352734 System time = 22/05/2016 20:30:59, Simulator time = 16:55:24 (14:55Z) 352750 Aircraft="Eaglesoft Citation X 2.0 N800ES" 353687 Starting everything now ... 354031 Advanced Weather Interface Enabled 653344 Sim stopped: average frame rate for last 301 secs = 6.0 fps 653344 Max AI traffic was 23 aircraft 653344 Average weather filter write interval in that time = 37677.8 msecs 944406 .PLN 969656 System time = 22/05/2016 20:41:16, Simulator time = 17:11:03 (15:11Z) 969656 *** FSUIPC log file being closed Minimum frame rate was 4.1 fps, Maximum was 11.2 fps Minimum available memory recorded was 1734Mb Average frame rate for running time of 601 secs = 6.1 fps Average weather filter write interval in that time = 75115.3 msecs G3D fix: Passes 16627, Null pointers 0, Bad pointers 0, Separate instances 0 Maximum AI traffic for session was 24 aircraft Memory managed: 157 Allocs, 157 Freed ********* FSUIPC Log file closed *********** Link to comment Share on other sites More sharing options...
Pete Dowson Posted May 22, 2016 Report Share Posted May 22, 2016 10 minutes ago, samik said: Hi Pete Thanks for your response. I updated to the latest version of FSUIPC and again tried a flight on the ES Cessna Citation X. FSX stopped working within 2 minutes of take off. Please advise next step for me. Again, just as before the log clearly shows that FS did not crash, and that FSUIPC terminated normally, look: 969656 *** FSUIPC log file being closed Minimum frame rate was 4.1 fps, Maximum was 11.2 fps Minimum available memory recorded was 1734Mb Average frame rate for running time of 601 secs = 6.1 fps Average weather filter write interval in that time = 75115.3 msecs G3D fix: Passes 16627, Null pointers 0, Bad pointers 0, Separate instances 0 Maximum AI traffic for session was 24 aircraft Memory managed: 157 Allocs, 157 Freed ********* FSUIPC Log file closed *********** If you are not telling FS to close down, something else is, but it is patently nothing whatsoever to do with FSUIPC! If you think FS is crashing, where is the crash information from Windows? And if there is a crash at all, it is certainly occurring AFTER FS was closing down in any case! I really cannot help diagnose problems with other folks' software. Sorry. Perhaps you should try Eaglesoft, if this is the only thing you have this problem with? Pete Link to comment Share on other sites More sharing options...
samik Posted May 22, 2016 Author Report Share Posted May 22, 2016 Hi Pete Thank you, this time I went into the Windows event viewer after another unexpected FSX shutdown with the ES Cessna. The following are the detais: Although I kmow this is not related to FSUIPC, can you please help me diagnose the meaning and what I should do? I will ppreciate your guidance. + System - Provider [ Name] Application Error - EventID 1000 [ Qualifiers] 0 Level 2 Task 100 Keywords 0x80000000000000 - TimeCreated [ SystemTime] 2016-05-22T18:11:35.457707500Z EventRecordID 3698 Channel Application Computer HP Security - EventData fsx.exe 10.0.61637.0 46fadb14 ntdll.dll 10.0.10586.306 571afb7f c0000374 000dc7c9 2fe0 01d1b450e9094cbf C:\FSX\fsx.exe C:\WINDOWS\SYSTEM32\ntdll.dll 7662ab4a-ba05-458b-b21c-f68442a25af4 Link to comment Share on other sites More sharing options...
Pete Dowson Posted May 22, 2016 Report Share Posted May 22, 2016 Quote this time I went into the Windows event viewer after another unexpected FSX shutdown with the ES Cessna. The following are the detais: You've never shown me a FSUIPC log after such a shutdown -- the two you showed so far show normal closing actions, something which certainly wouldn't happen after an error such as the one you show above . I don't know what error C0000374 is, but the module NTDLL is a central part of Windows and provides many of the functions all programs make a lot of use of. so, apart from going through a process of elimination (stopping assorted add-ons, possibly reinstalling FS and so on), the only think I can think of trying is repairing Windows and if that doesn't help, re-installing it. Googling the error I did find this, which mainly relates to the same error during a Windows update, but you might find it useful to follow the same advice: https://www.sysnative.com/forums/windows-update/15943-windows-update-error-code-c0000374.html Pete Link to comment Share on other sites More sharing options...
WarpD Posted May 23, 2016 Report Share Posted May 23, 2016 Pete, Perhaps I can offer some information. I see a crash whenever I have FSUIPC loaded into FSX/Prepar3d and the last known module I see in the Call Stack list is FSUIPC4.DLL. I just had the crash happen and the call stack says: ->F9001810() FSUPIC4.DLL!14698623() [Frames below may be incorrect and/or missing, no symbols loaded for FSUIPC4.dll] etc.. etc.. I have no idea what is causing the crash... just that FSUIPC is the last named module in the call stack and perhaps this info may (probably not) be of help. I can tell you that I can catch this crash in Visual Studio no matter what aircraft I'm currently working on, code wise... so it's not aircraft specific, just something showing when I run my stuff. I also have another issue regarding FSUIPC and SimConnect I would like to discuss with you, however I'll make a separate thread for that sir. Ed Wilson Link to comment Share on other sites More sharing options...
Pete Dowson Posted May 23, 2016 Report Share Posted May 23, 2016 1 hour ago, WarpD said: Perhaps I can offer some information. I see a crash whenever I have FSUIPC loaded into FSX/Prepar3d and the last known module I see in the Call Stack list is FSUIPC4.DLL. I just had the crash happen and the call stack says: I have no idea what is causing the crash... just that FSUIPC is the last named module in the call stack and perhaps this info may (probably not) be of help. I can tell you that I can catch this crash in Visual Studio no matter what aircraft I'm currently working on, code wise... so it's not aircraft specific, just something showing when I run my stuff. Always crashing, FSX and P3D? If this was happening to everyone the Forum would be littered with nothing else. What does the crash actually say -- what module, what offset? The stack is little use as it looks like it is corrupt. FSUIPC might be the last DLL standing because it tried to tidy up, sending termination notices etc. What "stuff" of yours is running which might interact so? Pete Link to comment Share on other sites More sharing options...
WarpD Posted May 24, 2016 Report Share Posted May 24, 2016 It's an access violation trying to read the address I listed above. That was while I was in Visual Studio so no module listed and no Windows error because I had to terminate my debug session on my own stuff. My 'stuff'... is gauge code for aircraft. It's not doing anything fancy, just reading sim variables and displaying stuff in the avionics. Link to comment Share on other sites More sharing options...
Pete Dowson Posted May 24, 2016 Report Share Posted May 24, 2016 5 hours ago, WarpD said: It's an access violation trying to read the address I listed above. That was while I was in Visual Studio so no module listed and no Windows error because I had to terminate my debug session on my own stuff. Aren't the crashes logged in the Windows event log, seen in the Event Viewer? Doesn't that identify the module? The stack address is just somewhere in a Windows DLL I expect. All that upper region of virtual memory is reserved for that stuff. As for FSUPIC4.DLL!14698623() For the address here to mean anything to me I need the FSUIPC base address -- see if you still have the FSUIPC4 Log, because it is logged in there. Maybe, if it is FSUIPC4, it will tell me which Windows API function it's in at the time. Pete Link to comment Share on other sites More sharing options...
WarpD Posted May 24, 2016 Report Share Posted May 24, 2016 I will ensure to collect this information on the next crash. I don't know what is causing it, and I'm not willing to say it's FSUIPC that's doing anything. I just see it as the recognizable module in the stack list and hope that somehow the two of us can figure out what's actually happening and make it go away. Link to comment Share on other sites More sharing options...
Ted Striker Posted May 25, 2016 Report Share Posted May 25, 2016 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 Link to comment Share on other sites More sharing options...
Pete Dowson Posted May 25, 2016 Report Share Posted May 25, 2016 15 minutes ago, Ted Striker said: 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. 15 minutes ago, Ted Striker said: 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. 15 minutes ago, Ted Striker said: 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. All the above results seem to immediately point to something related to the database handling, yet at the end you conclude: 15 minutes ago, Ted Striker said: 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. The only likely difference in any recent version of FSUIPC is that the memory arrangement of data is likely to be different. If there is an error somewhere else which references incorrect memory locations, perhaps because of data poointer corruptions or uninitialised variables, then whether a crash results depends purely on whether the memory so referenced is actually valid in the current process -- i.e. it is an allocated region of memory and has appropriate read/write access enabled. Small differences in memory arrangments because of updated modules can make the difference betwen such erroors crashing or just possibly creating a blip which goes unnoticed. BTW I cannot support versions earlier than the current released installer package, which is 4.953. There is a later one available in the Download Links subforum (4.954c) which you could also try. You never know, another small change in meory arrangement could make another difference. Pete Link to comment Share on other sites More sharing options...
Ted Striker Posted May 25, 2016 Report Share Posted May 25, 2016 (edited) 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 Edited May 25, 2016 by Ted Striker wrote wrong FSUIPC version number Link to comment Share on other sites More sharing options...
Pete Dowson Posted May 25, 2016 Report Share Posted May 25, 2016 4 hours ago, Ted Striker said: 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? Not really. The best would be the debuggers withing software development tools, like Visual Studio. But in cases like this you wouldn't know where to begin, and WarpD has already trapped the error at least once in a debugger and hasn't figured it out. The only way I know, especially with the sorts of errors which are due to unallocated memory access, is to undertake a thorough process of elimination. From what you found earlier I think you may have pretty much done that -- it's likely to be either bad data (especially indicated because of that comment of yours " I tried deleting this in the FMS flight plan and got an immediate crash", which in fact eliminates FSUIPC straight away because there is no way FSUIPC is involved in private interactions between you and any aircraft's FMS). Again, the other comment where you got a much earlier crash after changing something involving FMS data reinforces this (" 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"). This so much points towards a possible error in the FMS treatment of data, or possibly erroneous data, that I'm rather surprised that WarpD hasn't decided to put some additional logging into that code in order to narrow it down within. That's what I'd do. Pete Link to comment Share on other sites More sharing options...
Ted Striker Posted May 26, 2016 Report Share Posted May 26, 2016 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 Link to comment Share on other sites More sharing options...
Pete Dowson Posted May 26, 2016 Report Share Posted May 26, 2016 12 minutes ago, Ted Striker said: Is there a way I can tell the FSUIPC installer not to update FSX when I run the installer to update P3D? No, not without removing entries from the Registry so it doesn't appear to be installed. If you use an old version of FSUIPC I cannot support it. Pete Link to comment Share on other sites More sharing options...
Ted Striker Posted May 26, 2016 Report Share Posted May 26, 2016 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 Link to comment Share on other sites More sharing options...
samik Posted May 26, 2016 Author Report Share Posted May 26, 2016 Ted... going by your method I made some trials this evening: I tried two flights from KSEA to KLAX with ES Cessna Citation X. As usual FSX stopped right after take off before reaching the first waypoint. Then I installed an older version of FSUIPC 4.853 which I had and tried the same flight with exact route and SID. The flight is still working satisfactory and I am 20 mins into it. No malfunction or stoppage observed. I am not qualified to comment on the nitty grittys of FSUIPC, but will tend to agree that there is something conflicting about the latest FSUIPC and Citation X. I will complete a few more flights and report back by the weekend before I draw any conclusion. Thanks anyway for suggesting the shortcut to some enjoyable flights with is wonderful aircraft. Regds Sam Link to comment Share on other sites More sharing options...
Ted Striker Posted May 29, 2016 Report Share Posted May 29, 2016 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 Link to comment Share on other sites More sharing options...
Pete Dowson Posted May 29, 2016 Report Share Posted May 29, 2016 4 hours ago, Ted Striker said: 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 But where is the Event Viewer data for me to look at, and the FSUIPC4.LOG file up to that point? Maybe I could try to narrow it down, but I cannot even start with no information. With the location in API.DLL and the normal FSIOPC logging I might just be able to track back to what function it was attempting to perform at the time and whether FSUIPC could have any involvement in that. Please make are you are using FSUIPC 4.95 at the time, as I still have mapping files for that. Thanks, Pete Link to comment Share on other sites More sharing options...
Ted Striker Posted May 29, 2016 Report Share Posted May 29, 2016 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 Link to comment Share on other sites More sharing options...
Pete Dowson Posted May 29, 2016 Report Share Posted May 29, 2016 3 hours ago, Ted Striker said: I also attached the FSUIPC 4.953 log file to my first post above. Yes, but I needed the crash data and Log for the same event. The main use of the Log is for the "Module base" and the versions of each of the FS Modules linked to. 3 hours ago, Ted Striker said: I did a search on the event id and exception code but did not come up with anything specific. C0000005 is an access violation. I described why this is proably happening earlier. I think something in the Add-On aircraft code is using an incorrect, unchecked or uninitialised pointer. I'll see if I can track which action in API is being used when it crashed, but I don't offer much hope. We'd really need a stack trace, and that would mean running it under a debugger. If the API crash is so easy to reproduce I'm amazed the add-on author hasn't done this already! I don't have the aircraft and I'm not going to buy it to find a problem in someone else's code. Pete Link to comment Share on other sites More sharing options...
Pete Dowson Posted May 29, 2016 Report Share Posted May 29, 2016 I've analysed this as far as I can get. The place where it crashes in the version of API.DLL you are using (FSX/Accel) is deep in a small routine called in many places. Without a debug trace it's hopeless. tracking back up could take so many branches reaching the calling API function could take weeks. Not only that, but the code in my version of FSX (FSX-SE build 62615) is substantially different. So I'm not convinced it would even happen at all here assuming I had the aircraft in question. You should also note that this thread started which was a different crash altogether, though there was never any relevant data supplied. It was that one to which the aircraft's author was presumably referring in his response here, some time back. Quite honestly, the aircraft author is the person best placed to sort this out. If he does identify something FSUIPC is doing which explicitly somehow conflicts (only!) with his code, then I'll gladly look at resolving it as best I can from my end. [LATER] It's just occurred to me that the very last entry in both Logs you submitted end on the line ".PLN". Now this line should be giving the name of the flight plan which SimConnect tells FSUIPC has just been loaded. But it has no filename at all! Could this attempt to load, into FS, a flight plan with no name somehow crash API.DLL? I know that DLL is involved in interpreting flight plans. It seems to me that something you are doing, or the add-on is doing, may be attempting to load a plan which is causing that process to fail. Can you check the FSUIPC log from a run with new of the FSUIPC versions you say "works"? What are the lines shortly after the one saying "Advanced Weather Interface Enabled"? I just checked, and the second log posted by the thread starter also had this ".PLN" line in it: 354031 Advanced Weather Interface Enabled 653344 Sim stopped: average frame rate for last 301 secs = 6.0 fps 653344 Max AI traffic was 23 aircraft 653344 Average weather filter write interval in that time = 37677.8 msecs 944406 .PLN 969656 System time = 22/05/2016 20:41:16, Simulator time = 17:11:03 (15:11Z) 969656 *** FSUIPC log file being closed It was soon after that line that the sim closed down. No error, just a close. The user says he didn't close it! Pete Link to comment Share on other sites More sharing options...
Ted Striker Posted May 30, 2016 Report Share Posted May 30, 2016 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 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now