Leaderboard

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.

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."

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.

Yes.

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.

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.

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.

Made up stories from a dramatic streamer. Nothing new.

What I found was that once the engines are running, then you can activate the mode. That doesn't make a ton of sense to me....I have observed some voltage datarefs begin tied to the engine RPMs...but can't speak to as if there's some connection between voltage and the mode...that's philipp's territory. I do know that Philipp has spent a ton of time fiddling with electrics and he also writes the code for autopilot behavior. If he shows up at FSExpo, I plan to get some clarifications on how its supposed to work and how he designed things. He may have a perfectly plausible explanation. But if you start the engines...then everything does seem to work as expected.

quite understandable, but still a pitty

Hi there I just updated to the newest version V2.2.2. When I set the Garmin-map to the following screen (see screenshot) to get airport-informations, the WX-key doesn't work. When I press on it, nothing happens. It works perfectly in the default SR22. I would appreciate any help. Many thanks.

I only see one instance of that 9 days ago now that I've searched. Either way, we're fairly confident after a code audit X-Plane is misrepresenting the faulty plugin here. The reasons why need not be discussed here, but Laminar should work to fix this so we're punting it to them.

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.

Thanks.

Oh, I didn't realized that. But anyways, if that turns out to be the issue -that the CL650 doesn't work because of XP11 and its age, then I'd have to buy XP12 anyways. And it actually turned out that XP11 itself was the problem, because in XP12 the CL650 works far better than ever and I have overall much, much better fps on top of a far better graphic. The switch was definitely worth it. But I wouldn't have done it if it wouldn't have been for the Challenger. PS: the two knobs(HUD and EVS) in the Captain's Glareshield pop up window are still missing though.

Hi X-Aviation-Team, i've just downloaded the latest version of the Challenger 650(v.1.9) and installed it. After that I've ran into a couple of problems. -The first one was a pop up text that told me: "There were several minor problems loading the aircraft: Aircraft/X-Aviation/CL650/CL650.acf You may need to update the airplane or report this to the aircraft's author. Please see the log.txt file for a list of the problems" -The next issue was: the entire lacking of any kind of HUD-symbology even though the aircraft and all generators were running -The third problem were: two missing knobs on the Captain's glareshield pop out panel, including their functionality -just like in the virtual cockpit. I've never had those problems with the v1.8. version -Then there was a fourth problem: something I've already encountered before and in all versions of the aircraft, a total system crash after I've touched the CDU mid flight. The only solution to that is an entire reboot of my computer. Here are some pictures and the log file. Thanks in advance Log.txt

Not sure what you mean by that. The "EFB" is just AviTab, nothing else.

I gotta tell ya, I love that image. Good thing we didn't know then what we know now.

Same issue. PDC message status shows as being received, but the actual clearance doesn’t show up. EDIT. Could be an issue with my SI callsign not set to match the aircraft. I’ll try again. EDIT2: nope not working. I can see messages in the SI logs but nothing coming back to the aircraft.

This plugin is causing your issue: C:\Program Files (x86)/Steam/steamapps/common/X-Plane 12/Resources/plugins/GndHandling/

It seems to me to be quite a complex matter, and then there are the constant beta changes that undo some of the work – it must be incredibly annoying! It's a shame there's absolutely no headroom left since the brightness sliders are already at 100%. Perhaps a little more brightness will be possible when X-Plane 12 is finalized!

In the Citation when using the TDS garmin GTN750Xi, in turns the roll bar on the flight director is incessantly twitching back and forth, and the AP is also constantly varying the bank angle, resulting in a small but annoying rapid wing rock. It appears as if there are conflicting roll inputs fighting each other. It does it with the UNS on or off. Any ideas on how to calm it down?

I'm not sure what happened. After I rebooted my computer, the reverse starting working. We'll see when I restart my PC tomorrow. Thanks for your interest in helping.

Hmm, I can't confirm this Behavior. Two short Flights, one with the 4 Blade GNS and one with the 5 Blade GNS. XP12.4.2-r2 AP did work as expected. HDG Mode, ALT Mode, NAV Mode with and without GPS, ILS Approach, all did work. My Startup from Cold and Dark, no GPU connected: Battery Switch ON Inverter Switch to MAIN Position Battery Isolation Normal Avionics OFF AP SBY Switch Light Green but no Action yet because Avionics OFF Initiate Engines Startup Sequence with all the needed Stuff. After Engines Start, Generators ON and Avionics ON. AP SBY Switch Check -> All AP Lights ON. Before Take Off -> No AP Mode selected, only Heading Bug and Target Altitude set. Flight Plan loaded. If there is one. After Take Off and reaching the Altitude and best Speed for Climb and AP Activation: - select HDG (stays green) - select ALTSEL (green) - select IAS (green) AP ON Yaw Damper ON If a Flight Plan is active - Garmin CDI to GPS, AP NAV Mode enabled, GPSS Roll Steering Switch (GPSS HDG) to ON. And the Moo is happy following the Magenta Line. So, no AP Mode selected while on the Ground, only in the AIR. That did work since I purchased the Moo and with all XP12 Version since the first Release. Betas included. Did you check your (new made) Joystick Profile for the AP Settings? I use the Honeycomb Alpha and Bravo Devices with the Original Plugin and a simple Plugin Profile only for the Lights and the Rotators. The AP Switches are Standard XP References and I can use both, the Buttons on the Bravo and the Buttons in the Cockpit.

@jrsaez82 I know its been a long time since i've messed with the MU-2, but I expect to come back around to it within the next 2 months and start pointing it to the future. I'll make an announcement and explain the timings and future at that time. There is a lot of really good and positive developments going on behind the scenes at Laminar, which I'm involved in....and for the better. Quite a bit has changed with regards to the flight model and electrical system models and I fully suspect that Philipp may have put some type of criteria on enabling the various AP modes based on more advanced "amp flow" and voltage models that he implemented well after I coded these systems up....so its absolutely incumbent upon me to find out what those are and bring this thing up to speed. As silent as i've been here, I honestly have never been more involved with X-Plane than I am today....and I am fortunately being able to contribute to overcoming the impediments that have historically caused delay headaches for devs forever, including me. We've been asking the questions internally, "what slows devs down and makes it hard to update and test" and are engineering solutions for that....something that has been sorely needed for a long time.

Honestly, one of the things in life I can wholeheartedly loathe. Not just it messing with circadian rhythm, my meetings, commuting in the dark, and my mood. But I am even doubting any of the "crime" and "economic" impacts that are touted. The only people that seem to be for it, are in Government.

Welp Felis 74 and this bird are the only two aircraft I have interest in, regarding XP-12 .. So far incredibly after all these updates, IXEG still flies sweet.. I've made a little tweak to the startup sounds.. Personally the main update for me would be FMC.. The sounds are pretty sweet as they are for now. Whilst I am capable of doing manual holds I would prefer it to be taken care of xD. Meanwhile I have found a plugin that automatically does it. Do I love this addon?, yeah.. Do I think it's a "Broken promise"?.. I don't remember being promised owt, If that's my ignorance, then fair play xD.. All I know is I paid 80 quid for 737 simulation that lasts indefinitely that appears to do (to the best of it's ability) what a real 737 does.. I could rent a sim down south for 2 hours that might do a better job for nearly 300 quid. IXEG 73 is a gorgeous plane and I hope I get few more years out of her. I'd be grateful for any future developent. I always think to what I got when I was a Kid, back end of 90s lol. I have moaned in the past, but I since grown out of that crap.

In a nut shell. Project was nearly dropped completely. Some developers allowed continuation of project just with less people. Developer all spent time helping laminar. With less people its getting a complete FMS update to use XP nav data and fix nagging nav issues, its also getting a complete sound update to FMOD. Wont happen in a hurry with less people. Yes I read a lot

Every time I load a flight I get a CTD with 'threading violation' in the log. 2026-03-31 13:55:31 CL650[libsvs.c:4912]: libsvs(SVC): utilizing background rendering via IOSurface Threading violation calling XPLMGetDatai (/Users/administrator/.gitlab-runner/builds/5iac3Er_D/0/x-plane/design/SDK/COMMON/xplanesdk/Src/XPLM/XPLMDataAccess.cpp:327) Violation by Challenger 650 by Hot Start (hotstart.challenger650) 2026-03-31 13:55:31 CL650[except.c:120]: Caught SIGABORT: abort (0x1a049d5b0) Backtrace is: 2 libsystem_platform.dylib 0x00000001a04e1764 _sigtramp + 56 3 libsystem_pthread.dylib 0x00000001a04d7888 pthread_kill + 296 4 libsystem_c.dylib 0x00000001a03dc850 abort + 124 5 XPLM 0x000000012aba52c4 _Z26__XPLMValidateThreadSafetyPKcS0_i + 536 6 XPLM 0x000000012ab938ac XPLMGetDatai + 56 7 systems.xpl 0x000000037117028c wfETC1_DecodeImage + 130948 8 systems.xpl 0x0000000370ed55b4 XPluginReceiveMessage + 4031316 9 systems.xpl 0x0000000370edbed0 XPluginReceiveMessage + 4058224 10 systems.xpl 0x00000003711a6e78 wfETC1_DecodeImage + 355184 11 systems.xpl 0x00000003711a3840 wfETC1_DecodeImage + 341304 12 libsystem_pthread.dylib 0x00000001a04d7c08 _pthread_start + 136 13 libsystem_pthread.dylib 0x00000001a04d2ba8 thread_start + 8 --=={This application has crashed!}==-- In the X-Plane release notes it acknowledges that the Challenger 650 is not compatible: https://www.x-plane.com/kb/x-plane-12-4-1-release-notes/

Laminar released the current stable version of X-Plane 12.4.1 today on which the current version 1.8 of HotStart Challenger 650 crashes with the error "Threading violation calling XPLMGetDatad". Loading the TorqueSim SR-22 crashes with the same error. The release notes of X-Plane even state the issue. I hope this gets fixed soon as there is no way of getting an older X-Plane version on new installations.

Hi all, I would love to show you the failures manager V0.1 for the Hotstart CL650, I am still working on the project and would love to make it open source so other can profit from it. I will leave some screenshots bellow for multiple fonts I made, you can choose your own. Im still new to coding and having to live in a war torn country doesnt make it easyt too, so be easy on me haha.

Correct. Challenger is top priority. Saso has done some amazing work on it.

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

Note: this is already integrated directly on Simbrief (see above) so the link below now only exists as a backup. LINK HERE Note: aircraft name is clipped to 12 characters for custom airframes, sadly (limit does not apply to default profiles). Fixed by SimBrief Based on the already-accurate default CL60, with the following adjustments: equipment codes and extra flight plan remarks kindly provided by Graeme_77 here: OEW/BOW updated to match the Hot Start airframe without passengers (12,315 -> 12,556kg, includes two pilots) passenger weights updated to somewhat more closely match the randomized weights as simulated, going with 74+15kg so you can still carry 5 passengers+luggage and full fuel at MTOW if you are flying Kim Dotcom around (supposedly ~141kg or thereabouts), sorry, you will have to make adjustments, or just count him as two passengers see below for more information: Don't forget to add extra crew (anything above the two included in OEW) as passengers when planning your flight! Cheers, Tim

Hi @imemyself it has been a while for sure and a valid question and I have no real excuse. The last year has very much been a "foundational stabilization" year. I'm getting close enough to retirement to start eyeballing these next 6 years and how to best navigate them after the Covid ripples upended several things in my life. A year ago this time I had an opportunity with Laminar once again and I took it....the previous years since Covid were a bit rocky and I had some catching up to do, which I have mostly done over the last 12 months. I've spent sporadic moments in the year working on the 737 FMOD conversion and we're in final sound testing on that. The MU2 has taken a back seat during this time. I have recently integrated X-Plane's new weather radar and most of the known issues are fixed, which you guys won't see till 12.4 or 12.5 perhaps, so I have been chipping on it. An update absolutely will be available and it is still maintained and will be for years to come I suspect. I took the gig with Laminar to "stay in the X-Plane ecosphere" and some important personal things have transpired this year that should clear the way for more XP work. I know that's pretty hollow talk considering the last year, but I'll just wrap up by saying there are no plans for me to abandon the MU2 and I get reminded about it frequently...so the pressure is on and felt.

I use it regularly in XP12. Weight and Balance is Fuel only, no Passenger or Cargo. There are a few Bugs (no Lights for the selected COM, Right Push Button on G500 Inop) that annoy me but Flight Performance seems pretty close within the Limits of the SIM. I use the Classic Cockpit Version without the Radar. I hope there will be a Fix. Maybe one Reason is the Status of XP12 with it's fast changes in short Time that could be a Nightmare if you are the one and only Developer for a Project. Latest announcement from the Developer was, that he was working on this and some Performance Updates. But that he needs Time for Testing and his Time is limited because of other Projects. But a short sign of Life would be nice. And maybe a small Fix for the COM Lights and the Push Button.

X-Plane 12 - Pilatus PC-12/47 - Sedona to Telluride Pilatus PC12/47 by Thranda Design Sedona Airport and Scenery by X-Codr Telluride Regional Airport UHD and Scenery by X-Codr

On the learning curve with a Skyhawk, toward EDDF (Germany). As you can see, Ortho4XP doing a fine job.

Hello Marcus, Phew that's quite a bit to answer in one post. Let me try and cover it. 1) ILS approaches. Let me describe the normal method, assuming you have a FMS flight plan with an ILS approach and you've checked the lateral coding to make sure it all works. You don't need to set anything up specifically for the ILS. Loading the ILS approach should be enough. Make sure the left PFD is navigating with FMS1 and the right side is FMS2. You will have a magenta CDI indication. When you are close to the airport you'll also see blue "ghost" indications on the HSI and blue diamonds in the localiser and glideslope scales on the PFD. Typically when the final approach point is the next waypoint, press the APPR button and this will arm the system for localiser and glideslope capture. You don't need to mess with the altitude knob as long as the aircraft is actually at the ILS platform altitude (you shouldn't need to do this with a 737NG either, but that's another story). When you capture the glideslope, set the altitude for the missed approach altitude. 2) Speeds. Manual control of speeds is normal using the speed knob or manual thrust. If you have VNAV enabled you can resume the VNAV speeds using the PERF page on the FMS, but really that's a bit pointless and it's easier to fly it on the speed knob. You need to know 250 kts, 200 clean, 180 with the first stage of flaps and 160 with gear and the second stage of flaps. Select the final stage of flaps and slow to vref + 5. It's no more complex than that. Even on an Airbus with managed speeds, lots of pilots prefer selected speed modes - LNAV/VNAV and chill is very much a sim-ism and not how aircraft are actually operated. 3) It's just a machine, so isn't very likely to "freak out" as you say ;-) Bearing pointers have no influence on flying the approach, they are for the pilots reference only. I'd suggest reading (1) above carefully, then pick a long ILS approach, and post some screenshots of the aircraft level at the platform prior to intercept, and another couple of pics on the approach. Suggest EDDF 25L via CHA VOR - grab a screenshot flying level at 4000ft between CHA and LEDKI, and another on the ILS at 3000ft, and another at 1500ft - make sure we can see the full PFD clearly.

Hi all, Thought i'd post a few screenshots of some of my recent flights, all have had some tweaking in photoshop to give them a slightly more real appearance.

Ops Reference manual has some clues too. In the documentation folder.