|
|
Post by redbaron55 on Jul 25, 2014 16:24:50 GMT -5
I first purchased the 1.009 of the Q400 several weeks back and have consistently experienced the dreaded "flameout" announcement immediately after takeoff, along with the FO negative feedback which I believe has been a chronic issue for many. I just read about a new beta guage xml file v0.31 that addressed the 1.009 version and installed it -- along with the newest 1.010 fix. I'm still getting the flameout issue (I quit before I further upset the FO  so don't know for sure if the negative feedback issue also exists). My question is whether the v0.31 gauge should handle the 1.010 fix or not -- and if not, if this will be taken care of in the upcoming fscaptain release. [Vcockpit01] //file=$vc2q400.bmp Background_color=0,0,0 size_mm=1024,1024 visible=1 pixel_size=1024, 1024 texture=$vc2q400 gauge00=mjc84_main!VC_sheet2_gauges, 0,0,1024,1024 gauge01=FCDU!FDR,1,1,1,1
gauge02=FCOMPNL!InterfaceMJQ400,1,1,1,1
Thanks very much for any help! |
|
|
|
Post by Travis on Jul 26, 2014 9:08:21 GMT -5
Even with 1.009 I would get a false flameout report usually after takeoff, but that annoying FO was shut up (especially after disabling the FDE to FSX option).
I have 1.010 just installed and I will give it a looksee later in my morning.
|
|
|
|
Post by Travis on Jul 26, 2014 12:10:36 GMT -5
I'm still seeing the false flameout just after takeoff, but I made a short flight just now with 1.010 and (with the FDE-FSX disabled) everything else was smooth like butter. Maybe I should register that phrase as a servicemark or something.  I don't know if it was the area that I flew in (LIMJ - LFMN) but my VAS numbers were well improved over the short jumps I flew last weekend. There were loads of CU and even TCU in the area, so lots of clouds. |
|
|
|
Post by redbaron55 on Jul 27, 2014 10:07:34 GMT -5
Thanks very much Travis for taking the time to install and test the 1.010 fix. I've been busy this weekend and haven't had time yet myself to fully test how the rest of the flight goes after the flameout, but that's good to know that it should be a happier flight. I assume I can just ignore the flameout announcement, and continue the flight as I normally would then..
Thanks again and to Dutch and the support team!
Mark
|
|
|
|
Post by Dutch Owen on Jul 27, 2014 11:24:50 GMT -5
We're working on trying to figure out what was changed to make the flameout issue re-appear.
Dutch
|
|
|
|
Post by Travis on Jul 27, 2014 18:46:57 GMT -5
That's okay Mark... for now you'll get an extra 5 points for landing with a "missing" right engine. |
|
|
|
Post by Travis on Aug 4, 2014 10:54:06 GMT -5
I believe the source of the phantom phlameouts has been found. Me.  My maths teachers would be embarassed. Expect version 0.32 of the xml interface to be posted before the end of the day. |
|
|
|
Post by Travis on Aug 4, 2014 14:15:55 GMT -5
The new interface has been posted in this forum thread. I encourage all Q400 Captains to upgrade to this interface. |
|
|
|
Post by nightmoon42 on Aug 11, 2014 12:31:47 GMT -5
I tried again the Q400 with the latest interface but it still don't work.
I get a lot of complains from my co-pilot and a bad score every flight:
Completen w/mech fault 720 (+5)
Damage Assessment (-30)
PAXCOM: Rogh Flying (-10)
|
|
|
|
Post by Travis on Aug 11, 2014 13:07:33 GMT -5
Which ACARS did you use - the gauge or the stand-alone .exe?
The xml interface only works with the gauge ACARS....
|
|
|
|
Post by nightmoon42 on Aug 11, 2014 13:48:32 GMT -5
The gauge ACARS
|
|
|
|
Post by Travis on Aug 11, 2014 17:50:35 GMT -5
Well that shouldn't happen unless you just had a bad flight... or... did you set the Majestic Control Panel's SYSTEM / FDE TO FSX SYNC to "DISABLE"? If you leave it set to ENABLE, the sim will be told that you're bouncing around the sky and that thing are likely to break, and the PAX will be unhappy. Even though things are peachy keen in your seat. EMail me the FCDU log from that flight along with your Q400's panel.cfg file and I'll take a look. |
|
|
|
Post by nightmoon42 on Aug 12, 2014 10:22:14 GMT -5
Well that shouldn't happen unless you just had a bad flight... or... did you set the Majestic Control Panel's SYSTEM / FDE TO FSX SYNC to "DISABLE"? If you leave it set to ENABLE, the sim will be told that you're bouncing around the sky and that thing are likely to break, and the PAX will be unhappy. Even though things are peachy keen in your seat. It seems I forgot to press "Apply". I'll try again. |
|
|
|
Post by Travis on Aug 12, 2014 15:01:40 GMT -5
No problems Nightmoon! |
|
|
|
Post by nightmoon42 on Aug 14, 2014 11:59:37 GMT -5
Ok, much better now my score increased from 62 to 107. But I got a flamout warning after takeoff and a score entry: Completed w/mech fault 702 (+5) I'm using V1.010 with Interface version 0.32. |
|
so don't know for sure if the negative feedback issue also exists). 
