Leaderboard

I did indeed have a simple view in mind, just to improve situational awareness. If there was a lite version until the real thing is implemented, most people would probably be happy with it, possibly never knowing the difference.

TCAS, even though rarely used IRL, is quite handy when flying on VATSIM, especially in uncontrolled airspaces. Same goes for hold function and even offset, which is a cool little trick to use when flying online with friends. Even though rarely used, in a flight sim they can be really handy! Just pitching in so you see what is important to the customers If I had a say, I'd have these functions before any of the other items!

42k kgs of fuel is given for a +4hs of trip, your cruising ALT FL200 doesn't make sense at all. can you share me your entire route? sid, trasition, rouute, star, trasition landing runway? something does not match on your parameters and the FMC is judging it will not make it. all of your waypoints have no vnav information populated (speed/alt), the fmc can not calculate a valid profile a few side tips: -you have to set the HDG knob to runway heading prior to departure -if you do not have fuel on the center tanks do not activate center fuel pumps on the overhead panel, you have an alarm trying to suction fuel from a dry tank (fuel low center) -the speed dial should be set to V2 speed given by the fmc when you set takeoff parameters prior to departure. This is the safe climb out speed in case something goes wrong. -edit: also your doors are not set to auto, you have an alarm too

You really don't need to venture too far to find one in development.

So on another note, quite a bit of a milestone. All the code for the VNAV 1.0 feature list is in place as of today and we are beginning flight testing and debugging of the full route LNAV / VNAV capability within a few days (our main tester seems to be a real airline pilot away at work....slacker). After our internal debugging checks and fixes, we'll engage a relatively quick beta test with some selected newbies (already selected)...and then we will mop and sweep, spit and polish and release. No date given. -tkyler

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 was just now able to see the video of the FMC VNAV climb. All I can say is WOW WOW WOW. All the other airliners that I own for X-plane pale in comparison to this one. If you tried to change things on the other airliner's FMC's as Jan did in the video, without a doubt, you either could not do it, or the FMC would have a "brain fart." Awesome job guys. I can't wait to add this plane to my virtual hanger. Once I do, the others will collect virtual dust. Kevin

That's what I was getting at

i forgot to mention if you are in vnav mode lets say cruising at FL340 and the FMC suggest a step climb to FL380 or you want to climb to FL360 or whatever, just rotate the MCP to your desired new target altitude and clic/push the altitude knob as well. This will let the FMC know you do require a new higher cruising altitude and initiate the climb to level off at desired target altitude. This will not work to reduce your cruize level since this was not simulated by the developers.

HDG: push the HDG knob to enter in HDG mode. Rotate the HDG knob left or right to your desired HDG heading, you can set max lean angle on the back part of the knob, default is auto. Once you are on HDG mode, rotating the knob will make the aircraft to turn immediately, you are already in hdg mode. ALTITUDE: you have two options. -VS (vertical speed mode) set your target altitude on the MCP (higher or lower) push VS button on the MCP. The vert speed display will illuminate. Rotate the VS wheel dial up or down to set your desired climb or descend rate. Once the aircraft reaches your MCP alt it will enter in ALT HOLD mode and will maintain such altitude. -FLCH (flight level change) set your target altitude on the MCP press FLCH button if you target altitude configured on the MCP is higher (a climb) A/T will enter in climb thrust mode as configured on the FMC until reaching desired altitude. if your target altitude is lower (a descend) the A/T will enter in IDLE mode and set nose down as required to maintain present air speed. To maintain present speed being at IDLE it will put the nose down as much as necessary. So the rate of descend will vary based on your current speed and altitude. note: VS mode will gurantee a specific rate of climb or descent in ft/sec as configured on the vs display. FLCH mode will keep varying rate as required to maintain IAS during the process. hope this helps

Please, .. new video?

Landing in sunset

No its not...but this one is!

What's next?... I think is not the time to talk about the next project when this one is still latest stage of development. But on the other hand, and while we impatiently wait for the release, it is OK to dream about what bird these guys can make. But for now I think the next will be that IXEG take a deserved rest and a deep breath before starting to deal with all the questions and posts, and for sure a huge number of people asking for help, once is finally released !!!!

That is noted. Thanks for the feedback! Jan

Really looking forward to this aircraft. Ive been a fsx/p3d user for many years and latly started to try out x-plane. One thing I discovered after bying aircrafts to x-plane is that they often are buggy or lack of features. And they are charged at full price and updates are comming slowly or not at all. So Im glad you putted this list out so I know what to expect. 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. If I could vote for one thing that i want in version 1.0, it have to be the "Hold" function. I do all my flights online on Vatsim. And with heavy traffic events you are often told to hold. So that is a feature I personaly would love to see in the first release. Im not demanding anything, its only my feedback on the list. Keep up the good work.

This doesn´t even happen in real life all too often, so don´t get your hopes up . Jan

Carenado Cargomaster over Yosemite

The thing is, people try to argue semantics using their own, subjective dictionaries. It's silly. It's a colloquial term, created by us, the simming community, to distinguish between very complex and those less complex addons. More or less, the general consensus can be made between the simmers of what is and what isn't a "study sim", but there will be obviously some differences here and there. What I find crazy though, is that looking at some posts in this thread, NOTHING is a study sim, and nothing EVER will be. If you are looking for 1:1 simulation, then go ahead and pay $550/hr for a Boeing simulator and then you will have an actual experience. PMGD is regarded as study sim by the majoriy of the community, and yet it's missing quite a lot of features of the real thing. Maybe some people should just accept it's a game, and that "study sim" means something different in PC simulation games than they think it means. So tl;dr (as some people seem to get lost in posts): "Study sim" is a term colloquially used by specific community, which isn't to be taken literally. It has its own meaning given by that community. While everyone has right to their own opinion, arguing with semantics widely spread in the community is rather silly. Cheers.

Please, please, please, please, please: READ my post again. Slowly. A third time. Ask if you don´t understand a word. I know English might not be your first language (it´s not mine either, so maybe I used a wrong word?), so please don´t jump to any assumption on a casual glance of what I wrote. Entertain the possibility that for the first time in your life you might be wrong or have made a mistake. I refrain from quoting my own post, because if you can´t comprehend what I wrote the first time, you will most likely not be able to if I just post it again. I never said we "drop" anything because it is not important or not used. I only said it won´t be in 1.0, and stated reasons why we picked feature X over Y to omit FOR THIS INITIAL RELEASE ONLY! So all your posts and bickering about this are just meaninlgless hot air and I refer back to Tom Knudsens initial commentary that still holds true: If you NEED a feature that we omit for 1.0, don´t buy it yet. Otherwise please don´t make me feel sorry for you and your lack of reading comprehension ability, every day I am mad or sad or sorry I can´t help Tom to finish the FMS and next thing we know we just might drop LNAV for 1.0. How about that? Jan

I don't post much, but as an Instrument rated SEL pilot you just made me spit out my coffee when I read the above, It's just not an airline pilot.

Hi there, I agree with you - the goal is a fully functional FMS, and no feature is so "unimportant" that we will simply leave it out "forever". But - as I said before - we need to omit some stuff for 1.0, or delay release even further. We opted to omit things that you can probably do without the easiest. Custom Holds: I have never, ever flown a custom hold AFTER I got away from that pesky instructor in the glaring Arizona sun in1993. Maybe a "hold at present position" (can´t remember, though), but if ATC asks an airline pilot to "hold at the R-155 at 35DME to LBE with 267 deg inbound, right turns" I would LOVE to hear the reply on the radio. Regular holds :I fly about every two months or less. Of course that depends on the destination/weather/time of day. If I had to fly a holding and my FMS couldn´t fly it, it wouldn´t even raise my heartbeat - I probably wouldn´t even have to put down my coffee! Just push HDG SEL as you come up on the fix, turn the heading bug in the direction of the hold to the outbound bearing (you can use a calculator, if you have to), push the stopwatch as you complete the turn. Maybe adjust a bit for wind. ATC won´t berate you if your inbound timing is 0:55 instead of one minute, they have other problems to worry about if they stick you in the hold... Offset: I think I said that before, only really used on Oceanic/African Ops. If you really have to, you can also do that with HDG SEL as a substitute. User created points in flightplan: This is something I do about once a year in real flying. If I am bored. Display of RTE data on EHSI: This is one I actually miss, as it greatly enhances situational awareness. Restrictions to meet, speeds to fly. I think we will have that fairly quick. Of course you can just look at the LEGS page to see the data... If you let 90% of your flight be completed by the FMS, you are either lazy, a bad pilot, or need to get an Airbus! Jan