[Resolved] FCDU shuts down after landing.

[charliealfatango]

Had this happen twice. Long flight from EGPF to LGAV. Right after landing when taxing to gate FCDU just shutdown and vanished. 
Sending logs in email. 

[Travis]

I'm putting a hold on the release of 1.8.3 SP RC until I can look at this and make some tests.  My guess is it's a legacy bug....

I'll likely release MSFS Build 2 tomorrow (my Sunday) to the MSFS Testers unless I find that there's some cross-contamination.  (I think not, but I may be wrong.)

I do need one more bit of data from you though - please send me (here in the forum or in email) the Windows Event Log data for these "CTDs" of the FCDU.EXE.  Just look in the Event Viewer / Application for the correct (Error / Event 1000) data and copy everything from the events.

Best,

[charliealfatango]

Event Log:

Log Name: Application

Source: Application Error

Date: 6/17/2022 2:52:06 PM

Event ID: 1000

Task Category: (100)

Level: Error

Keywords: Classic

User: N/A

Computer: WIN10PROALEX

Description:

Faulting application name: FCDU.exe, version: 1.8.3.0, time stamp: 0x627e9d7d

Faulting module name: FCDU.exe, version: 1.8.3.0, time stamp: 0x627e9d7d

Exception code: 0x80000003

Fault offset: 0x00146a7c

Faulting process id: 0xf68

Faulting application start time: 0x01d882796c69ed46

Faulting application path: C:\Users\Public\Documents\Steam\steamapps\common\FSX\FSCaptain\bin\FCDU.exe

Faulting module path: C:\Users\Public\Documents\Steam\steamapps\common\FSX\FSCaptain\bin\FCDU.exe

[Travis]

Thanks.

I'll look into my code and try to replicate.

[charliealfatango]

Unrelated, just curiuous what are the numbers in the upper left corner of the FCDU. They sometimes turn red.

[Travis]

The numbers represent the FCDU Screen you are currently looking at - #35 is "Communications", #23 is "Flight Menu", etc.

When that number is red, it means your AI Freeze Ray is in effect, freezing some ground object that's close to you.  If the number is yellow, it means your AI Freeze Ray is active but not freezing anything.

You can set an option to have the AI Freeze Ray to be controlled by your Landing / Taxi lights by going to your Administrator's "Profile and Settings" dialog and clicking the "Weather and Hazards" button.

So when your landing and taxi lights are off, there is no Freeze Ray in operation.  But once you start to taxi, you will freeze surrounding generic SimObjects.  We can't freeze traffic generated by GSX or other add-ons.

Best,

[Travis]

Jun 19, 2022 18:28:15 GMT -5 Travis said:

I'll look into my code and try to replicate.

I had found two possible causes for this to happen, and I've added code to account for one, and to ameliorate for the second.

I tried to cause a CTD by focusing on the second method (and using the Beta FCDU), but couldn't cause a problem.

If I'm correct on the first possible cause, you might experience this CTD on any flight where you restored during the descent phase.  I should have that covered in the Release Candidate build though!

Best,

[Travis]

CAT,

Have you experienced this problem since installing the updated Release Candidate??

I would like to mark this as Resolved rather than Ongoing.

Best,

[charliealfatango]

Jul 11, 2022 11:50:50 GMT -5 Travis said:

CAT,

Have you experienced this problem since installing the updated Release Candidate??

I would like to mark this as Resolved rather than Ongoing.

Best,

Nope. We are good.

[Travis]

Cool beans!

I'm running some final flights tests... after taking a couple of days off for R & R... so I hope to have the Release Version ready for download by next Sunday July 17th.

(Barring any last-second bug reports, I'll be working on updating the User Guide until then.)

Best,

[Travis]

I did get a reply in email about an outstanding bug report not listed in the forum.  It appears to have been resolved, but I need to check with the affected Captain that there are not other related issues.

So look for an additional 48 hours delay in posting the Release Version - I'm looking at the 19th or 20th.

Best,

[Travis]

Captains,

The release will occur this coming Sunday - I want more time to test the changes as one of them is 'flight important.'

The first change was requested from someone new to FSCaptain.  Now that the FCDU uses Override Aircraft Configuration files as the primary set of Configuration files, we were asked why the Administrator opens pointing to the base "\Aircraft\" folder and not to the "\Aircraft\Overrides\".

So going forward, when you click on "Select" or "New", the Windows file selector will open in the \Aircraft\Overrides\ folder.

----

The other 'flight important' change request comes from a Captain who points out that in real life, airlines will inspect jetliners that land at or above "10 feet per second" which translates to 600fpm.  Such an incident would only apply to Captains who have enabled the Hazard Pack option to "Require A/C Inspections when damage occurs".

So we're changing the default values for the "Max Landing VSpeed" variable on the Aircraft Configuration files:

• Tiny = 600 fpm
• Small = 700 fpm
• Medium = 800 fpm
• Large = 900 fpm
• Heavy = 1000 fpm
  

These values are greater than the real-world values, and they will be used whenever a new Override Configuration file is created by the FCDU, and will be noted as "recommended" when saving in the Administrator.

However it will be okay to enter any value up to 1200 fpm if you feel you don't want to face an Inspection at the end of a flight leg!

And again, if you don't have "Require A/C Inspections when damage occurs", this just doesn't apply.

Best,