Leaderboard

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

Core i5 2500k running at 4.0Ghz. Geforce GTX 970. Recording with FRAPS. Cheers, Jan

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

What plane/livery is this? I know it's not mine... I only made one because I couldn't find an Aloha one. I don't know if the HD liveries work with XP9 but I've uploaded an HD version with corrected colours and a better tailfin emblem. Also, XP9 is still a pretty sweet version, I have it installed still and occasionally open it up because I haven't bothered transferring all my scenery and aircraft to XP10. XP10 is just for development for me, XP9 is for fun and flying. PS - never mind! I just noticed the extra windows over the cockpit, this is -700 from XPFW... sorry

OK! I checked the MEL list and all that stuff Jan posted are not includuded in it!, so the status for this release flight is GO! Thanks a lot Jan, mostly of things are 'visual,' they don't really affect the fidelity of a realistic flight simulation, so I think we can all live without them for the moment, I like to follow the procedures, so I don't care if I don't have a 3D pilot or wing flex, but what I do like is to have a 95% of features of the real aircraft.

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.

Behind enemy lines! Thats better!

Almost every time now I read a post from you, that has something to do with "release" it makes me more happy, you're talking like it's boiling for release. I think you guys are just around the corner now.

"In NYC (with DD's NYC & NYC Airports) with default SMP v3 settings I have very little ram left, about 100 with fps in the 20s. The sim is still very smooth." If the OP is talking about the VRAM usage in XPX: I run HD mesh, orthophoto's and some World2XP - even then, out of my 6GB Vram I don't like it touching 4GB and above. Headroom helps a lot with transitions. If you have nothing left then some ram has to be cleared for new ones to come in. You will wait this out. Also remember that the GTX970 only has 3.5GB VRAM - the remaining 500mb is not that fast and people got their pitchforks out earlier this year when a bunch of people were pushing their GPU's at 4K res and extreme graphics settings in other games and ran into stuttering - which is not entirely relevant here as stuttering vs pausing is two different things to the eye. But, both are due to VRAM running out. DD's NY series is awesome, but you will run into pauses when the weather reloads and SMP reloads the clouds along with you moving in the scenery. If this scenery has hd mesh and relative high rendering settings you will run out of VRAM and you will pause as the engine redraws. If I fly in NY or EHAM (the most intensive airports imho) - then I reduce some settings to make that more FPS friendly. But most important of all, I keep an eye on my VRAM and even then I don't do it in game as that does not indicate actual VRAM usage. On the flipside, if you run out of system RAM that is in itself a easy fix, either reduce open programs or get more RAM which is quite cheap these days (unless it's DDR4).

And there´s the risk of "thats not a bug, its a..." So let the professionals find the real bugs. We waited so many years. I don´t care about weeks.

But a 200-strong test team can be overwhelming - These guys know what they're doing, and they want happy users with a highly-stable and accurate simulation - Not a tonne of complaints about things not being right! Patience is rewarding, why not just wait a little longer and not have to worry about any problems?

Anyone who downloaded Lanai, Molokini, or Kahoolawe, needs to follow those files immediately as major updates/total overhauls are coming to those scenery files in the next few months. Niihau will be released first, then updates will follow with the combination of Molokini into Kahoolawe and the re-release with HD Mesh, then finally Lanai, which will probably take quite a bit of extra time as it has an airport and lots of roads and whatnot. Please check the new thread about the HD Mesh.

Just me doing some FMC route testing at my local airport ENGM. One SID and one "point merge" arrival.

You can switch layout on the fly...

This has been on our list of want-to-have for a very long time. So far we haven´t been able to put any effort into making this work, but we certainly plan to do so after release of V1.0 . It´s not easy, as both machines must stay synchronized and we have a lot of datarefs that need to be sent back and forth... It has been discussed before, it IS possible to operate this plane safely with just one pilot (and judicious use of the autoflight system plus some proper pre-planning for high-density workload phases), but for a realistic and redundant operation of an aircraft of this complexity and speed really two pilots are needed in the cockpit. Jan