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

Mark Crabtree

members
  • Content Count

    27
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Mark Crabtree

  • Rank
    Flight Student - Groundwork

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I fat fingered the version I am using...sorry...but the problem is still the problem... I have been noticing some stange fuel behavior with the latest experimental release across all aircraft. I use the Axxx fuel weight and fuel planner and generate a load sheet. when programming the MCDU I initialize the fuel page by pressing the bottons next to the ZFW and Fuel enries and setting them to the values broght in from the fuel sheet. Currently flying KSFO to PANC. load sheet put 31000 lbs of fuel on board and that is what was entered into the MCDU I am 120 nm from tod and my onboard fuel says 27880 and fuel used says 26000 lbs while the EFOB at PANC on the fuel prediction page shows 10.5 on landing.... any ideas?
  2. I am sorry, I fat fingered the version number. I am experiencing this on version 1.2.4.2 the latest experimental.....
  3. I have been noticing some stange fuel behavior with the latest experimental release across all aircraft. I use the Axxx fuel weight and fuel planner and generate a load sheet. when programming the MCDU I initialize the fuel page by pressing the bottons next to the ZFW and Fuel enries and setting them to the values broght in from the fuel sheet. Currently flying KSFO to PANC. load sheet put 31000 lbs of fuel on board and that is what was entered into the MCDU I am 120 nm from tod and my onboard fuel says 27880 and fuel used says 26000 lbs while the EFOB at PANC on the fuel prediction page shows 10.5 on landing.... any ideas?
  4. Update...after uninstalling and reinstalling and reupdating...it appears to work.
  5. The following has occurred on all 3 tests flights so far. I use GSX and have Use GSX configured in the Gnd Services section. Upon pushback, I start Engine 2 and as before when I here the Engine 2 Stable announcment, I start Engine 1. The Engine 1 Stable announcment never happens and the info bar continues to show Follow GSX Instructions. I let the aircraft sit running for 1 hour and stayed stuck at that position in the flow. Does anyone else see this?
  6. I have not flow again. But, I am as certain as I can be. I also use the Pilot and CoPilot checklist, they always set things correct before. I will try it again.
  7. Flying over the Carribean from TKPK to KMIA and I ran over and into 5 weather systems, including on approach. I had rain on the windshield, but nothing every showed up on the weather radar. This is the first time I have ever had this issue as it mornally works without issue. Anyone else experience this after update? I have always used Active Skpy P3D v4 for the weather.
  8. 1.2.4.1 Has shown no managed speed issues using 319, 320 and 321. It does seem to be more "agressive" tracking during managed descent on an arrival, trying to play "catch" with the ball, snowflake, whatever the correct Airbus term is for the vertical profile indicator (litle green dot next to altitude tape).
  9. Route was KMCI-KSTL (doesn't matter as so far on 10+ flights the same issue manifests) A319 (also, doesn't matter same issue on all four aircraft) Simbrief Flight Plan (same issue when entering everything by hand) AIRAC cycle 1904, the same one I was using before the update LAKES3 COU KAYLA KAYLA3 This was the full route (happens Offending waypoints FLUDD and TRYSH. After entering the DEP and ARR info, I was presented with a DISCO after FLUDD----MANUAL. Before the 1.2.4 update I could clear the DISCO by selectink the LEFT lsk next to FLUDD and entrying TRYSH into the NEXT waypoint field. The flight plan would stay whole and simply remove MANUAL and the DISCO. Now however the FP is deleted. See pics
  10. A321 KSTL to KBOS FL350 CI80 Active Sky Wx Version 1.2.4.0 On this flights I took copious notes to try to see what/where the managed speed issue triggered. I was rewarded with a PERFECT flight, no issues at all. LOL. I will not take notes on all my Airbus flights. LOL
  11. What flaps setting? Weight? Are you using Manflex or TOGA, those get confused. I have never seen TOGA set anything other than full power. Manflex by definition is a lower powered flex takeoff setting that the computer calculates, if as in real life, for factors like rwy length, weight, OAT, flaps etc....
  12. After the update, A321 seemed to engage Approach Mode by itself. In fact, MCDU did not even show me the option of Approach mode under Performance. A319 did not show this beahvior. I am flying another A321 flight now KSTL to KBOS and will report back if same issue appears.
  13. If that issue was solved, please post the solution. I am seeing the same routing issue with 1.2.4.0, took pictures too, but the show the same thing as above.
  14. I flew from KCLT to KPHL with a Simbrief generated plan this time. AS weather. A320 CFM. Once again I got the managed speed issue during descent. This is three flights in a row with two aircraft from the series. I am actually excited about this because the issue seems to be confined to a particular phase of flight with 1.2.3.6. It has been called Alpha Floor mode in other posts, but today got me thinking. I was on descent and the behavior was as if the Approach Mode was somehow initiated. In fact, I left the speed alone, everything in managed mode and manually activated the Approach Mode and there was no change in behavior, again leading me to believe that something is automatically activating approach mode internally. Has this been explored?
  15. I thought the same thing at first, however I started paying attention to it and confirmed that the altimeter looks like it was set to standard but in it not until I use the mouse myself.
×
×
  • Create New...