Recently we have seen a lot of codes used to unlock our products being offered for discounted prices. Almost all of them are bought using stolen credit cards. These codes will all be blocked by our systems and you will have to try to get your money back from the seller, we are unable to assist in these matters. Do be very careful when you see a deal that is almost too good to be true, it probably is too good to be true.

Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

53 Excellent

About Sabretooth78

  • Rank
    Flight Student - Crosscountry

Recent Profile Visitors

2298 profile views
  1. 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.
  2. 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:
  3. 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.
  4. 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:
  5. 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.
  6. OK, I officially don't know what's happening - I turned off the GSX integration and rolled back the modifications to vanilla, 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 update, because I don't remember this happening prior?
  7. 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.
  8. Odd issue with the GSX2 integration that I have noticed on a couple of flights. Before takeoff, MCDU3 showed that the aircraft (A321 IAE) was loaded with the correct 176 PAX, although the GW in the lower ECAM was a little lower than it should have been. After taking off, I decided to look at MCDU3 and sure enough, it was now reporting just 174 PAX loaded (cargo was OK). I've noticed this happening in other flights where the last PAX or 2 claims to be loaded but does not show up in the GW calculation, though this is the first time I've actually checked the tally mid-flight. I guess I'll just chalk it up to 2 no-shows! In the past I've typically just used "Load Instant" which has worked without fail.
  9. Yes, green and yellow flashing. Version; Navigraph current AIRAC (1907 I believe). I don't recall the RNP exactly (I did look at it) but I think it was either 0.03 or 0.30. I'll be running another flight today so I'll see if this crops up again.
  10. At some point during each of two flights last night, the green/yellow flashing despite the aircraft apparently following the LNAV course and with an acceptable RNP. First flight: KLGB/12 F330 ZOOMM2 MISEN CLARR3 KLAS/19L <- first noticed sometime after MISEN Second flight: KLAS/26R F300 BOACH8 WHIGG DCT FEYLA DSNEE4 KLGB/12 <- first noticed before BOACH, did not persist through the entire flight. Oddly, both instances seemed to occur in roughly the same geographic area. I'd had that indication pop up in the past, but very infrequently and it would usually seem to go away faster.
  11. I noticed a similar issue last night, but on a turn-around. Everything loaded normally (incorrectly for the cruise as it always does for me, but it did at least populate something) for the initial flight but on the return leg the winds would not populate even after manually updating the plan in ActiveSky, etc.
  12. I think I've posted this before, but I can't seem to find where (and whether it was acknowledged). When in managed climb, the MCDU PERF CLB page gives some quite nonsensical results data for the managed climb predictions: "Expedite" seems to more or less make sense but the "Managed" makes absolutely no sense at all: 3 hours to climb 5500 feet at 800 fpm? The target distance number was fluctuating wildly as well, anything between 500-800 miles only to final settle down once getting closer to the target altitude. A321 IAE,
  13. Just to document another instance (as I said it happens consistently). This time with the A321 IAE; Attached is the activeflightplanwx file and my AS settings if that helps. Everything posted was captured while paused, during preflight so it should all be consistent with the wx picture at that moment. Flight plan: KJFK DCT COATE Q436 RAAKK Q440 SLLAP DCT GRB DCT KINGZ DCT FAR DCT DIK DCT MLP GLASR1 KSEA Note GRB: Note based on the activeflightplanwx file, the entry 160@7(12) leading off the GRB line. If you include that as 6k altitude (when it should in fact be surface?), then it might seem as though the Bus is reading an incorrectly delimited file, or the Bus doesn't skip an entry it should be skipping. It's over my head regardless, so curious to see what you hear back from Hifi. activeflightplanwx.txtCMS_PTA_EF.CFG
  14. I'll check for that file next flight, which will be tomorrow evening - I was previously looking at the activeflightplanwx.txt as mentioned above. Are you sure the "EDDNEDDH.wx" file would be in the PMDG folder? That seems a little odd for instance if you didn't have any PMDG installed.
  • Create New...