Thanks, gandy. As said, no offence intended in those statements of mine. I just had the folks in mind asking 'which sim?' all the time, while the plane's installers currently only support FSX.

CoolP wrote on Apr 24^th, 2012 at 12:32pm:


Yes please, we do not support any P3D issues. All products are FSX only.

Back to FSX, we need at least one ticket to put the CTD on the list.

Captain Sim wrote on Apr 24^th, 2012 at 3:22pm:
It appears to be random to me! I can't get it to do it again. Yet.

" X > GO FL290 > Dist 260nm (GO FL auto changed to 370 and time to 44) > Time 32 ............. press enter and immediate crash to FSX encountered error close program."

I believe the crashes I had were user error and totally confused the system.

Having found and read CoolP guide to using the PDCS I was trying to input data into the climb/descent intercept mode with information for the entire flight as per the FP rather than the climb/descent modes' intended use. I'm not surprised that my confusing data made it crash.

Goes to show that I mustn't play with toys until I've read and understood what I'm playing with.

Ian

Unfortunately I've just had another PDCS crash and this time I was only inputting the load data, nothing fancy. I was only using Battery and GPU as before.

I have found something from my event log that clever people than I may make sense of:


-      System
           -      Provider
                 [ Name]      Application Error

           -      EventID      1000
                 [ Qualifiers]      0

                 Level      2

                 Task      100

                 Keywords      0x80000000000000

           -      TimeCreated
                 [ SystemTime]      2012-04-25T18:18:46.000000000Z

                 EventRecordID      15963

                 Channel      Application

                 Computer      Ian-PC

                 Security

-      EventData
                 fsx.exe
                 10.0.61472.0
                 475e17d3
                 MSVCR90.dll
                 9.0.30729.6161
                 4dace5b9
                 c0000417
                 00036d36
                 d34
                 01cd22ef5e48b2c6
                 C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
                 C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50
934f2ebcb7eb57\MSVCR90.dll
                 18572afe-8f03-11e1-91e1-50e549403fac


Faulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3
Faulting module name: MSVCR90.dll, version: 9.0.30729.6161, time stamp: 0x4dace5b9
Exception code: 0xc0000417
Fault offset: 0x00036d36
Faulting process id: 0xd34
Faulting application start time: 0x01cd22ef5e48b2c6
Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50
934f2ebcb7eb57\MSVCR90.dll
Report Id: 18572afe-8f03-11e1-91e1-50e549403fac


Is this of value?

CXA546 wrote on Dec 14^th, 2012 at 2:50am:
No. Not fixed yet. We'll have to wait until the next update (v1.1).

I just enter the data slowly (don't hurriedly enter the info) and that usually prevents the PDCS from causing a CTD.

But it would be nice to have it fixed.