Leaderboard

Captains, Firstly, we'd like to express our gratitude for your recent upgrade purchases. This week has been bustling with activity, as we’ve endeavored to respond to inquiries and meet the high demand for support. Level-2 Failure - Fixed! It quickly came to our attention that a number of our customers encountered a Level-2 failure, which restricted the aircraft's systems from functioning at all. We deeply regret any inconvenience this may have caused and assure you we've been working diligently to identify and rectify the problem. While we strive for perfection, it's an unfortunate reality that despite thorough internal testing, unforeseen issues can arise when a product reaches a wider audience. This particular setback wasn't evident during our beta testing but manifested for some once released. The good news is that we've isolated the cause and have promptly deployed a patch. To access it, please re-install the IXEG 737 Classic Plus from your order history. Didn't have Level-2 Failure? For those unaffected by this issue, there’s no immediate need to update. You can comfortably continue using the aircraft and await our next scheduled update for other enhancements. We truly appreciate the patience and understanding shown by many of you during this period. Thank you once again for your continued trust and support. Blue Skies, X-Aviation & IXEG

XP 12 IXEG 737 Classic until Cargo variant is made available.

@fortinworkaround....put two waypoints in the LEGS page at minimum before executing.....that should get you past the error.....then after you get airborne, you can put MIGLO into the first line and execute if that was your intended plan (one waypoint only). Looked like the crash happens when running a VNAV calc with only one waypoint in the legs page. Already fixed for next patch. TK

@AngelOfAttack I have identified and fixed the reason for the weird pitch during takeoff and landing. It will be fixed in the next version, so dont get too used to the effect ;-)

After few more flight I can say the rotation (both TO and LD) issue is the most annoying one, even the LVII bug I can get around, and all other bugs I can make a flight condition that get avoid, but only this one.... even with anticipation, the muscle memory on my home setting is hard to replace, explically when all other flight going smoothly so I almost forget these 2 kinks.

Thx for rerporting. I put it on my list this morning to check.

@Cameron Update doesn't work for me see my post please https://forums.x-pilot.com/forums/topic/27190-ixeg-no-power/?do=findComment&comment=195360

You are right, I can see it with the "front galley lights" being on! I think it is an artifact of X-Plane´s lighting engine resolution, lights that are further away will have less resolution when it comes to their lighting effects to save on rendering performance (kind of like the shadows do, too). I think the ultimate goal her is to emulate the cockpit door and rear wall being really opaque...so that there is no lighting from the cabin if the door is open (in the real airplane the galley lights go dim when the cockpit door is open).

Hi axmiha, I thought you were talking about the screen itself - but the keys should have backlighting that comes up with the center pedestal rheostat, which they don´t! So thank you for reporting that! That "phong" you see is not showing on my screen, but I have seen something like that before, I think it may depend on graphics card settings/driver/anti-aliasing?

the patch has been made and is being tested with select folks. Several testers have confirmed its fixed their issue thus far. It may still be a day or so as there are other precautions to be made.... and we don't want a 2nd occurrence to happen. Much better to take a day or two to make sure its good and get this one totally behind us. As to the unfortunate timing..see recommended post at top of this page if you haven't already. it explains the weekend thing. -TK

Updated September 2023, Version 1.5 Hi everyone. While it seems to be the economically "smart" thing to do to NOT talk about the shortcomings of your product (and then sometimes to just ignore the complaints after you cash in the money), we are trying to run things a bit differently here at IXEG. I would therefore like to share a list of things that will NOT be in version 1.5, and also give a little background of why, and wether we are planning to add it later. I will try to make this list as encompassing as possible, if I forget something, please don´t sue me! I will add/remove from this list as warranted. Aircraft visual 3D model Ancilliary vehicles (catering, fuel truck, loading crew) - this is now accomplished by using the XP11 native ground vehicles, the docking locations for those are correctly added in planemaker. Cockpit keypad entry mechanism Omitted due to security reasons. Deployable emergency slides.Omitted due to time constraints, planning to add later. Deploying oxygen masks. Omitted due to time constraints, planning to add later. Sound effects/visual model for passengers and their (assumed) behaviour. Too complex a simulation off it´s own, most likely won´t be added for fear of having something repetitive or cheesy. Cabin crew voice interaction. You can communicate via menues that are invoked by pressing the cabin call button, though. FMS Pilot entered HOLDS. While we have database-inherent holds (like at the end of a missed approach), we won´t feature the HOLD page where you could enter all sorts of HOLDS. Omitted due to time constraints, definitely planning to add later. RTA feature. Omitted due to time constraints, planning to add later, but low priority. OFFSET feature. Omitted due to time constraints,planning to add later, but low priority. ABEAM points (after shortcutting route, for example). Omitted due to time constraints, definitely planning to add later. You CAN enter stuff in the FIX page, and "find" a PBD point that way (enter a fix, enter a radial and a distance to see the green radial and distance-circle) Entering descent wind forecast (normal wind entry on PERF INIT page possible). Display of "RTE DATA" on EHSI/map, i.e. showing ETA and restrictions next to waypoint. You can see that on the LEGS page, for now. Omitted due to time constraints, definitely planning to add later. Automatic entry of performance data (weight, etc.). We might include that for the "ready to fly" scenario, not decided yet. For now it must be entered manually, if FMS performance assistance is desired (not mandatory). Fully working PROGRESS page - we started to code it, but much of the things shown are placeholders. We expect this to be one of the first things we will add soon after release. Full VNAV functionality for descents with speed and/or altitude restrictions. The FMS gets confused by changing the cruising altitude while enroute and multiple descent restrictions and restrictions of a certain type. Basic unrestricted descents work, though. GUI Dedicated flight-planning software. We feel that this is not necessarily within the scope of our add-on. We model the plane like you get it after delivery from Seattle (+ free lifetime fuel!). There are plenty of flight-planning solutions out there, we include a basic "ballpark" fuel calculator. Complex and visually appealing load+trim software. We feel that clicking empty seats to fill them and pulling sliders to load cargo is fun for a few times - but really all you get is a weight and a center of gravity. And you might just as well set those directly in the gui. We have simple sliders and click-buttons for that (or you can use the default X-Plane menus). No way to output any CDU, EADI or EHSI onto an external device like iPad or such. Would like to have that (especially for cockpit builders), though. Exception: it is possible to use AirFMC, available at the Apple App Store. No pop-out 2D displays of flight instruments/CDU/EFIS to make reading or entering stuff easier, no hiding of yoke to not obscure view. We feel that the ergonomics (or lack of) an airliner cockpit is an important part of the experience, so we don´t want to "help" too much. We have "preview pop-ups" of the EHSI when making changes on the EFIS control panel to help you see if you have the right setup. Other systems Wxr radar returns can only be displayed on the left EHSI/map. Omitted due to time constraints, definitely planning to add later. Terrain colour display can only be shown on the left EHSI(map. Omitted due to time constraints, definitely planning to add later. Operating circuit breaker (CB). We decided that most CBs will never be moved in normal operation. We will add moveable CBs with the yellow collar later (to be used in abnormal situations), and possibly some others as well (standby altimeter vibrator!). Automatic startup/shutdown "macros". Won´t add that. This plane is about realistic operation (it´s not hard!). If not desired, just select "ready to fly" or "turnaround-state". IRS using "false" position. It is not possible to deliberately enter a "false" position and have the IRS align to that. The entry will be rejected unless reasonably close to the real position. In the real plane the GPS would also "correct" your wrong entry (if close enough) or warn you. A position far from the old "shutdown" position would be rejected once. A wrong latitude would be detected during the alignment process...It would be a lot of coding effort to maintain a "wrong" position with the corresponding effects (map-shift, etc.) A dedicated way to fly the same plane together in multiplayer. Note that SmartCopilot has made great progress in making our plane flyable with a crew of 2, and while not perfect yet, it is working very well, going by user reports: http://forums.x-pilot.com/forums/topic/9714-smartcopilot-first-attempt/?page=1 Volume control for radios/navaid ident checking. We have implemented a better volume (more loud), but it can not be adjusted yet. We are trying to be as upfront about the shortcomings of our model as possible. I have myself bought many aircraft for flight-simulations boasting great things, only to be disappointed. I want to avoid that for everyone, so if you find a "must have" feature on this list, I encourage you to hold off on purchase until we added your feature in a later patch. I could make a feature list of things we have that would take you hours to read, but instead you can assume that our plane can do everything that the real one does, except for the things noted above. Cheers, Jan

I've just tested the fix, a short hop between Porto and Faro, with no issues to point out, besides the already reported bugs. I'm thankful to IXEG team for bringing my favorite 737 to XP12!

Thank you Litjan, No worries, thank you for looking into this. I'm still enjoying the plane regardless of the texture resolution. Regards, Chip

Thanks for fixing !

fixed. I had a '>' instead of a ">=" DOH...tk

Did my first full flight, and here is what I have observed, I'm a NG/MAX instructor but never on classic so don't hold much credit then.... Taxi: Seems need a lot power to get moving, over 40% is quite high IMO but not sure if it's true on these old engines. T/O: I made a improved climb with BPS data, the runway is almost gone, 15% of margin seems about correct (maybe a little short, and I'm using ATM it should have more margin then). However the rotate feels very nose light and I almost feel I have a tail strike (if it's on -800) CLB: climb rate seems right, seeing the record about 10nm/2min longer than FPPM data, good enough. CRZ: Compare to realworld cruise table, the N1 and FF is almost spot on! DES: VNAV actually works mostly fine, and the descent rate matches FCTM data quite nicely. On final N1 and pitch all looking good. Flare: In contract to T/O, the nose is very heavy, kinda like most airliner port to XP12 or XP11 EFM without proper adjustment...(for example some A350 is almost unable to flare...) Landing roll: Factor out my short flare distance, the landing roll distance is almost the same as the number I got from realworld data with Autobrake1, very impressive! Over all, it feels believable and could flown by the book, The main problem seems with in XP12's new ground effect scope, feel both noes light on TO and nose heavy on landing (weird). and also maybe engine is a little bit under powered? I mean I'd love to have 22K engine then...but compare to 20K data it still feel a little bit short. I might push it harder to test it against the "Flight With Unreliable Airspeed/Turbulent Air Penetration" chart! Not many high-end add-ons can pass that!

One of my biggest pet peeves many developers don’t get right in simulating their aircraft. I really enjoy the 737-300, but the auto throttle wandering at cruise is so obnoxious with the throttles constantly wandering from 70% to max cruise N1, not to mention it makes using fuel calculations difficult as you don’t have a very steady fuel flow. Real autothrottles don’t do this. One of the things real engineers do to prevent autothrottle wandering is to code the throttle adjustments at cruise in relation to accelerations/decelerations sensed by the INS, NOT from an airspeed indication as airspeed indications can be too erratic. For example, if you’re using a PD controller with tied to airspeed error and airspeed rate, the erratic fluctuations of airspeed rate will mess with the algorithm where as a more stable rate input such as ground speed would be better to prevent over/undershoots of the autothrottle. I am by no means an expert in programming or aircraft engineering, but I’ve definitely seen the autothrottle wandering not be an issue with many of the 3rd party aircraft for X-Plane for a similar price point as the IXEG. Please consider fixing this issue, and help bring the plane from very good to great.

Thx for reporting and your patience. We've added it to the list. We won't cease working on the IXEG and will certainly endeavor to increase accuracy in all areas, including this one. Now that we have the 737 out....we have to stabilize a few super obvoius oversights...but after, we'll enter a quite long phase of tweaking all those perf issues while we tackle our other roadmap items as well. -TomK

The patch has fixed my system and Living Scenery Techology now works with IXEG 737

I'm not aware of any flags to add to the executable to disable the ATC, but this could also be a red herring. Also, some notes: There are some VK_ERROR_OUT_OF_DEVICE_MEMORY, but most important my fellow rohirrim, update your nvidia driver. You're using the Driver from end of June (536.40). The most current one is 537.34! So, you should update your driver, strip of any add-ons and slowly but surely try to trigger the crash while adding one by one the add-ons besides IXEG.

..oh noooo ,thanks Jan and Jude ,my mistake ,i turned the upper knob of the HSI That's the problem when you don't fly a plane like that often enough

No complaints on the sound front from here... all sound quite authentic and believable and adds a lot to the experience.

Move that window, it need to uninstall the existing and that is being hidden by that window. Alloying buts thats all it is. Youll need to click ok.

This morning after applying update, same problem , Level2-FAIL. I download from my account IXEG_737_Classic_Plus_1.5.zip I unzip this file I run IXEG737CP-windows-x64-installer.exe Installer uninstall previous version installer install new version Launch XP12 flight with Ixeg737-300 Ask for licence Set preference Set START STATE to Cold an Dark , APPLY SETTINGS No Power , No sound. Exit XP12 and launch a new flight as above, same problem. I remark that installer (IXEG737CP-windows-x64-installer.exe) from today has exactly same timestamp and size as the one uploaded on Saturday morning. Is it normal ? Log.txt

Good enough. Thanks. I thought the "phong" thing because I sometimes forget and get that in some models, which is a pain in the arse. Awaiting the wipers, then. Funny that I almost never use the wipers, but now that the plane is out, it's raining everywhere I go! Followed your instructions and managed a much better landing, but still, as soon as I touch down, the nose goes down and bangs on the runway really quick. Do you cut the power completely off around 10f or something? Or just after touching down? I see guys cutting off around 30 or 20. Maybe I'm coming in too slow, already at ref speed before touch down. But I'll get there.

Thanks - I hadn't seen that link so that's useful info to know. Re. crashing, see above. I will post the log.txt when I know what combo is causing it.

I followed your advice in a recent post and disabled all plugins apart from Gizmo and admin and, apart from one crash, things have definitely improved. I am currently in the process of adding plugins back in. I suspect it's Lua but I don't actually have any Lua scripts enabled and running out of device memory on a 4090 is a bit of worry! I'll attach a log once it crashes again.

Could be, I'll check. Did you check at night with the cabin lights? I think it depends on some angle the light comes in. But it's no big deal, whatever it is. You guys have bigger birds to land (as in "bigger fish to fry"). Thanks for the reply.

Rider of Rohan, take a look again in case of a crash, x-plane is showing that an extra log, atc related, is also being generated that may show the root of the crash.

Yes, that's accurate. This particular update was solely focused on resolving the Level 2 failure error due to its critical nature. Any additional enhancements and fixes are planned for upcoming releases. We appreciate your understanding and patience.

Got my discount code this morning and bought the Classic Plus right away. I just wanted to say "wow!". It's really looking good and I look forward to fly it later this week, when time permits. Great stuff! Now I can retire XP11

As @Pils mentioned above, email/forum post from X-Aviation is the 'official' way. Soon though, we'll be putting up web based info, similar to the MU2...and the version listed at the top will be the most current version released. We won't change that version # until the actual release. Usually we synchronize updating the online info with the release itself, its part of our deploy checklist. So if you wake up one day, wondering if you've missed a release, you can check your version in X-Plane (use the 'Customize' button inside X-Plane to see the version)...and compare that against the version listed at the top of the (soon to be posted) docs. It will look like so when posted: So the current version listed inside X-Plane is now "1.5"....and that screenshot above shows what it will be when we make the next release and this info is put online. So just another way of checking versions. -Tom

Works fine on my end...

Hey Morten, great to see you chime in! I will take this up with Austin in a little bit, right now we are on his case to fix the too rapid N2 rise after fuel is injected. You know him, it is better to feed him stuff one after the other ;-) All the best, Jan

Hi guy's, been a long time Regarding rotate feeling light, this is mostly an XP issue (at least in XP11 that i knew well). In short, the 737 has a supercritical airfoil (NASA term, or "aft loaded" airfoil as Boeing calls it). One of the differences between conventional and aft loaded airfoils is (as the name implies) that the aft loaded airfoils have the center of pressure further aft. Meaning also the center of lift is further aft than on a conventional airfoil. XP does not model this very well, and as far as I know has its center of lift at the 1/4 chord. So this means XP airliners have their center of lift too far in front which cause problems in the transition phase between ground and flight. Should be a fairly simple fix for Austin. There are some temporary "hacks" one can do, but it's a can of worms... Good to see the old girl in the XP12 skies - great work Jan and Tom

Thanks for testing this, Jude. Let´s see what Tom can find out!

I dont think you understand how the skunkcraft updater works, it looks for altersd, missing and updated files, and only replaces deletes as necessary. Means you may only need to download 300 meg for an update than the full 1.5gb. Its far more efficient especially for those on low bandwidths. But it means your tied to another developer and another cost. No reason why Gizmo couldnt do the same thing.

Please do so - it is what I have used to tune performance ;-) I agree on the ground effect thing - it does strike us seemingly more than the default 737-800, might be a geometry thing. If I make the nose more "heavy" on rotation you would be unable to pull it past 10 degrees until out of the ground effect - the landings one can get used to, but you need to be ready for the nose wanting to drop (more than on the real aircraft). I might take this up with Austin, but got him busy on the N2 acceleration during engine start for now ;-) Try taxiing again on a verifiably flat area - I find that even a bit of slope plays a huge role. The 737 starts rolling on my side at idle power up to 50 tons of weight, as it should. Cheers, Jan

HI, I went through the liveries and various searches and could not find a house livery for the IXEG B737. If it isn't out there, maybe some talented painter can make one. Thanks.

Three weeks later, I'm now (virtually) in Jakarta, Indonesia. As planned, I flew the Moo via Kathmandu (VMKT) and Paro (VQPR), and then on to Lilabari (VELR), Momeik (VYMO) and Thandwe (VYTD): From Myanmar I had to fly a deadhead leg and relocated to Bangkok (VTBS). Not the best weather down there currently... Yesterday I started moving further south, delivering a well-paying VIP transport job to Jakarta. Due to time zoning, it was an all-night flight. The distance of more than 1,200NM was quite a stretch for the Moo, so I made a fuel stop at Kota Bharu (WMKC). Arriving in Jakarta, I was greeted by a thunderstorm, surrealistically lighting up the city (on final into Halim Perdanakusuma, WIHH): The next assignment will indeed take me again further south to Australia - got a bunch of VIPs headed from Jakarta to Paraburdoo (YPBO). Again that leg is too much of a stretch for the Moo (at least when observing legal reserves and some margin for weather), so I'm planning to fly this with another fuel stop - hoping to meet Santa on Christmas Island (YPXM)...

Thanks for your response. A Royal Australian Air Force Livery would be great. I have purchased it albeit pension week is still a week away but I like the vintage aircraft being an ex RAAF member myself