Leaderboard

I do Seriously. still going every single day...we'll be making an announcement/report about whats going on here within the next few days. I'm trying to get to a specific point before we give a more formal update and I don't want to rush it....I'm as picky as most of you folks, so I'm steadily laboring away towards that point. -tkyler

Is there anyone else that visit this page everyday hoping for a good news??? no pressure guys, just very anxious for this one, by far one of the most amazing mod for the Flight Sim community... Thank you for putting so much love on it!!!!

I want to thank everybody for their patience here. We won't make March 8th as mentioned previously, but not for lack of attention to the update process. We do plan to give a more informational update next week though and I still feel we're not terribly far away from a release as work continues regularly. The roadmap for myself (being both IXEG and TOGA) is to get this port update out, then I'll binge the MU2 for 4-ish weeks, getting it refined for V12 and then take a deep breath/short break and dive into the FMS / VNAV functionality of the 733 while also seeking out other areas to improve throughout the remainder of the year. Thx again. -TomK

A freighter version for the -400 has potential because the workload to produce that is "relatively" light. The -500, being a shorter variant would require a much more laborious effort to change both the 3D and the flight model, being geometrically disparate...and the return on investment in that, I believe, probably would not justify the efforts. While I think a freighter variant would appeal to a statistically smaller set of customer use cases, I recognize that there is still a place for it...and so I do want to do a -400 freighter at some point. ..and yes, I'm still working on the 733 every day...my carpel tunnel and "tennis elbow" remind me constantly. I think I can safely say at this point that we'll definitely put out a more informative report this week on whats going on with the development. -tkyler

All I have are things I look at and go..."yea...I'd like to improve that". ...but first and foremost is the FMS / VNAV work of course. Right along side that is a conversion to FMOD based sounds, which will allow us to expand the sound set to cabin/ambient sounds or whatever we can think up, etc. Also, I'd like to improve the 3D in several spots...it is, after all, over 10 years old. I can foresee a high-resolution exterior and textures at some point, which would necessitate new livery repaints, but oh well If I have to redo work with the evolution of X-Plane and computers, so will livery artists I'm going to look at the feasibility of implementing a cargo variant also..unsure the workload just yet. And we are moving to imGUI based interface, rather than the custom widgets we built previously. The thought here is that will allow us to integrate more 'management interfaces' for handling failures, flight setups or providihng additional graphics, etc. Of course working cabin doors, a completely new cabin interior and some wing flex would be nice.....but that work is taking a tiny bit longer than I........um....I mean....yea...those features would be nice to incorporate! Beyond the 733 work, I have another project I'll be working on in the back half of the year alongside the 733..and then one more in 2024 I'd like to tackle and that'll probably be it.

Dear Captains, Has been a long time since the last update, but we have been working continuously, especially the last months. We are now at the point, that this might be the last developer's update before release. X-Plane 12 As you already know, a lot of things happened the last year; the biggest one, the release of X-Plane 12. We were participating in X-Plane 12 alpha testing, from day one, and while we were proving feedback to Laminar, we also testing DC-3's compatibility, and how we will react to this change. Initially, without knowing XP12 release date, we were planning to release for XP11. But around Autumn, with the X-Plane 12 beta out, it was obvious we had to support X-Plane 12 as well. In those testing days, we were continuously switching between X-Plane versions, to be sure that things work right for both simulators. But, with the new stuff X-Plane 12 brought, it was obviously that we cannot have a common aircraft for both versions. Even we tried to have a version with only what works in both version, but that was going to be a half-baked product, so was no go. Also we took a decision (read below), that would have made parallel development impossible. Given the extension of our development roadmap, we were sure that DC-3 release will happen after the official X-Plane 12 release. So, we decided to move forward and support only X-Plane 12. Introducing DC-3, Modern aircraft version! While all the above was going on, brainstorming together with our beta testers, we decided to create a second aircraft with more modern avionics. While the, the now named, DC-3 Classic gives you all the vibes of the 1940's technology, it was going to be hard, if not impossible to perform flights specially in online networks. Also, the newer, "Modern" aircraft is more accessible to more pilots, having instrumentation that is very well known, widely used. Of course, that does not mean, just drop a few instrument (idk... like G1000s ) and call it a day. Everything designed and developed to work as per manuals. Here what is new: Pilots' Stations: 1. Pilot's HSI: Bendix/King KI-525A. 2. Pilot's RMI: Bendix/King KNI-582 Dual Pointer RMI. 3. 2 Course Indicators, one for each pilot. 4. 2 independent KDI-572 DME indicators, one for each pilot. Radio Stack: 1. Bendix/King KAP-140 Autopilot - Two Axis with Altitude Preselect. 2. X-Plane's GNS 530, with support for RealityXP's 530, which also provides controls for COM1/NAV1. 3. Bendix/King KX-165A VHF COM/NAV transceiver, for COM2 and NAV2 tuning. 4. Bendix/King KT-73 Transponder. 5. 2 Bendix/King KR-87 Silver Crown ADF systems. All radios and autopilot are fully simulated and perform all normal operations, as described in their manuals. For the rest of the systems, they were updated were needed, and adapted to operate with the new aircraft. The maintenance and airframe systems, are also apply to the Modern aircraft as well. Conclusion We are reaching the final stretch of this development road, and will be very happy to provide you 2 aircraft, the Classic for the vintage aircraft enthusiasts, and the Modern, which is more capable, in terms of IFR operations. Time for a couple screenshot of the new aircraft, right? (of course still WIP!)

Eagerly awaiting some info! Love this bird.

I am fairly hopeful that the flightmodel bugs will be very few, this is something that we can test in-house fairly well. As for user bugs, yes - there is inevitably a large array of different systems and even more so different ways that users operate the airplane that reveal things not working as intended...so every major new release will be followed by collecting user feedback and rolling the resultant fixes into a short-term update.

That is actually very much "in progress" Graeme and I anticipate switching to that dataset asap. I wrote extensive nav data routines for parsing XP11 navadata quite a ways back in prep for this eventual port....so the heavy lifting is mostly done. It will look for the custom data if it exists (from Navigraph or Aerosoft...XP11 format), and if not present, defaults to Laminars dataset. I posted on it in the forum somewhere way back when where the left FMS was running with the XML dataset and the right FMS was running with the XP11 navadata format; however, at that juncture, it was only displaying procedural names from the parsed data, not loading anything into the flight plan. We have a 'de-coupled internal' format we use for the FMS data, whereby we read in the XML data and cast it into our own data structure...so in theory, I now only need to write the 'caster' between the XP format and our internal format and it should be mostly done. TBH, I'm hoping it will just work with minimal troubleshooting...so yea, we're right on the same page. -TomK

Here is why I think you should take all the time you need... Empirically, there seems to have been an exodus of developers and, I think you know why. Those who have chosen to stay on the X-Plane platform are excellent developers, IMO. Most of you (devs) have decided not to rush your products to market, but to take the time to redevelop your products so that me and others can get products that's realistic and take advantage of the XP12's characteristics. With that said, you (tkyler) and a short-list of other devs are expanding the envelope of what aircraft should be capable of in the sim. This is where I believe the X-Plane community will differentiate itself from the other sims. Developers who actually model those little things, and allow those little things to have a cascading effect, while maintaining the realism of the aircraft, will certainly make XP's aircraft THE best available. Simply put, XP12's aircraft needs (I don't like the word 'need') to be better. The aircraft should be the best. Your aircraft, I believe, will be among the best, if not THE best. So take all the time you need. I didn't mean to rant, but I am passionate about the horse I picked.

BN-2 updates are almost complete so those should be coming out soon. No exact ETA though.

I mean I'm already invested in whatever variants of the 737 Classic y'all come out with haha; I think most of the IXEG users will wait however long you'd need to get the 735 made. I've been missing the 734/735 from my fleet since the Wilco 737 PIC days. But I'm just one dude with a affinity for your 733 lol. Thanks for the response!

And I wouldn't be too bold in presuming we would see a regular -400 alongside the freighter if that were to happen in the future? I agree the -500 is sorta not work/reward equal but the -400 would be pretty nice to see

https://blog.x-plugins.com/2023/02/gizmo64-version-23.html

IANAL, so take this with a grain of salt: I'd say if you publish something that's completely your own work, but enhances the experience with one of LR's aircraft (like a livery, or a plugin (REP comes to mind)), then you probably don't need express permission from Laminar (since your work doesn't touch any of Laminar's intellectual property). If you however derive your work from theirs (e.g. modify an object file or tweak one of their xLua scripts) and want to redistribute that, you'd be on the safer side by asking for their permission - an EULA would probably give you the answer; ironically I couldn't find one for X-Plane...

Can't wait to have the 733 refreshed and back in action - it was my introduction to X-Plane and made a great first impression. I did my multi crew and jet orientation on a 737 Classic sim, and the IXEG brought back all those memories - even with XP10 visuals it was way better than the actual sim ;-) When you launched back in 2016 I was amazed at how well the sim captured that 737 experience. I can understand doing the XP12 compatibility first then moving to the FMS work later, and hope it comes together easily for you. Perhaps if the FMS is being reworked it would be good to move to the now standard Laminar navdata rather than using a custom set? I know this dataset didn't exist when the IXEG project started, but perhaps some of the edge cases in the nav code would be better handled with this format?

Thank you....you're not the only one to make this argument for obvious reasons!, and I'm in complete agreement. Hopefully "all the time I need" won't translate into "an extraordinary amount of time". I'm just happy to be working this stuff full time for a change. Thx again! -TomK

https://forums.x-pilot.com/forums/topic/22996-wow-even-without-a-proper-manual/?do=findComment&comment=181548

It already fully supports X-Plane 12.

Hi Rick, While the roadmap isn't certain, the current priority order is: X-Plane 12 updates for our existing aircraft (SR2X series, BN-2 Islanders, PR) CitationJet 525 TorqueSim Mooney M20R Realistically, the M20 is at soonest many months away.

I’m running X-plane -11 (version 11.55r2 - build 115501) and plugin Hot Start TBM 900 ( version 1.1.13) on a Windows 11 Alienware PC with RealSim G1000 10.4" PFD, 15" MFD, PROC GMA Audio Panel, GCU478, GFC500, TBM Switch Panel. When selecting “PROC” button on the RealSim GCU478 panel, it is not possible to select the airport identifier or desired approaches using the Alpha-Numeric section of the RealSim GCU478 panel. It is possible to select the approach using the on-screen Alpha-Numeric version of the GCU478 panel with a left-clicks of the mouse. All the hardware appears to be working since it is possible to enter flight plans using the RealSim GCU478 Alpha-Numeric panel. The DataRef tool shows the RealSim GCU478 buttons are mapped correctly ( i.e. appears and turns yellow when selected). The data value =”1” when depressed and “0” when released. Command Mapping.ini file shows for Example: the letter “K” [RealSimGear-GCU#5] BTN_K=sim/GPS/gcu478/K The on-screen button left mouse click is mapped to: tbm900/actuators/efis/mfd_keyboard_K. The keys on the GCU478 that are inactive after selecting “PROC” include: A,B,C,D,E,F,G,H,I,J,K,L,M,N,O,P,Q,R,S,T,U,V,W,X,Y,Z,1,2,3,4,5,6,7,8,9,0, ENT,SPC,BKSP. All of the above keys function in the flight plan enter mode. Is this a known bug? Is a patch available?

I figured it out. Bad graphics card!

Picky is what made it excellent. Looking forward to the updates.

I love that plane. I use to fly it a lot. Maybe I'll pull mine out of the hanger and get the carbon out of the cylinder heads. I enjoyed flying is so much that I got a second one.

Maybe someday it will be on your roadmap. X-Plane 12 could use B1900. I like the de icing fluid you added to the AFM M20. I hope you add this to all your small aircraft. So pilots are able to fly in Alaska in the winter time.

Outstanding job Ilias, can't wait!!! Also would be great an integration with the REALSIMGEAR G500 and G5 from the Torquesim guys in the virtual cockpit of the LES modern avionics DC3 variant, would be really awesome!!!

Thank you Ilias, this is great news indeed! I'd have been a happy customer of the classic alone, but I love a good retrofit, so that second model is the icing on the cake for me. I'm really looking forward to flying its wings off.

I see, and for sure I only got near stall because that MD11's aerodynamic back then is not fine tuned so I'll go stall even at proper VREF. But most add-on I have use is simply sync to hardware as soon as AT disconnect and any hardware input movement, so it's my second nature to match throttle before intentionally disconnect AT, on many add-on with EICAS display there it simply a "fake" indicator on engine display, for 733 without EICAS the "ghost" throttle UI is perfect for that. So.. maybe make it an option?

Speaking for bush flights, I've brought down 2 Beavers attempting to fly from Norway House Airport (CYNE) to Pas Airport (CYQD). My failure to do proper fuel calculations led to a ditching (the first time I was forced to make a water landing). I underestimated the headwinds I would encounter en route. The 2nd time, I was brought down by a bird strike. My virtual insurance company is not happy.

That sounds like you're using X-Plane 12. The IXEG 737 is only compatible with X-Plane 11.

I wouldn't be surprised to see anti-icing fluids modeled in XP12. However, I'm looking forward to seeing icing modeled first. XP12 already has rain effects. I hoping that will be followed by snow, ice, and the good de-icng effects. XP12 is in it's infancy. I flew the Donier 228 (the freeware version) a few times. I enjoyed it. My journey into the airliners will probably emulate real-world flying. I am considering buying the Dash Q4 800. I do own a couple of airplanes the are regional carriers. I hardly fly 'em. I'm planning to acquire the classic 737 when the new version drops. I have heard a lot of new sim pilots actually start with airliners. Thanks for the feedback on modding, @scooke7. I am gonna keep advocating for the mods.

Hi Rick, VirtualGAaviator I second this! I'd like to fly everyday too. But alas, time seems to be my enemy! I fly heavies all the time, at this point it's all Boeing aircraft. And for now it's the Zibo B737 on XP11. When XP12 settles down (will take 6 months, IMHO), I'll try out the A330 for medium haul. I've seen the Citation X on XP12. I'll probably try that as well. It sounds like a fun aircraft to fly. On the modding, I don't think you need permission from LR. I've seen folks just pushing out mods for other aircraft in the other place. The Zibo B737 & Soarky B744 are just 2 that come to mind. I think it becomes complicated if you want to charge for modding. Either way, I don't think it hurts to get an official line from LR that clears the way for modding aircraft. I think they might even provide extra information that might prove to be useful when modding. Steve

Those are all good points and should be addressed Graeme. Bleed air for several things passes through the AC system...so I have to dig a bit deeper into that switchgear and I suspect this will get addressed when I did into that. I plan to incrementely improve the systems once the IXEG/MU2 are ported to V12 in their current forms. As usual, I've added this to my tracking list. Though it seems quiet here, I'm rolling full steam on XP still...the Moo just has to wait for its rotation across my desktop -Tom

I think this version does it. After installing the ToLiss A319 I had to run X-Plane 12 under Rosetta (Interpreter for Intel-Code on ARM-Macs), because the ToLiss Airplanes aren't ready for ARM yet. This broke the install with the 'lipo'-trick. I installed your build from above and it works just fine. Manually allowing the execution is, of course, still required.

Hello Captains! We are happy to announce that our Beechcraft C23 Sundowner, soon will be available for X-Plane 12! This is not a simple patch to make Sundowner X-Plane 12 compatible, but a serious upgrade with many improvements, and additions! The version that is already in the store, includes 2 versions of the aircraft, the original version, and upgraded version with Garmin's G5 avionics. The new Sundowner adds 2 more versions, for a total of 4! One with the Garmin G500, and one with Garmin 1000 avionics! Those upgrades are not simple instruments swapping, but go deep into aircraft's systems, like the electrical, which now includes all circuits breakers to be operational! Here is a feature list with all the major items: X-Plane 12 (only) compatible. Support for the full X-Plane 12 run. X-Plane 12 flight model integration, which includes: a. Flight model adjustments for correct aircraft performance. b. X-Plane 12 new weight and balance model. You can adjust the weight of each seat occupant, through X-Plane's UI. c. Yaw trim tab adjustment, for neutral rudder input at cruise. Four aircraft models, with unique panel layout, and operation. a. The original C23 Sundowner. b. C23 Sundowner with G5 Instruments (requires the RealSimGear G5 Instruments from X-Aviation store). c. C23 Sundowner with G500 Avionics Suite (requires the RealSimGear G500 Avionics Suite from X-Aviation store). d. C23 Sundowner with X-Plane's G1000 Avionics Suite. X-Plane 12 windscreen rain effects, and defrost control. Full use of X-Plane 12 lighting system. All circuit breaker are operational. Fully simulated AMR-350 TSO audio panel, for the original, G5, and G500 models. For the G1000 version, extended simulation of the GMA 1347 audio panel. All models simulate the use of headphones. Integration of Libradio, for true to life COM and NAV reception. Credits to @skiselkov. Controls and displays for COM and NAV radios, individualized per model. For the original model, G5, and G500, COM1 and NAV1 are controlled via the GNS430 head unit, and COM2 and NAV2 via the radio stack units. a. The original model has a button between CDI and DME indicators to switch sources between VOR1 and VOR2. Pressing the CDI button on the GNS430, source becomes the GPS. b. In the G5 model, NAV1 drives the G5 HSI, and NAV2 the CDI and DME indicators. c. For the G500 model, all NAV indications are displayed on the G500 PFD. New tablet location. Now stored under the panel, on the right side, and displayed on pilot's yoke. I think it's time for some images! Here you go!

Thank you for the kind words Ian. We are certainly excited to be working on the IXEG again. On the one hand, the initial port to XP 12 is a bit more labor intensive than anticipated...but on the other hand...getting everything ported to modern workflows and features is ceratinly a welcome change on our end, ensuring less development pain once we get this initial infrastructure change done. -TomK

I foresee two 'events' with regards to the 733. Event 1 is "port to XP12 'as is'. Event 2 is 'upgrades beyond the port'. The goal of event 1 is to get it to work in XP12 the way it does in XP11 given XPlane changes. Those who have made 733 purchases since early this year will certainly get the XP12 port version for free as stated on the XA product page. Beyond that XP12 port though, we have not made any determinations about what may or may not constitute a 'paid upgrade' beyond the fact that it shouldn't be egregious or outlandish. Regarding features 'beyond the xp12 port'... we have and hear arugments all the time for/against variants, cargo versions, etc and have not made up our minds yet about what may be next. The obvious things todo are the FMS work and upgrading all the 3D/textures/animations. As far as MSFS, a lot of us developers have kept an eye out on the whole market/dev process and a port is not a trivial thing, regardless of what Fenix / inisim is doing. We're talking multiple 1000s of man hours easily, and at my age and road traveled, that's a tall order.....regardless of the money potential. I rather enjoy my little world in X-Plane and those users who also see the same value in it. Perhaps Fenix, iniSim or someone else can do a 737-300. I can't speak for any other devs in the X-Aviation ecosystem, but for our part, we'll probably stick to X-plane with the 733...best I can tell from today. -TomK

Hi, is it possible to deselect a previously selected SID/STAR. Once the RWY and PROC have been selected, I can change them - but not deselect/deactivate them. Only way is to delete the individual way-points in the LEGS page. Is this by design of the ProLine system, or do I miss something. TNX Xaver

If this is such a huge focus for you (you've mentioned doors multiple times now), you were never really the target customer for IXEG anyhow. Hate to say that, but it's true.

Please elaborate Cameron. I'm not trying to start an argument with you, I'm trying to make a point to you and others, and it seems to be getting misunderstood. What, exactly, do you think I'm not understanding? Allow me to reiterate, what I'm asking for is a manual/user guide like the one that came with the TBM 900.(and most other payware aircraft that I've purchased) Something that would have shown me exactly where the pitch sync button was located, or where the ATS disconnect buttons are located, recommended button/key bindings etc. Thanks in advance.

I'm talking about a manual written by the developer, like the one that comes with the TBM900. I'm not talking about the actual Bombardier manual.

I know that's cheating but maybe "Realignment IRUs Immediately" works? It sounds like that might happen in the real world as well. My wild guess is that one way (in the real world) would be to tow/taxi the plane to an area that's better protected from winds (e.g. into a hangar, maybe a runup area with blast shields would also be sufficient?). I've never tried if X-Plane simulates objects shielding from wind though (and it might just not do it, it's usually not important to simulate that), so maybe the "cheat" is the only option. As an afterthought... If X-Plane does not simulate wind shielding inside hangars etc. we can still control the winds within the simulation. So to simulate shielding from strong winds e.g. inside a hangar it would be possible to temporarily override the winds to be calm in ASXP and restore live weather after the alignment has finished.

Documents last updated 20th December 2022 1128340285_CL650FMSPrimer.pdf CL650 Operations Reference.pdf 1323904309_CL650ExpandedNormalProcedures.pdf CL650 Checklists.pdf CL650 Checklists - Printable.pdf CL650 Flexible Take-Off.pdf CL650 Shared Cockpit Quick Start Guide.pdf

Ah, so if you're finished with the ATS you need to press the ATS disconnect button. The binding is CL650 \ pedestal \ throttle \ auto-throttle disconnect.

When the APU encounters a fault, you'll need to hop out of the plane and reset the APU ECU to clear the fault. Go to the tail of the aircraft near the cargo door, pop the latches and pull the little door open under the left engine nacelle: Inside you'll find a panel with 3 buttons. Push the "RESET" button, close it up and you should be good:

On the M20 Ovation II there is an anti icing panel that shows "0.0" of anti icing fluid. Is there any documentation how to fill and operate the anti icing ? Bodo Edit: more precisely its a M20 Ovation II with G5 , see ice protection below the ANALOGE (not the G5) turn indicator