Jump to content

Sabretooth78

members
  • Content Count

    243
  • Joined

  • Last visited

Community Reputation

53 Excellent

About Sabretooth78

  • Rank
    Flight Student - Crosscountry

Recent Profile Visitors

2993 profile views
  1. No, this was shortly after reaching TOC on a 1.5 hour flight.
  2. I had this issue occur last night for the first time in a long time. Shortly after reaching cruise, I noticed the throttles rolling back and the PFD speed target was indicating "107". I then tried going back into managed speed at various times during the flight and the problem persisted, right through descent where it was still calling for an unreasonably low "213". At all times, the MCDU PERF was showing the correct speeds (for CI 35). Flight plan: KMCO/36R F370 MCOY2 GUANO DCT FEMON MCOY2 GUANO Q87 JROSS DCT FLO Q87 JROSS J207 RDU DCT NEAVL J207 RDU DUCXS4 KRIC/34 I'm not at my sim PC so I don't have the log files but I do believe I have logging turned on so I can post them later. This is running the latest version with experimental updates enabled. An interesting note is that I did a full reinstall of the PC about a month ago, so everything should be relatively "clean".
  3. I know. My question relates to the fact that when it is set to negative (whether correctly or incorrectly), the 00s and 20s disappear. This doesn't occur for positive 00s and 20s.
  4. Just a little "problem" I discovered while setting the altimeter before my last flight - A321IAE on the latest version 1.2.5.0. When at negative altitudes, the minor "00" and "20" seem to disappear when you cycle past them. I'm not sure this is much of a practical concern as I'm sure there are very few usable airfields at these elevations, but I'm noting it nonetheless. Note the altitude readout as the QNH knob is turned: (Edit: I'm not sure why the pictures saved different sizes...)
  5. I actually just noticed something like this last night as well. I had set a DIR to waypoint WIKIR on approach to KFLL/28L and activated LOC while still 4-5 miles from interception (from roughly DEKAL, so about 20-30 degree intercept and roughly on g/s) and the a/c immediately started banking to the left. I quickly turned LOC off and pulled the knob for heading select, then reactivated managed NAV. Then a little closer to intercept, I reactivated LOC, the a/c quickly and slightly banked left but restabilized on the NAV course until getting closer where it did intercept the LOC normally.
  6. I did actually just do a video driver reinstall, and with DDU to chase another issue, so I'll pay more attention next time! If it ultimately requires a reinstall of the Airbus I'll just wait until there's a bigger update requiring a reinstall... It typically only goes 5-digits during the takeoff - certainly not in any other phase.
  7. On my current flight, I just experienced something very similar to this, but on the A320 IAE (not the A321). Again, the GW, fuel burn, and P3D "Fuel and Payload" dialog all seem to be showing the correct numbers; it's just the ECAM and MCDU3 that seem to think the a/c is "refueling itself". This is the first time I've seen this on the A320 IAE, which I use fairly often. There is one thing I did slightly differently during this flight which may or may not be the cause? Typically I fuel up the a/c by selecting "Load Instant" or "Load Fuel" (depending on how I feel like doing it on a particular flight) on the MCDU3 Load and Fuel display. This time, I initiated fueling through the GSX menu and never touched any of the load buttons on MCDU3 (i.e. LSK 1R-4R). Also interesting, after I noticed this happening (about a half hour into the flight), I disabled the GSX integration in the MCDU3 "Gnd Services" page and shortly thereafter the FOB numbers seemed to begin decaying as expected. We all seem to be aware there are still some nagging issues with the GSX integration, perhaps this is one of those? An example; note the time and the discrepancy between fuel burn and FOB:
  8. I've run 2 flights so far with that file (though different routes) and haven't seen the problem recur. I'll update if and when it happens again.
  9. Just a minor problem here: during takeoff and initial climb (i.e. times of high fuel flows) the ECAM displays don't properly show values with 5 digits. I see this with both IAE and CFM models: IAE: CFM:
  10. I still see this "magenta" rollback during climb at or near crossover altitude/speed on almost (if not) every flight (commanding something like 166 kts) but the a/c still follows the correct speed (usually 280-300 kts) and the problem goes away either at TOC or by just playing with the altitude knob (push or pull). Haven't seen it occur at cruise in some time.
  11. Upon further review what I'm seeing here doesn't seem to be a result of my modifications but rather the same issue as this:
  12. Somehow I didn't catch this topic - although I think I've encountered it as well. My initial thought was that it was something I had done, namely modifying the aircraft.cfg and MCDU2c.xml to increase the capacity of the center fuel tank.
  13. OK, I officially don't know what's happening - I turned off the GSX integration and rolled back the modifications to vanilla 1.2.4.2, loaded a fuel amount well less than the default capacity (say 40.00 klbs), and still seeing the increasing FOB once the transfers from the center tank begin shortly after takeoff. Situation: Load state ready for takeoff at KSFO, Rwy 28L at 1850z+/- 10Jul2019, TRUKN2 departure, ORRCA transition. I get this behavior before hitting ORRCA every time with the A321 IAE - although technically speaking I can also just sit there with nothing programmed and parking brakes on while running up the engines to TOGA and it'll still happen once the wing tanks get low enough, about 13250 lbs. If I use a smaller total fuel quantity (say 35.00 klbs), the FOB doesn't increase but its rate of decrease seems to lag behind the increase in the F.USED. Only seems to be happening to the A321 IAE. Did something break with the 1.2.4.2 update, because I don't remember this happening prior?
  14. More of a notice to others regarding the increased fuel capacity "fix" myself and others have promoted (link below) as I realize it's unsupported. I'm currently running a flight which I believe to be the first I've run where I've filled the aircraft up into the "additional" capacity range (i.e. above 19150 kg total or 2180 gal/14600 lb in the center tank). KSFO-KBOS, with a block of 45900 lb or 20820 kg (GSX actually loaded it to 45940 lb). I noticed during climb out that my fuel wasn't declining as quickly as it should be, whereas my total F.USED was showing the expected amount. Turns out that something is causing the total FOB to increase during periods where the ECAM showed that transfers were occurring. Note that despite this, the following all show correct numbers: The P3D "fuel and payload" dialog F.USED on the CRUISE, ENGINE (though incorrectly in KGS) and FUEL ECAM displays GW in the lower right of the lower ECAM FOB on the MCDU FUEL PRED page Current burn on the flight is also within a few % of where SimBrief says it should be (I track weighted average fuel usage so my perf factors are generally quite good; I use 1.03 for the A321IAE.) Not shown, the fuel panel mode selector is also displaying a fault. I don't believe I've noticed this before. Playing around with that and the center fuel pumps manually doesn't really seem to be causing much of a different behavior, even after getting the center tank to display below 14600 lb and back into the "supported" realm (without going manual it doesn't seem to dip below that value); the value shown in the FUEL ECAM does continue to decline (along with the wing tanks) despite the pumps being turned off. As time goes by without transfers, the gross sum of the reported tank volumes and engine burn does seem to slowly be decaying (currently it's still at a total above the original loading, and for that matter, actual capacity, but I'm not sure the flight will be long enough to catch up if it indeed actually will). I guess the first question is has anybody else who has applied this "fix" encountered this same issue? I've yet to see feedback saying so, but perhaps they, as I did, applied it without ever actually utilizing it. I looked through some of the XML files to see if there was something that stood out but didn't find any smoking guns. Does it make sense that this could happen, and if so, would it be possible to re-code a file somewhere to allow capacities above the standard 2180 gal to just come out of the center tank as those from 1 to 2180, "realism" be damned? (Even if not officially released or sanctioned but rather as a your mileage may vary; I'm not going to open a support request if I knowingly break something! I also keep backups!) I'll try it again sometime without "GSX Services" enabled just to confirm (I used that to load fuel and I have been having some weird results with that regarding PAX loading as well, and just want to rule it out). It happened fairly quickly into the climb out so it shouldn't be a lengthy trial to attempt to replicate it. In the meantime I'm continuing with my flight and just calling it a faulty center tank sensor and if I have a double flame-out over Chicago or have to land a little hot in Boston because the plane thinks its heavier than it is, so be it lol.
×
×
  • Create New...