Leaderboard

I suppose I should demonstrate some form of life. I'll have to get with Jan on that as our radar (best I recall) had most of the features of the real thing. As far as "coming out soon", here's what I'll say....and this is overdue for sure....and I'm not going to convince anyone to believe me or not on the timing. It will get looked at and updated at some point. As sure as this is my 20th year actively involved in X-Plane work, it will continue to be so. A year and a half ago, things changed for me when Laminar announced its new store initiative in Montreal. I took a job with Laminar to completely rewrite its developer documentation. This was a "look to the future" for both myself and X-Plane, at the cost of 'now'. Laminar are looking to embrace a future generation of developers and we need to have better learning materials to engage this generation to develop for X-Plane, so I'm that guy....thats for Laminar. For myself, I needed more stability and a cushion, as the add-on market for X-Plane is still too thin to have any kind of long term security. Taking on this work with Laminar has allowed me to close out all other obligations and stay in the X-Plane ecosystem for the foreseeable future. The 'problem' for my customers and X-Aviation thus far, is that the initial phase or work to revamp and deploy the documentation was/is huge. New developer web site, new manual formats, a new, interactive PlaneMaker manual, lots and lots of rewriting, new illustrations...etc....and that has taken a good while to develop and received all my focus to get to what we call the "initial deployment" of the docs out the door. That initial deploy is not terribly far off. After the initial deployment, I will settle into a more regular time schedule that will afford me the time to get back to my own work. It has been my effort over the last year to try and achieve a point where I can only work on X-Plane endeavors between now and my retirment......and there have been personal hurdles along the way that are neither anyone's concern or business, but real to me just the same. It is my intention to crack open the MU2 and 737 again in early October, to resume work on my 'X-Aviation' things. I have discussed this with X-Aviation also. Between now and then I am focused on getting an initial deployment of the new docs out the door for Laminar. We will look at the IXEG radar early on for sure. I want to remain developing for X-Plane fully and it is my firm belief that this path i've taken was the required path to do so, and I apologize for the silence and delays. -tkyler

zzz....oh man...just woke up after a 18 month hibernation! Seriously....Nothing is forgotten, only life has happened. Here's a quick summary: Spent last 18-24 months in a significant life transition as I approach and prepare for retirement. Lots of loose ends to tie up and leave in the past. I now work full time for Laminar, a big change...and I have been positioning myself to stay in X-Plane work exclusively for the future. I'm wrapping up a 2-year private contract for the BETA ALIA production aircraft (which will be in X-Plane). I'll complete that work next month. Gizmo based code in all my products is nearing end of life and had complicated the update process due to the volume of code to rewrite......however AI has enabled a path to relearn concepts & rewrite the code as its become "X-Plane SDK aware" in the last year...This reduces the effort drastically and is a major catalyst. No fees for future updates on the MU2 or IXEG when they eventually go out. Updates will always be free for existing customers. They've earned that. After ALIA delivery, I'll return to push an update to the MU2 with the Gizmo code-base....I won't get OCD....I'll just push what I have, which is a good amount. After MU2 update, I begin code rewrites to serve as my future code platform for the MU2, IXEG and the forth-coming 717. This is foundational and absolutely required to guarantee long term compatibility for these products. Those aircraft will be the only three products I will maintain into retirement and beyond. That's the highlights. This gap in work has been all about my focus and preparation to sustain myself after retirement, and stay within the X-Plane ecosphere in the process.

Hello All, This will serve as an official announcement that we have released update version 1.9 for the CL650. All customers who have purchased the CL650 up till now have been sent an e-mail by X-Aviation with complete instructions on how to obtain your update. We have made this a very simple process! For those that purchase the CL650 from today forward, your purchased download will already be updated to version 1.9 for you. What if I didn't get the update e-mail? If you did not receive your update e-mail don't fret! X-Aviation has updated our system to allow all customers to update with ease, regardless of whether you received an e-mail for the update! Here's what to do: 1. Login to your X-Aviation account here: https://www.x-aviation.com/catalog/account_history.php  2. Find your original Challenger 650 download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: Release Highlights: Fixed various manipulators being reversed on the overhead Particle effect luminosity is incorrectly set in XP12 making them appear extremely bright Rewrote large portions of shared cockpit to allow for multi-crew, passengers, spectators and a much simpler setup process (documentation forthcoming) Engaging the yaw dampers requires holding the buttons down for a couple of seconds As we no longer utilize Gizmo, Mac ARM support is now complete and Mac users should stop running X-Plane through Rosetta if you don't have any other products which require Gizmo (the installer will point them out if you do). Improvements: 4536: Add support for rudder and steering control using only keyboard & mouse 4565: Add support for SayIntentions and custom ACARS service provider URLs 4569: Retune AP flap constants to avoid excessive altitude excursions 4573: Refactor pitch FMA mode to hold the commanded attitude more tightly 4577: Implement persistent logging of CB pop reason 4589: Add waypoint description codes introduced in ARINC 424-20 4590: Switch to reduced bank angle for hold path at FL316 not FL245 4593: Update world magnetic coefficients to 2025 4606: Implement gRPC API 4629: Workaround for weak X-Plane's aileron effectiveness at low airspeeds 4643: Switch to using nvcompress for DDS generation (better texture colors) 4649: Implement compressed normal maps for XP12 4600: Add support for new combined wheelbrake axis 4468: Stab/mach trim and yaw damper buttons must be held down to engage 4698: Expand shared cockpit to allow for multiple concurrent connections and easier setup Bugfixes: 4535: Typo in pressurization study screen tooltip 4538: Crash on XP11 when aviationweather.gov returns zero METARs for an airport 4537: Mouse yoke breaks on 3rd party airplanes if the CL650 was loaded previously 4539: Module boot time variation is producing doubled audio on startup from DCU and PSEU 4534: FAA obstacle database not decompressing correctly due to ZIP version change 4541: Remove IRU debug logging on release builds 4542: Typo in AFCS visualizer reads "Nm/s" when it should say "Nm" 4543: Deleting last leg of an airway in LEGS when preceding and following legs are discontinuities can crash 4545: AC AUTOXFER FAIL indications on MFD synoptic page should be driven directly by CAS trigger 4546: Recompute a vertical direct-to on mod exec 4547: On executing vertical direct-to, disable the NO VPATH-PILOT CMD suppression 4372: Sporadic and spurious NOT IN DATABASE messages 4551: Bad memory allocation in DCU wire-to-lamp definition parsing code 4556: CTD due to phys.c assertion in atmos_main for shared cockpit guest in X-Plane 11 4558: Harden netcode against ingesting values too large to represent as an FP16 4552: Various manipulators are reversed in latest stable release 4563: VTBS has overflowed the maximum number of SIDs (200) causing a crash when attempting to pick a SID in DEP/ARR DEPARTURE 4571: CTD due to assertion "abus_isval(tod_pause.time2tod)" failed 4574: NWS actuator shoudn't be feeding off the inboard brake hydraulic line 4582: Regression: fix for 0004495 broke AIRWAY INTERSECTION page's ability to automatically resolve the intersection 4583: earth_nav.dat parser needs to normalize whitespace before line splitting 4584: Fix heat damage on engine isn't fixing damage from engine fires 4585: DataRefTool crashes trying to immediately read our datarefs before their setup is completed 4592: FDR data incorrectly labels stick shaker signal as pilot-commanded AP disconnection signal 4595: MFD display reversion is erroneously triggering MFD XTLK flag 4607: Aircraft contrail particle effects are broken in XP12 4608: KLAX ORCKA5 produces spurious UNABLE FPLN ALT due to short leg sequence across discontinuity 4610: FCU clogged failure can cause crash due to incorrect meter_valve_rat clamping 4624: IF legs need to be stripped out when following an enroute transition that bypasses them 4493: Linux with AMD GPU without Zink is borked on latest beta build Object Fixes: Main Panels1.obj Dsus fastener positions fixed on right side panel. Object Fixes: Nose Gear Bay.obj Mesh added to fill in gaps around edges of opening. 4625: NOT ON INTERCEPT TRACK is coded completely wrong 4626: Increase XTALK FAIL message time delay to 10 seconds 4627: SBAS VPL should be ignored when flying an approach in RNP mode 4602: Anti-ice fluid on wings not visible from inside 4628: Refactor nose door implementation to properly route through relay K4GA 4631: Tie amber generator circles on the AC synoptic page to corresponding GEN OFF CAS messages 4632: Use tighter holding pattern radii at all altitudes 4636: PPOS flight plan disappears from PFDs 4 seconds after selecting PFD reversion 4638: phys subsystem still references rucsoundings 4639: Incorrect LPV vertical path construction 4640: Harden LTP and FPAP access functions to bad data 2452: FIX page symbology not showing on MFD when SEC FPLN showing on MFD 4650: NAV LTS breaker has the wrong rating 4651: Stop hard-depending on stock X-Plane commands existing 3938: Updating DIRECT-TO NEAREST AIRPORTS's MIN RWY does not require UPDATE AIRPORTS to be selected 4118: Existing waypoints should be dropped when changing flight plan via Direct-To NEAREST AIRPORTS 4369: XP11 version of ACF is missing instrument label and CB collar OBJs 4385: Updated hint images with all corrections to Jan 2024 4548: Change hint image loader to accept RGB formatted images 4503: Update "more info" links to use CL650/Study prefix 4434: Engaging AP while FLC is active should sync speed target to current speed 3141: Pressing Left LSK for RX fix (visual approach) should put pre-constructed PBD into scratchpad 4654: Pilot-defined waypoints do not properly initialize pbd.src field 4656: Stabilizer trim runaway failure cannot be interrupted by disengaging stabilizer trim 4657: Remove "CVR" failure from 24-Elec 4660: Failures.txt documentation mistakes 4570: Regression? When IF is not aligned with FAC, APPR LNV wrongly flies FAC 4661: Don't show CHECK LOC TUNING when on missed approach 4668: Attempting TTS on Arch Linux with no festival(1) binary present crashes X-Plane with SIGSEGV 4673: Along-track waypoint doesn't use the correct inbound course on direct-to leg 4674: Compute VDEV even when track angle error exceeds capture limit 4675: Retuned ISI attitude finding to produce less pitch error while in hold 4670: Avionics should default to inches of mercury rather than hPa 4684: Implement missing failures 4695: Retune XP12 cabin lighting 4696: Harden the AIRAC parser against invalid altitude constraints causing a crash 4710: Crash on XP12.4.1 due to hard limits on not querying datarefs from background threads 4711: FCC 1B/2A status study screens are mislabeled 4712: LDU channel label in failure description is incorrect 4715: X-Plane 12.4 requires instances to be created from pre-flightloop callbacks 4720: Triggering auto-FO checklists crashes on X-Plane 12.4.1 4722: X-Plane 12.4.1 breaks popup panels due to XPLMFindCommand being invoked from background thread 4778: Reloading while in a hold pattern will reset the hold pattern state and perform hold entry again, 4779: Implement a HOLD DEBUG screen, 4768: Regression: with a lot of crosswind at high altitude, hold pattern tracking gets confused on the outbound leg 4771: Add data ref to indicate shared cockpit role of user 4520: In shared cockpit throttle control is susceptible to jittering 4810: Readjust panel lighting levels to match XP12.3 and later changes 4140: Generator transfers trip off stab & mach trim Enjoy these latest updates, and stay tuned to the forum as we continually announce the latest happenings.

I'm not sure why I feel compelled to give an update today....probably because I'm optimistic about the future and I'm "coming out of the fog". The fog in this case is "X-Plane Developer Documentation", which I've been crafting for over 2 years now and getting close to deploying for a soft-launch/preview/feedback/evolve phase. What end-customers probably don't see, is that there is a major rework going on within X-Plane....the kind where we (Laminar) say to ourselves, "we need to plan and retool for the next 10-15 years". X-Plane has been stretching old tech for a long time....and a deep introspection and plan had to happen. Being that I've been around since 1999, and have worked for Laminar in the past, I thought I might could help ....and in doing so, protect IXEG/Togasim's future in the process, but at the cost of taking time away from overhauling my own products and giving that time to Laminar for the remodeling effort. So my part in the Laminar overhaul, is in the simplest terms to "train developers" how to make awesome add-ons for X-Plane....doing so through better documentation and tutorials...and make development a lot more fun and satisfying for folks who want to try it. Developing is a fun hobby...if we can remove the pain and friction of having to hunt for sparse information. You may recall a major challenge I've had with my products was converting all my source code from Gimzo Lua to C++ so we could be less dependent on 3rd party tech. This is like building a RV-7 experimental airplane...and then saying, "I want to turn my RV-7 into an RV-8". I mean....better to start form scratch. Another reason I'm optimistic is because of AI. In the last week, we have successfully used AI to convert my MU-2 source code from Lua to C++.....BUT....this is incremental, not just a 100% compatibility swap, there are some fringe functionalities we are still working through...and in addition, we are learning how to better use AI along the way and of course we have to check ..every....single....corner of the code to make sure it works. Further, we have to 100% understand what AI did in the conversion. As of today, I'm quite excited about getting back to developing add-ons and participating in helping others improve their add-ons. AI is really making quite the change for the better, and a lot of the initiatives we've been working on internally are fast approaching internal testing and getting closer to making their way to the community. So as far as my own add-ons go.....we are steadily working through this conversion from Lua to C++ and starting to see some quite impressive success. It won't look much different to end-users obviously, but for our part, this is a major, major milestone. Mind you once this AI conversion is done and we have the workflow.....coding will no longer be the long straw in aircraft development. We will be able to focus on 3D quality and systems accuracy and not get burdened down in compilation and coding syntax and the physical time lost to typing. It really is an exciting time, and I know its been a bit of a burden having to wait for AI to grow up to enable this point. First up will be the MU2....probably around late September or October if our current success is any indicator. ....it will be our prototype test case for leveraging AI. Then we'll take that experience and expertise and apply it the 733 and get it ready for another decade of service....and with no upgrade charge to existing customers. On the one hand, I'm bummed its taken this long, and on the other, I really couldn't see any other path, as annoying as its been. This is just the nature of technology evolution...and taking the time to retool was the wiser and more prudent path for long term sustainability. Ben Russell's Gizmo Lua opened the door for incredible products and enabled really creative folks to execute their visions and for this I am very grateful. As with anything in life though, it comes in seasons and we need to look to the next one. -tkyler

Sorry I didn't see this thread until now, but when the TDS was first released for XP I made this plugin that tricks the MU-2 into thinking RXP is present and loads the TDS. Fake RXP.zip

If you hear nothing from us, assume that the project is not abandoned but no work has been done on it that would warrant us sharing any progress info. If we abandon the project, we will announce this here - so if we don´t - you know it´s not abandoned.

Model is finished. Textures are finished. Saso is doing his best to take care of minor issues with the 650, one of which is getting the weather radar added to it. Once he finishes those, he'll send me a new TBM build so I can start initial testing in X-Plane 12 with animations and making sure textures look good. To sum up, as of this post, all artwork is considered done.

Really? If any feature warranted deploying an update, this would be it.

This is absolutely NOT true. It's just their technical support team using canned responses to get rid of you. If you run the installer with --install_name="X-Plane 12.4.0-r2-9b69b91a" command line option then it will downgrade when you select "Update X-Plane."

As much as I can understand the wish for some update to this feature or that - if someone wants "a flight model update" it makes me think he just wants an update because updates are cool (and perceived as additional value). Something that is fine does not need an update.

Yes.

This will serve as an official announcement that we have released the version 2.2.2 update for the SR22 G1000 Series. All customers who have purchased the SR22 G1000 Series up till now have been sent an e-mail by X-Aviation with complete instructions on how to obtain your update. We have made this a very simple process! For those that purchase the SR22 G1000 Series from today forward, your purchased download will already be updated to version 2.2.2 for you. What if I didn't get the update e-mail? If you did not receive your update e-mail don't fret! X-Aviation has updated our system to allow all customers to update with ease, regardless of whether you received an e-mail for the update! Here's what to do: 1. Login to your X-Aviation account here: https://www.x-aviation.com/catalog/account_history.php 2. Find your original SR22 G1000 Series download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: Bug Fixes and Improvements: X-Plane 12.4 / 12.4.1 adjustments and updated dataref usage Latest physics engine Spark plugs will revert to clean status when wear/maintenance system is disabled (previously whatever state they were in before when disabling was kept) Fuel lines are primed by default when persistent systems are turned off Disabled fuel sloshing on ground Expedite priming process until fuel flow registers during engine start Adjusted turbocharger bearing drag and fluctuations near idle (SR22TN) Tuned fuselage Cd for more accurate speeds in pattern environment (SR22) Adjust positive fuel flow with low boost and engine off Replacement of deprecated datarefs Updated libraries and dependencies Adjusted prop disc behavior FMOD Volume adjustments and minor sound tuning Fix error where certain degraded networks lead to stuck loading of aircraft As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support! Enjoy these latest updates, and stay tuned to the forum as we continually announce the latest happenings.

We can't INSTANTLY come out with an update when a new version of X-Plane comes out. As much as we want to, it's unreasonable to expect that from anyone. In the X-Plane world, many developers always recommend to keep 2 installations of X-Plane. A stable version and a beta. Regarding the Challenger update...we're currently on beta 3 within 1 week. That beta is in the hands of our testers. 3 beta's in 1 week is quite fast. There are only 2 of us on the Hot Start team. We can't work on two products at the same time, so while the Challenger is getting updated, we're going to ask people to continue to be patient for the TBM. If you expect an update in the next week or two, all I can tell you is the update will be out when it's done. We want it out as much as you do. But it doesn't make sense to put out an update that isn't ready. Whatever you think about the situation is entirely your opinion. It will have no influence on how fast the updates get done.

It's not worth doing. Laminar can instruct you on how to downgrade if you contact them. We hope to have an update out on our end within the next week or two.

I will be the one to bring it up, is the tbm900 still being worked on for release to x-plane 12, and can we get any kind of update on its progress?

I have to agree with the above statements. I have several planes rotting in the hanger because of updates promised and never delivered. The Challenger 650 desperately needs the weather radar to function and properly. It appears that the plane was made for X-Plane 11 originally and changed to woke with X-plane 12. Laminar Research has made giant strides is the improvement of the Flight Simulator and I truly believe it should the plane developer to bring that experience to their customers. Laminar has created a real time weather with cloud condition for your flight route. The Weather Radar is not just a color changing screen to look at, but critical flight data to avoid dangerous weather ahead. Would you really get on a commercial flight knowing the plane did not have radar heading into sever weather. Yes, this aircraft is very much in need of updates. Not become complacent with your thinking I'm good and so is my plane. Since the CL650 has no Weather Radar maybe a price reduction to $70 US Dollars is needed. Laminar is working overtime on their planes. UPDATE NEEDED: The cabin switch (Mics Lts) on the overhead panel does nothing. What is this switch for? The anti ice switch for the Wing works backwards. To move the switch down you must direct the switch up. Therefore, to move the switch up you need to direct the switch down.

Apologies for the late reply. I'm working on a large update for the DC3. I'll make a note of this and address it.

Still no new for the XP12 and specifically 12.3.1 upgrade ? at least now we can expect the new real weather wx radar ;-) For turbine fan, in addition of the XP12 EPIC1000 and PC12, a Piper M500 XP12 should be released rather soon

It doesn't warrant an update? I think it absolutely does. Other aircraft have had an operational weather radar for some time now, but it's been missing from the CL650 - one of the most expensive aircraft addons available. I rarely fly the CL650 now because it is missing Wx Radar. It's a great aircraft, but incomplete since it's missing critical functionality. I routinely receive updates for other expensive aircraft addons ive purchased, but not a single update has been released for the CL650 and I've owned it for 5 months now.

Tkyler, Appreciate the update on your activities with Laminar. That is good news for everyone using XP. Look forward to your future work with the B737! Thanks! Rich Boll

Man, its a shame this project never materialized into what it was supposed to become. I used to love flying the ixeg in xp11 and had high hopes it would be completed. Every now and then I check back on this forum to see if anything has changed and unfortunately still nothing. Xp12 is looking seriously good these days, I just wish the ixeg 737 was up to par because it has huge potential.

Quite some time ago, but tried it as shown in your video and good enough for me

It's not dead at all!. Before I say this, a bit of disclosure. I AM NOT involved with IXEG, and I will not discuss or mention details/plans I will let official channels do so. I met Tom at FSExpo this past year in PVD and had a good hour long discussion with him about (mostly) the 737 we all love. NO IT'S NOT DEAD. He discussed details with me that if he wishes to share one day he can, but it's not my story to tell. But it's a VERY interesting story at that!. You folks would not believe the dark side of developing that happens. Like many of you, I too have been frustrated with the 737, but after talking to Tom at Expo, I can say I heard it from the horses mouth, THE 737 IS STILL BEING WORKED ON!!! Again I won't discuss what Tom discussed with me about what's being worked on. ALso @tkyler I would like to thank you again for you time at expo, was an absolute pleasure meeting and talking!

Made up stories from a dramatic streamer. Nothing new.

I find this thread an interesting and an informative read. The only question I have is X-plane 12 came out with a recent update and just would like to know about compatibility with the CL650, and where I can get such reports of when CL650 has been tweaked to conform with the update. I’ve run into nightmarish issues with incompatibility in the past and would like to avoid it.

Hi, do you guys have a timeline on the update? I'm curious if I should buy the steam version so I can go back to 12.4.0.

You obviously haven't been to our discord where we answer countless questions. The 2 most common ones? When is the 650 update coming out and when is the TBM update coming out. Both questions are always politely answered. Your comment is out of line and not true.

Yes, there are quite a few parameters to be met for an autoland approach to be legal (and safe), I think the crosswind limit was like 10 kts (it goes down with decreasing RVR). The 737´s autopilots have no access to the rudder, so it can not "decrab" or "sideslip" to counter crosswinds. It can also not maintain the centerline after touchdown (rollout), so all it does is fly you to touchdown (in full crab) and then the pilot has to take over and manage the rollout. Also keep in mind that some ILS localizers in X-Plane are not very well centered on the runway, this is due to inaccurate government data on localizer direction and also a certain leeway LR allows airport designers to place their runways (iirc it´s "within 5 meters" of the official runway end coordinate).

Now that the final version of XP12 has been released, is there any timeline for the CL650 weather radar to be implemented?

That is absolutely your prerogative. Some say minimal activity and updates indicate a lack of care by the developers, others say minimal activity and updates indicate a mature product that is not in need of them. As a developer I am partial, of course - but I personally still love playing games that have not had updates in decades, like the car I am driving, and both work fine. Ultimately I think the conclusion constant updates = high value is false, in fact some of my games that get constant updates leave me with the feeling that I "rather hold off playing them until they are done". Just my 2cts .

Still things to come, and you're right, X-Plane 12 is looking great!

Can we therefore agree that it would be mutually beneficial if the IXEG team posted status updates from time to time? So that customers don't conclude that the aircraft has become "abandonware" and so there is awareness that issues are being worked on? It's not unreasonable to provide an update every 6 months or so - "Hi guys, the work on version 1.6 is proceeding steadily, our priorities are recoding of the FMS and recording of engine sounds. Lots of work still remains with FMS rework, we've tackled 10000 lines but there is still 600000 to go. This will address some of the VNAV issues of previous versions. We've rerecorded some of the auxilliary sounds. We're hoping to work on some improvements to the cockpit texturing but that's aimed at future updates". The amount of time it takes for a post like that to be collated and written and it'll reduce the backwards and forwards, misunderstandings, wrong assumptions, arguments and offence. People will no doubt say "is there any update" - quote the latest update and say "Our last update remains accurate - work is still ongoing. There is not much else to say"

Hi, @Cameron I’d like to clarify something. At no point was I disrespectful in my wording. Using terms like “abandoned” or “disregard” was not meant as a personal attack, but rather as an honest reflection of how the situation looks and feels from a paying customer’s perspective. I believe constructive discussion includes not only praise, but also criticism...sometimes strong criticis, especially when issues remain unresolved for years. Expecting customers to tone down their language to a point where frustration cannot even be expressed seems unreasonable. I respect the work behind the scenes, but I also ask for the same respect in allowing honest, even if firm, feedback.

Eventually, yes.

The Challenger can be hard work on the approach and landing, but when it all comes together it's very rewarding. All the beta testers had difficulty learning how to land, it's all part of the fun. On approach be aware that unlike aircraft like the 737, the pitch response to power is reversed, that means a power increase will see the aircraft pitch down for a moment. This can lead to an oscillation developing, so be sure to fly the pitch attitude accurately. If you find you're wobbling up and down, aim to make smooth power changes, and remember the HUD flight path vector is useful tool, but can get you into trouble too. A useful check is 0.6 on the AoA index on approach. If it's higher than that, you're too slow. Remember Vref +5, and check your weights on the approach ref page. For the landing flare, lift the nose to to arrest the rate of descent, starting at just below 40 ft. Make a smooth power reduction and fly the aircraft onto the runway. The pitch attitude in the flare is around 3 degrees, but look at the end of the runway, not the HUD! You'll have plenty of time for butter later, so for now put the aircraft down positively in the touchdown zone. If you go butter hunting, you'll only find little bounces - ask me how I know! Once you've landed, extend the flight spoilers (the ground spoilers are automatic, but the flight spoilers need to be raised by pulling the lever), use the reversers and you're down. And stay away from that HLIS button, it'll trick you into making your landings worse!