Leaderboard

thank you sir, very helpful........

On aviation exist 2 terms: TA: transition altitude, this is the altitude when climbing you switch from QNH altimeter to QNE altitimeter 29.92 and you start flying FL (Flight Levels FLXXX) You set the TA on the PERF INIT page on the bottom right corner, in USA the TA is 18000ft, other countries/regions is variable given their airspace rules. The charts specify this. TL: transition level, this is the FLXXX at which you switch back to altitudes when descending. Altimeter moving from QNE back to QNH You set on the DES page. I do recommend the tutorials. See at the bottom. Press the LSK X (left soft key) of the first waypoint below the disco (this will copy the waypoint name to the scratchpad automatically), then press the LSK of the disco and this will shift the entire flight plan one step up and clear the disco. To delete a waypoint press DEL key (DELETE will be shown on the scratchpad) then press the key of the waypoint you want to delete, that position on the fmc will be cleared. Re-type the waypoint name on the scratchpad and press the soft ley you cleared to insert. note: if you missed to insert a waypoint, suppose you entered A then C then D and you missed to enter B inbetween A & C. Simply type B on the sratchpad, then pess the softkey of C. This will shift C and remaining flight plan D, etc. one step down and insert B inbetween A & C. Tons of profesional tutorials for the different phases of flight you will be required to understand and know how it is done on the real thing. Hope this helps.

Just back from my holiday this weekend and FIRST thing I did...Install SMP update. Again, I applaud you guys (and gals) efforts for a real amazing product. The clouds look better than ever and my frames, well, a bit better throughout but having some post card effects here and there, but I think it may be some of the ortho scenery I have installed. I'll experiment here and there, but still, in the end, this is a great product...and thanks to you all for hanging in there to address issues and do some fantastic upgrades/updates/additions. SMP really adds a dimension that puts you in the pilots seat! (hows that for a sales pitch lol, but I do really mean this..bigtime!)

First I just wanna say that if you are hit by this storm or knowing someone who are, stay safe. I did this flight 9 September 2017, from MUCM Camaguey to KNQX Key West Naval Air Station. The weather was pretty badass for the takeoff. Wind was 18027G38KT (Runway 25). So pretty much direct crosswind. The crosswind limitations for the 733 is 35knots. And that is for a trained and skilled pilots. So not me I did mess up a bit on takeoff. First I got windshear. The belive the procedure for that is not to change any configuration (I did gear up). Second I did mess with the heading right after takeoff. I didn't account for the heavy drift due to the crosswind. So I though it was a bug then I engaged LNAV and A/P and the aircraft banked the to left, but the bug was me When reaching FL240 I hit a cell with heavy icing. I dont know how realistic x-plane is simulating this, but I was rapidly losing airspeed. Engaging wing and engine anti-ice was solving this issue. On the approach to KNQX I decided to divert to KMIA Miami since I was unable to identify my runway for landing. It was a rough but interesting flight. Wind charts for the flight. You can clearly see the center of the storm.

Got this one fixed....this is a nav-data problem. I'll post an explanation later with diagrams as I find it a bit interesting to demonstrate some of the challenges here. The solution, is to edit the XML data file, particularly the transition in question. You will note in the latest data set (Navigraph 1706?), there are 5 waypoints in the transition, the last waypoint being "LB484". You need to delete from the XML file the waypoint BEFORE this waypoint, and change the Waypoint ID of LB484 to '4'. This will allow the procedure to load. More to follow. -tkyler

Thanks for testing TomS. This looks to be an "ambiguous intersection" calculation....which I'll have to talk to Jan about how to handle gracefully. We labor under the assumption that the waypoint nav data sequence is "sane" and in some cases it is not....and in some instances, we cannot calculate an intersection (due to diverging paths). This is "hit and miss". LSZH, for example, has this problem with newer data where it did not with older data. Its like being in Texas and saying, "head due south till you get to New York City" The numbers just won't add up...but we'll come up with some message. -tkyler

It takes you little effort to install and find out. No one can tell you how your system will perform.