Leaderboard

Take a look into the IXEG interface documentation, you can find there a list of the datarefs. Second thing would be to install DataRefTool to find out the datarefs for all the activators used in the plane.

I think it’s reasonable to want some clarity before investing in an updated version, especially when the last visible update was in 2023. I’d also like to know how well the plane performs in the current XP12.1.4 environment and whether the developers have plans for future improvements. Slope Rider

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

No forward slash between waypoint and bearing.

This is not the same. Your log shows the plugin causing the issue. Violation by XTLua 2.1.1 id42

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.

What you hear there in the cockpit is the trim mechanism, trying to keep the airplanes attitude correctly. Switch off AP and it will be gone, but then you have to do the work alone.

Thanks for your immediate reply. Tested it and this is, what I found out. I use the IXEG_Failure script to induce random failures, but it was not active at this flight, therefore I don`t understand that this happened at all. I could not create the situation again, thus I was not able to test things with gear lever down. With gear lever up, manual extension of the gear does not work. With gear lever in OFF, it works as expected, independent of hydraulic the pressure. Would have helped to read the complete sentence in the QRH : in the NG manual gear extension can be accomplished with landing gear lever in ANY position. However for standardization with the CL the lever is placed to OFF. Strange wording, but yes Achim

The upgrade promotion was available only for the first 60 days post release and has been long expired. There is no discounted upgrade path available for a few years now.

PH-OTH CIS Navajo Chieftain View File This is a livery for the CIS Navajo Chieftain PA-31, inspired by PH-OTH. To install, extract the zip file into the "liveries" folder. If you enjoy my work, consider supporting me on Patreon to cover some of the horrendous Adobe-costs ;). You can find 8K versions of most of the liveries there. Submitter pilotdeviation Submitted 07/17/2026 Category General Aviation  

I believe this file can help. It is a work around for the Direct to buttons. Be sure to backup your original 525_CLICKABLES.obj file before inserting this one. Also, you will need to remove my ".repaired" extension from the new file to make it read "525_CLICKABLES.obj" (less quotes of course). Place this file in the "X-Plane 12\Aircraft\X-Aviation\TorqueSim CitationJet 525\objects" folder. Should be good to go and not sure why this hasn't been corrected yet either. 525_CLICKABLES.obj.repaired

Made up stories from a dramatic streamer. Nothing new.

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.

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.

Jurassic Park N293G X-Trident AW109 View File This is a livery for the X-Trident AW109, inspired by the AW109 from Jurassic Park. To install, extract the zip file into the "liveries" folder. This livery is in 4K. If you enjoy my work, consider supporting me on Patreon to cover some of the horrendous Adobe-costs ;). Submitter pilotdeviation Submitted 05/14/2025 Category Helicopters  

Depend on the operator and what they have available. Many operators use a flight planning service that also contracts with a performance engineering service provider. For the business aviation fleet, that is usually Aircraft Performance Group: Aircraft Performance Group: APG (flyapg.com) APG provides the airline-style airport runway analysis. If you're familiar with TOPCAT (FlightSimSoft.com), it is the same thing. You would simply run a landing analysis report for the airport of intended use and then see if the maximum landing weight meets your requirements. In the US, for part 135 or 91K operators, their minimum field length is normally based on actual landing distance allowing the aircraft to stop within 60% of the runway's declared landing distance available. This minimum field length is increased by 15% if the runway is forecast to be slippery or wet at the ETA. Some operators can reduce the runway required to where the actual landing distance will bring the aircraft to a stop within 80% of runway's LDA. With EASA, they do not permit this type of reduction...yet. Last I heard, they are looking at it. On the QRH for the CL650, for different pressure altitudes there is a chart that provide the "LFL" or Landing Field Length both for a dry runway and a wet runway for each weight at a given pressure altitude. Since LFL "assumes" standard temperature, there are no corrections provided for temperature. The chart for a given pressure altitude also give the actual landing distance (ALD) at various landing weights and temperatures. These QRH chars can be used if you do not have access to an airport runway analysis service. One more thing to consider is the landing climb requirement and approach climb requirement. Landing climb requires a minimum 3.4% climb gradient, 8 seconds after go around thrust is selected, with the aircraft in the full landing configuration. Most turbojets, this requirement is not limiting. The other requirement is the approach climb requirement, which requires a 2.1% climb gradient at maximum go around thrust with one engine inoperative, in the approach configuration for a go-around, and with the landing gear retracted. This a "spot" or snapshot performance requirement at the start of the OEI go around. On the QRH charts, I noticed that ALD data is not provided above certain temperatures at certain higher pressure altitudes. Most likely reason is that the aircraft does not meet the approach climb requirement at those pressure altitudes and temperatures. A closer look at the performance charts in the AFM would likely confirm. If you would like a good primer on transport airplane performance, may I refer you to the NBAA website that host the FAA TAPP WG performance videos: Aircraft Climb Performance Videos | NBAA - National Business Aviation Association They're also available on YouTube from the FAA. Here's the first of four: Thanks, Rich Boll

CrewPackXP - Crew Callouts View File **Updated 01/04/2022** CrewPackXP is a FlyWithLUA utility designed to add some crew communications for aircraft in X-Plane 11. This includes basic callouts, and in some cases assistance from the PNF in high workload phases of flight. Settings can be adjusted to enable or disable the whole plugin, or just certain features of each aircraft. Flight Factor 757 / 767: - Virtual FO to pre-flight aircraft - Take-off and Landing calls by both crew members - Flight Attendant PA's - Ground Crew positioning of equipment - Virtual FO assistance with go-around procedure Hot Start Challenger 650: - Virtual FO to pre-flight aircraft - Take-off and Landing calls by both crew members Source Code https://github.com/N1K340/CrewPackXP/tree/main/src Documentation http://crewpackxp.readthedocs.io/ Changelog New features and bug fixes are listed in the change log. Installation Copy the Scripts and Modules folders into the main folder of FlyWithLUA: > X-Plane 11 > Resources > plugins > FlyWithLua Once enabled, the First Officer should announce his entry to the cockpit roughly 15 seconds after loading in. CrewPackXP settings can be accessed via the X-Plane menu bar: > Plugins > FlyWithLua > FlyWithLua Macros > Crew Pack Settings Prerequisite This plugin uses the FlyWithLUA plugin to interface with X-Plane. It is available freely from [X-Plane.org](https://forums.x-plane.org/index.php?/files/file/38445-flywithlua-ng-next-generation-edition-for-x-plane-11-win-lin-mac/) Luna INI Parser (LIP) is included as an additional plugin module for use with FlyWithLua. This module allows for the saving and reading of settings data within LUA. It has been included in this package under the MIT Licence offered by creator Carreras Nicholas. This is a common plugin; it may already exist in your modules folder causing a prompt to overwrite. Usage The CrewPackXP functions run autonomously based on in sim events, provided the aircraft is enabled within the CrewPackXP settings. Refer to each aircraft's entry in the manual for details on settings and features available. Disclaimer / Feedback This package is to be distributed as Freeware only under the GPL v3 license. This is the first time I have coded a plugin, any feedback is welcome. Bug reports, please include the x-plane log.txt file in the main x-plane folder for the flight in question. Acknowledgements Carreras Nicholas - Luna INI Parser (LIP) 'Togfox' - FSE HUD 'X-Friese' - FlyWithLUA Plugin 'mkultra44' - Documentation proofing Current Script Versions - Flight Factor 767 - 1.4 - Hot Start CL650 - 1.4 Submitter N1K Submitted 02/11/2022 Category Plugins and Utilities  

There is still ongoing work happening behind the scenes on this product. It runs fine in the latest X-Plane version, and we keep up with monitoring that.