Recommended Posts

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.0, 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

Operating doors (passenger, service, cargo) - omitted due to time constraints, definitely planning to add later

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.

Wingflex - not added because its a lot of effort and the real wings don´t flex much. Might be added at a later stage, dependent on user feedback

Fully fleshed out galleys and cabin interior. Omitted due to time constraints, definitely planning to add later. For now a basic, low-res placeholder 3D cabin is in place.

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 interaction. Omitted due to time constraints. Planning to have basic interaction, for opening doors, for example. Need to get sound-samples first, basic infrastructure in place, 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 user created waypoints (point-bearing-distance, for example) and using those in the flight-plan. Omitted due to time constraints, definitely planning to add later.

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.

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.

No mousewheel scroll support for turning knobs. We are pretty happy with the click-hold and drag system, but if user demand is strong, we might add mousewheel scroll support later on.

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.

Flight attendant panel 1L. Including cabin light switches, ground service switch. Omitted due to time constraints, definitely planning to add later. The ground service switch can be "moved" through a sidebar menu.

Operating CB´s. We decided that most CB´s 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.)

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

Edited February 17 by Mortenbringing list up to date as of Version 1.2 and 1st of January 2018

Share this post

Link to post

Share on other sites

This list is highly appreciated, and I don't see it as a degradation of the initial release in any way. I think that most of us will be more than happy to fly this beauty asap, instead of waiting another X years for features that are just "nice to have" or which are rarely used.

Share this post

Link to post

Share on other sites

Good to know. Once the main bulk is out and working then the timing of the next versions will be better on your part. As i say all the time, well done and i cannot wait to buy and use this aircraft. The later updates after V1.0 will be great, but for now i am more than happy with whats going to be released in V1.0.

Share this post

Link to post

Share on other sites

Operating CB´s. We decided that most CB´s 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!).

Yah, give the hard-working woodpecker a break. Very good!

Edited December 7, 2015 by frumpy

Share this post

Link to post

Share on other sites

Nice to see a bunch of mature, down-to-earth developers, who strongly believe in customer relations and transparency. As fellow simmers and former customers of other developers it's clear you guys have witnessed first hand how NOT to release a complex airplane, and are going above and beyond to make sure your customers don't get caught the same way. No half-finish a plane, grab the cash and run off to develop another here!

I doff my hat to you gents, you will definitely have my sale on day one!

Share this post

Link to post

Share on other sites

I concur with your opinion about getting it right or not doing it at all. I have never seen a pilot in any flightsim that didn't look stupid in one or the other way. Same goes for the scrollwheel support that I've seen so far - too many tradeoffs. There are often "features" that you get tired of after a week because they actually add nothing except an "ohh, nice".However, all the best for the initial release!

Flo

1

Share this post

Link to post

Share on other sites

I concur with your opinion about getting it right or not doing it at all. I have never seen a pilot in any flightsim that didn't look stupid in one or the other way. Same goes for the scrollwheel support that I've seen so far - too many tradeoffs. There are often "features" that you get tired of after a week because they actually add nothing except an "ohh, nice".

However, all the best for the initial release!

Flo

Well, one thing that always seems to work is some well-endowed female copilot - no matter how bad the 3D-model might be, the male mind seems to glaze over the shortcomings with the power of imagination... .

Share this post

Link to post

Share on other sites

Awesome list!!! Finally a developer that does this, very welcome indeed!! Question about the descent wind forecast. I noticed that there was no status on it, whether you plan on implementing it later on or not?

Share this post

Link to post

Share on other sites

Awesome list!!! Finally a developer that does this, very welcome indeed!! Question about the descent wind forecast. I noticed that there was no status on it, whether you plan on implementing it later on or not?

Undecided - it is likely that we make the page "operational", so you can enter something. We have to see if its worth adding the data into the calculation, though. X-Plane only offers 3 wind levels (iirc) natively. Even if you have a more advanced weather "injector" in the future, chances are that users will have no way of knowing what the wind during the descent will be - so how can they enter it accurately? If they enter data that doesn´t reflect the reality, then the whole descent calculation will get messed up.

We currently envision to take cruise wind into account to recalculate the descent when you approach the pre-calculated ToD. This is also what the real FMS does if you don´t enter a descent forecast (few real pilots ever do...). The FMS assumes a " wind correction factor" for the descent - since the wind speeds usually get slower the lower you get, this corresponds with your TAS getting slower, the lower you get. So if you have a 20% tailwind speed increase, this 20% factor can be applied to the whole descent "angle".

In reality, very few descents can be flown "idle" power as calculated. The real atmosphere is just too unpredictable, and even a 10kt unexpected headwind will make you come up short 3-4 miles, unless you add power (which the A/T will do for you in a VNAV PTH descent if you get too slow).

The real FMS also has a problem with the "wind-shift" factor. Let´s say you enter a strong layer of headwind. In the long run, this will make your idle-power descent "steeper". The FMS adjusts for that during descent planning, if you enter the wind into the descent forecast page. But as you ENTER the wind layer, initially your IAS will increase (positive windshear). This initial shear is not planned for and surprised the FMS. It assumes that it will need to descend steeper (due to the headwind), but suddently finds that the airspeed increases unexpectedly! This will often cause you to be forced out of VNAV (as the speed gets above the allowed speed error).

So in conclusion, VNAV is not the magic bullet and the FMS isn´t almighty or omniescent. It is a 80´s computer facing a very complex and dynamic reality, and while its a great helper, it has it´s limitations.

Share this post

Link to post

Share on other sites

Actually, I was flying home in a 737-800 and the airplane was landing in a wind of 24 knots and quite much turbulence at the ride down to the runway. I was sitting behind the wings, and watched the wingtips vibrating violently. It was a very nasty experience, and I have not imagined how violently wingtips may vibrate in turbulence. I have big regrets I did not tape it.

Wingflex - not added because its a lot of effort and the real wings don´t flex much. Might be added at a later stage, dependent on user feedback