Leaderboard

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

I almost forgot about this. In all honesty, it's quite low on the list of priorities at the moment. It still needs to be researched, and at what severity the wing flex happens and under what conditions. Once all the important updates are out of the way, and there are a few, we'll take a look at some cosmetic improvements, including the wingflex.

Flew the Piper M500 from Flagstaff, AZ to Casper, WY. and discovered the staggering diversity of terrain along the way.

Tom understands C++. Like it or not, AI is a powerful tool these days. Understanding how to properly use its strengths does not constitute slop if you know how to audit and architect the language.

This will serve as an official announcement that we have released the Version 1.1.0 update for the Take Command! CitationJet 525. All customers who have purchased the CitationJet 525 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 CitationJet 525 from today forward, your purchased download will already be updated to version 1.1.0 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 Take Command! CitationJet 525 download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: New Features: Integrated weather radar featuring the RDR-2000! Many thanks to Amy Parent and the Laminar team for such an amazing addition to X-Plane. Library and code adjustments throughout to fully support X-Plane 12.4 Updated and improved FMOD sound pack Improved and tweaked objects, textures, and animations throughout Bug Fixes and Improvements: Latest UNS-1 version (v1.22) Fix crash when the last airport in the flight plan is on a FM leg. Fix dates incorrectly formatted (month off by one after april, #72). Fix distance computation of arc (AF, RF) legs. Fix times displayed with 60 minutes past the hour (XX:60) in some situations. PVOR now pre-fills inbound track for runways picked from list. Fix PVOR using true runway heading rather than magnetic. Fix bad localizer front course parsing leading to off-course CF legs. Fix VOR and LOC database declination not used for CF legs computation. Fix standby resume failing to restore flight plan when using “radial/radial” custom waypoints (#76). Latest version of libradio to fix X-Plane 12.4+ compatibility Adjusted base system library with ordering fixes Replace deprecated dataref usage Adjusted particle system dynamics Migrate to new X-Plane chock system, fix rolling away on ground Fixed missing altitude minimum alerter, 500ft Improved accuracy of EHSI color schema Fix buggy DME behavior for speed/time, with improved alpha/beta filtering Transponder code, flaps, and fuel persistence Improve custom tail system handling with missing fonts Fix bus for flood light Add nose and aft cargo lights Fix handling for COM1 to be usable with EMER battery Flood light correct electrical bus 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.

That worked thank you very much. jeffg

Unacceptable...

Same issue and its not even with X-Camera. Dissapointed to say the least like mlb406 said with an $85 aircraft. And this forum seems dead too.

Thanks for the update, and I'm eagerly awaiting all the new features. New things are always welcome.

A bug triggered by noisy hardware. Will be resolved in next update. Workaround is to add a dead zone to Yaw axis.

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.

Reduce your text and display scaling to 100% so you can see the email and password fields. https://support.microsoft.com/en-us/windows/change-your-screen-resolution-and-layout-in-windows-5effefe3-2eac-e306-0b5d-2073b765876b

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

Yes.

As this topic got unlocked again, I guess questions about the update are OK to post here. Nice update, thanks for that! When installing the new version (on Windows), will all settings, state etc. from the former installation be preserved? Generally, a note "how to perform the update" should be part of any release announcement so people can see wether it's a no-brainer (just install "over" previous version, settings preserved) or involves effort to get into a "usable state" again. Thanks! Best regards, Daniel

Where can we find the landing ref speed? Thanks.

Yes.

Hi Graeme, The more landing i do the worst they are getting. I bounced almost at every landing even on firm / positive landing. I am for VREF +7 and making sure that the AoA is 0.6 max. However on release, during my landing trainning, i never bounced, it feels like the ground effect has changed in between

1 ACTION at the top right means that you need to do it. 2 ACTION means the FO will do it, and CONFIRM means you have to check it.

I agree that a short one page on the UI of the checklist system would be very helpful.