Leaderboard

As for features left in or left out. I'll fly this bird without the computer. I carry my own.

You can solve that descent with full flaps, gear down and spoilers full

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

Nice video and great job with the airports..

New video.. nice!

Amazing! I might have to steal your flight plan instead of my original one. I'll definitely be doing a lot of SWA and Alaska Airlines though......it's so frustrating I can never fly any of their routes in X-Plane! The IXEG 733 will change all of that...

You said you were beta testing the FMC, but clearly its not included in V1. I smell rat a

well here's a little report, just so you know we're not sitting around doing nothing. We are polishing up lots of little corners many won't see. As I said, the reason we are doing so is not a matter of pursuing perfection, but rather is because when you put this in thousands of hands, they will find these issues and if they cause crashes, that is no bueno as we like to say here in San Antonio TX. So today, I was addressing parts of the N1 limit page, for derate stuffs. So here's a CDU entry pattern you probably don't see much. Say you select "TO-1" derate....that will automatically select the "CLB-1" derate mode (so the throttles do not advance in the transition from Takeoff to climb phase....Boeing says that confuses the pilot dontcha know eh?). And then lets say you enter a assumed Temperature value....well depending on the temperature entered, that too might automatically derate the CLB thrust, not only to CLB-1 mode, but maybe CLB-2 if its hot enough......so far so good. But then lets say you decide to delete the TO-1 mode....well the CLB thrust mode may or may not revert to one of the reduced mode..... or not dependent on the assumed temperature entered.....and there are a myriad of other potential combos that may or may not get entered. Here's a little video to show several different combinations that have to be tested....and there are quite a few more patterns other than what is shown here. https://dl.dropboxusercontent.com/u/955680/n1_limitOPT.mp4

I'm just excited for the 737.

In the middle of bug fixing I had to spend a little time repainting OK-UBA with citywing livery

Well in the video Jan did the SWA livery is N654SW. So I will spend my first day doing what the real aircraft is doing. As an example N654SW's routing tomorrow 2016-03-16 WN4472 Phoenix (PHX) Little Rock (LIT) 17:20 PM MST - 21:45 PM CDT Estimated departure. 17:30 PM 2016-03-16 WN3027 Austin (AUS) Phoenix (PHX) 16:05 PM CDT - 16:40 PM MST Estimated departure. 16:15 PM 2016-03-16 WN3027 Dallas (DAL) Austin (AUS) 14:35 PM CDT - 15:30 PM CDT Estimated departure. 14:45 PM 2016-03-16 WN28 Houston (HOU) Dallas (DAL) 13:00 PM CDT - 14:00 PM CDT Estimated departure. 13:10 PM 2016-03-16 WN17 Dallas (DAL) Houston (HOU) 11:00 AM CDT - 12:05 PM CDT Estimated departure. 11:10 AM 2016-03-16 WN373 Austin (AUS) Dallas (DAL) 09:25 AM CDT - 10:25 AM CDT Estimated departure. 09:35 AM 2016-03-16 WN372 Dallas (DAL) Austin (AUS) 08:00 AM CDT - 08:55 AM CDT Estimated departure. 08:10 AM

Release 1.0 is closing... This is the point where I say "stop" for v1.0. You never really can finish a plane. Still, there are awful lots of things to do. But let's leave those for v2.0 So what we have so far: Quite realistic engine and flight model (~95% matching real data) Instrument lighting Yoke can be hidden Basic anti and de-ice system Custom engine sounds Custom engine startup Checklist for XCheclist Wunderbaum and many more which is up to you to find out All basic instruments are working, you can either fly RNAV with Garmin or NON-RNAV (VOR2VOR) flights with the NAV instruments. Did several flights on IVAO lately to check out if I missed something, but seems like all are there. Of course, I'll keep working on this beauty Despite I put a lots of effort to this plane, v1.0 will remain freeware. That's not going to change. Ever. Bugfixes of course will come after release, so I'll keep updating this version. But in the meantime I start working on v2.0 which going to be payware. But that's really the far-ish future, so I don't want to get ahead of myself yet. Here are the latest shots, hope you like it.

Looks like a good one for the classic North Atlantic route - via Gander to Shannon. So bad weather practicing already included on the route home

I love the idea! Jan

KBFI/KSFO A true first flight comes from boeing field.

There's no winning here. I have seen SO many complaints on X-Plane related groups about all the beta shots going out for the x737 and lack of release. We are not going to start doing this. At some point you have to realize the aircraft still looks as has already been shown. Short answer: won't be happening at this stage!

Any new update? Sooner or later you will be released this aircraft? are almost six years that we follow you, and I start to lose hope. I understand marketing, but you're on the thin line of the joke to your potential customers.