|
|
Post by pakradm on May 27, 2021 14:20:47 GMT -5
Hello,
My FSCaptain Version is 1.8.1 & I'm using P3D v3.4.
I think there is a problem in FSCaptain that in any situation when I click EMERGENCY on FCDU, The FSCaptain will close my flight by reduce my score from 85 to 65 because of "Cancellation/Pilot Error -20" in flight log details.
For example when I have a random failure by FSLabs A320 & I should make an emergency landing by proceed EMERGENCY page, FSCaptain will set my score to 65! 
Also I have a question... what's difference between EMERGENCY & CANCEL FLT?
I have tested CANCEL FLT with random failure of FSLabs A320, but it doesn't reduce my score & it will leave as 85.
I have tested the above situation with another aircraft like QualityWings BAe146. For example after takeoff reject by BAe146 & proceed EMERGENCY page again my score will deduct to 65!
Regards
|
|
|
|
Post by Travis on May 27, 2021 23:48:09 GMT -5
Hi Pakradm,
FSCaptain 1.8.1 is over two years old, so I would have to compare it against a similar aircraft to see what you might be experiencing. Since I don't have P3D3, that's not really possible.
CANCEL FLIGHT simple cancels the flight. Declaring an EMERGENCY does the same thing... but if an "Emergency situation" isn't active, then you'll be dinged points for an "improperly declared emergency". Since we can't detect FSL A32x nor QW BAE146 failures, I would suggest that you simply Cancel the flight when they occur.
Best,
|
|
|
|
Post by cxn4026 on Jul 26, 2021 9:04:30 GMT -5
I just had a similar one.
I was descending to ZSPD with CS757III and doing prepare, suddenly the AP disconnected, and FSC's FO told me there is an electric system failure, but I found that the main flight control is the issue I facing, It's like a simulated hydraulic failure, it will jump back to zero when I have joystick stopped to some fixed value. So for my feeling, it's kinda like a mixture of 737 style manual reversion and some kind of control jam, and no other indications of electrical system failure, so I declared emergency and struggled to land the airplane. After landing, I was able to taxi normally so I stopped it to a normal gate and ended the flight.
However the FSC log told me I was improperly declared emergency and -20 gone.
I checked back in P3D's failure system I do have an electrical system failure, and after clearing that, the main flight control went back to normal.
So yes, somehow CS mismaped the default electrical system failure into a flight control issue, but it's like I can't have a emergency if I have that kind of failure?
|
|
|
|
Post by cxn4026 on Jul 26, 2021 9:19:09 GMT -5
I just had a similar one. I was descending to ZSPD with CS757III and doing prepare, suddenly the AP disconnected, and FSC's FO told me there is an electric system failure, but I found that the main flight control is the issue I facing, It's like a simulated hydraulic failure, it will jump back to zero when I have joystick stopped to some fixed value. So for my feeling, it's kinda like a mixture of 737 style manual reversion and some kind of control jam, and no other indications of electrical system failure, so I declared emergency and struggled to land the airplane. After landing, I was able to taxi normally so I stopped it to a normal gate and ended the flight. However the FSC log told me I was improperly declared emergency and -20 gone. I checked back in P3D's failure system I do have an electrical system failure, and after clearing that, the main flight control went back to normal. So yes, somehow CS mismaped the default electrical system failure into a flight control issue, but it's like I can't have a emergency if I have that kind of failure? Ok, I just checked back that there is a FSC generated flight control issue, which not announced by FO nor show on FCDU, nor in P3D's failure system.
FCDU.EXE:: 21:05:43 Calling PlaySound: FSCaptain\Sound\FO_Trav\PAXBAD5.wav
FCDU.EXE:: 21:05:47 Flight control failure due to thunderstorm turbulence
FCDU.EXE:: 21:05:51 Flight controls fail due to thunderstorm turbulence
FCDU.EXE:: 21:06:08 PlayFO(1) SYSELE type:0 Qnext:0 Qmax:31 VA:7
FCDU.EXE:: 21:06:08 Electrical failure due to thunderstorm activity
FCDU.EXE:: 21:06:08 FOR(138 1) ADIT:54
FCDU.EXE:: 21:06:08 Calling PlaySound: FSCaptain\Sound\FO_Trav\SYSELE1.wav
FCDU.EXE:: 21:06:14 Flight controls fail due to thunderstorm turbulence
FCDU.EXE:: 21:06:20 METAR (7, DST): [ZSPD 011200Z 05007MPS CAVOK 13/05 Q1031 NOSIG]
FCDU.EXE:: 21:06:20 Parsed as: [ZSPD 011200 05013KT 20SM 13/05 A3044]
FCDU.EXE:: 21:06:20 Flight controls fail due to thunderstorm turbulence
FCDU.EXE:: 21:06:45 Flight control failure due to thunderstorm turbulence
FCDU.EXE:: 21:06:49 PlayFO(1) SPDWRN type:0 Qnext:0 Qmax:31 VA:7
FCDU.EXE:: 21:06:49 Spd:298.415253 IAS (352.971791 GS) Alt:9200
FCDU.EXE:: 21:06:49 FOR(129 2) ADIT:36
FCDU.EXE:: 21:06:49 Calling PlaySound: FSCaptain\Sound\FO_Trav\SPDWRN2.wav
FCDU.EXE:: 21:06:51 Flight controls fail due to thunderstorm turbulence
FCDU.EXE:: 21:06:55 PlayFO(1) TRANSD type:0 Qnext:0 Qmax:31 VA:7
FCDU.EXE:: 21:06:55 TA = 9842, OA = 8922 / 9638.
FCDU.EXE:: 21:06:55 FOR(152 2) ADIT:36
FCDU.EXE:: 21:06:55 Calling PlaySound: FSCaptain\Sound\FO_Trav\TRANSD2.wav
FCDU.EXE:: 21:07:01 Flight controls fail due to thunderstorm turbulence
FCDU.EXE:: 21:07:05 ACARS 36: F1 G0
FCDU.EXE:: 21:07:05 WCLABAF(3)
FCDU.EXE:: 21:07:05 WriteLogBin(0) Initiated, logrec recl: 276 for 661.
FCDU.EXE:: 21:07:05 ANA Log Header Written: ferror status 0
FCDU.EXE:: 21:07:05 Log Written with 661 records; ferror status 0
FCDU.EXE:: 21:07:05 ANA Log File Closed(0): ferror status 0
FCDU.EXE:: 21:07:05 WriteLogBin(1) Initiated, logrec recl: 276 for 661.
FCDU.EXE:: 21:07:05 ANA Log Header Written: ferror status 0
FCDU.EXE:: 21:07:05 Log Written with 661 records; ferror status 0
FCDU.EXE:: 21:07:05 ANA Log File Closed(0): ferror status 0
FCDU.EXE:: 21:07:06 PlayFAI(4) PRBLEM type:0 Qnext:0 Qmax:31 VA:0
FCDU.EXE:: 21:07:06 FAR(15 1) ADIT:36
FCDU.EXE:: 21:07:06 Calling PlaySound: FSCaptain\Sound\FA_Heidi\DINGER1.wav
FCDU.EXE:: 21:07:08 METAR (7, DST): [ZSPD 011200Z 05007MPS CAVOK 13/05 Q1031 NOSIG]
FCDU.EXE:: 21:07:08 Parsed as: [ZSPD 011200 05013KT 20SM 13/05 A3044]
FCDU.EXE:: 21:07:09 FAR(29 1) ADIT:288
FCDU.EXE:: 21:07:09 Calling PlaySound: FSCaptain\Sound\FA_Heidi\PRBLEM1.wav
FCDU.EXE:: 21:07:17 Flight control failure due to thunderstorm turbulence
FCDU.EXE:: 21:07:22 METAR (7, DST): [ZSPD 011200Z 05007MPS CAVOK 13/05 Q1031 NOSIG]
FCDU.EXE:: 21:07:22 Parsed as: [ZSPD 011200 05013KT 20SM 13/05 A3044]
FCDU.EXE:: 21:07:22 PlayFAI(4) EMERDS type:0 Qnext:2 Qmax:31 VA:0
FCDU.EXE:: 21:07:26 Flight control failure due to thunderstorm turbulence
So I declared an Emergency, and :
FCDU.EXE:: 21:41:49 Comments: ACI=0. Emergency declared! Successful Emergency Landing!
FCDU.EXE:: 21:41:49 SFOCT(0)
FCDU.EXE:: 21:41:50 PlayFAI(4) EMERGR type:0 Qnext:0 Qmax:31 VA:0
FCDU.EXE:: 21:41:50 FAR(15 1) ADIT:36
FCDU.EXE:: 21:41:50 Calling PlaySound: FSCaptain\Sound\FA_Heidi\DINGER1.wav
FCDU.EXE:: 21:41:53 FAR(18 1) ADIT:108
FCDU.EXE:: 21:41:53 Calling PlaySound: FSCaptain\Sound\FA_Heidi\EMERGR1.wav
FCDU.EXE:: 21:43:03 ACARS 29: F1
FCDU.EXE:: 21:43:03 EL-SL
FCDU.EXE:: 21:43:03 Stage: 0 L()
FCDU.EXE:: 21:43:03 Stage: A=0
FCDU.EXE:: 21:43:03 Stage: 0 A=0
FCDU.EXE:: 21:43:03 No airport within 50 miles. Loading airport DB.
FCDU.EXE:: 21:43:03 Reading Airport Exception data.
But still, in the Flight log it shows it's a CP, rather than CE/CM.... does that mean it's my fault to fly into a typhoon? (BTW as I know, the typhoon In-Fa is weaken enough to allow real world operation resumed as this afternoon)
|
|
|
|
Post by Travis on Jul 26, 2021 11:40:21 GMT -5
Cxn,
Email me the entire FCDU log and I'll look at things from start to finish.
Best,
|
|
|
|
Post by Travis on Jul 26, 2021 12:21:28 GMT -5
Also, please include your airline's logfile - it should be "ANA.log" - so I can see what's been recorded. I'll start by reading up on the differences on things such as these two lines.... The difference in the wording tells me that two separate things occurred.  I'll likely not do anything in code now, so RC1 can still release this week. But I'll look to make any needed changes quickly afterwards. Best, |
|
|
|
Post by Travis on Jul 26, 2021 17:00:52 GMT -5
I've seen that "control failure" means the elevators locked, while "controls fail" means the ailerons locked....
I believe I know what code changes to make to fix all of your issues. I would like to first see your full FCDU log and ANA.log file, so please email them to me as soon as you can.
Best,
|
|
|
|
Post by Travis on Jul 30, 2021 18:48:20 GMT -5
Captains,
CXN has worked with a test build, and all of the reported issues look good.
However CXN has noted an issue that Peter has recently called out - it's one that's different from Beta 1, which makes it a show-stopper.
So RC1 will release sometime next month - August.
Regards,
|
|
