Litjan

Thanks Ben for reporting back on that! I knew Windows Defender would cause some problems while entering a modified route into the FMS...but your problem was new! Thanks for sharing, Jan

Now I have learned to normally stay out of these "authorization" things. But whatever possible reason could someone have to type in FREEZE when presented with the warning that this action will lock his computer forever...if he actually intends to use this computer in the future? The only possibility to undo this action is to get a new copy of the IXEG, as far as I know. Or a new computer. You still have the right to use three machines, just not the ones you locked yourself when facing a very clear and concise warning to not do this if you want to fly the IXEG on it... Cheers, Jan

The one thing I could imagine is that you have no hydraulic pressure for using the brakes. Other than that our brakes are "default X-Plane" and should work just as well as in other aircraft. Cheers, Jan

Like Tony said - the VNAV logic can NEVER fly across the altitude set in the MCP - it is like a safety barrier. The VNAV logic can also not fly in the "opposite" direction, i.e. it can´t climb if the MCP altitude is "lower" than the current altitude, and it can´t descend if the MCP altitude is higher. So you have to assist the VNAV logic by setting your MCP altitude correctly. Cheers, Jan

Hey Nick, Nah, I won´t delete it - some valuable info in here that someone else might find useful. Plus - if you have any other questions - feel free to post! Cheers, Jan

Hi Nick, welcome and thanks for the nice words. We had to switch styles for some instruments during development - mostly because I was able to provide detailed shots for the type we had installed in the aircraft I flew. So yeah, some of those "early WIP" shots aren´t representative of the final, current product. At this point it is also not likely that we will spend the time to develop different variants for things like radios or transponder panels, to be honest. I hope that you will get used to those that we have! Happy landings, Jan

Not sure what you are talking about, do you have a pic or so? Thanks, Jan

Hi TH, it is normal for the real plane in VNAV PTH to not adhere perfectly to the "set" speed - the plane will calculate a fixed geometric path in the sky that it "believes" it can fly with idle power at the calculated descent speed. But more often than not some external influences (wind, mostly) will not allow the speed. The plane will prefer to stay exactly on the calculated path and lets the speed go up or down. If this is excessive, it will nag you "drag required". If the speed gets too slow, it will activate the autothrottle and add thrust to regain speed. But there is a "window" in which speed may vary without any action at all Our plane does not model a "smooth" intercept of the VNAV PTH at the top of descent (yet). So it will initially get a big high, then tries to catch up by descending fast to the pre-calculated path. For now there is not much you can do to avoid that, except manually starting your descent a bit prior to the T/D in V/S mode, then, once on the path, enable VNAV PTH descent. Cheers, Jan

Hmm, no idea, then - something unique to your setup. I think we would have received more reports on this if it was a genuine problem with the IXEG. Works fine on my system, too... Try to remove your plugins (better pushback and xenviro) to test if they influence this... Sorry I can´t be of more help, Jan

Hi Ben, really weird. The defaults are shift-2 for flyby, shift-3 for nearest runway, shift-4 for chase view, shift-5 for tower,...and so on! They don´t work for you for default planes, either? Some ideas... Do you have the SHIFT-LOCK key activated, accidentially? Do you have a third-party plugin running that may interfere (fly with lua, easyview, etc)? Did you change the key assignments in a custom key-binding profile? Cheers, Jan

Hi Ben, I am not aware of the Shift-8 view mode - the regular external view mode is shift-4. Can you try that? Cheers, Jan

Yes, I think this was only on an experimental, internal version. Cheers, Jan

No worries, Michael! I know it can be overwhelming to have a "real" 737 under your seat of the pants... I still remember the day I sat in the real one for the first time (March 92, Paphos, Cyprus) and even though I was type rated, had been in the LevelD for many hours and was "just" going to do some touch-and-goes to get my landing training in...I was really almost overwhelmed ;-) Keep learning and - most importantly - have fun while you do it! Cheers, Jan

And that is the way we model it, too. The "suggested" (QRH) Vref values on the approach page change with calculated weight, but once you "hardcopy" them into the MCDU they stay the same. Cheers, Jan

Hi Michael, I will concede that the tutorials are based on version 1.0 of the aircraft, we are at 1.2. Yet not THAT much has changed. I know you think there is a lot of stuff wrong with this aircraft, but let me tell you that I flew the real 737 classic for 10 years and I feel totally at home in our IXEG 1.2 and it pretty much (except for some stuff in the FMS like holds and VNAV descents) works EXACTLY like it did in the real aircraft I flew. It hurts me to say that - but flying an airliner (especially alone) is not for everyone. You need to be a proficient pilot to start with, any airliner is not a student aircraft. We have thousands of customers that fly the plane just fine - solely based on our tutorials and our training videos. If you crash and burn a lot or fail to get the aircraft to do what you want it to do, chances are that you don´t know how to do that. Yet I don´t think it is our job or comes with the product that we need to teach you how to fly an airliner. Cheers, Jan

Hi Michael, saving a situation with X-Plane will NOT work - for the reasons you found out yourself, many parameters don´t get saved. But it is possible to practice this (and other things) like this: 1.) Put the plane on the runway you want to land on. 2.) Tune the ILS freq and set the ILS course on both NAV radios and set autopilot altitude to 3000. 3.) Find out the Vref for the current weight (use placards above window) and set the plastic speed bug (white) on airspeed indicator. 4.) Pause the simulator 5.) Open the map (m key), change the display to IFR map (so you can see the ILS and waypoints). 6.) click the airplane, then change the altitude to 3000 feet and change the airspeed to 250 and the pitch to 3 degrees. 7.) drag the airplane to a spot about 20 NM from the runway 8.) close the map, unpause the simulator 9.) Now quickly: Turn on autopilot A, turn on autothrottle, dial in speed of 250 and click FL CHG. 10.) Raise the landing gear, click B to toggle parking brake off 11.) Now you can fly to intercept the ILS as usual... Jan

Hi Jim, 1.) Yes, hardware interaction can be tricky - us few IXEG devs don´t have all the hardware out there, and especially when scripts or plugins come into play, things quickly become unpredictable. Nonetheless we like to hear about interfacing issues, as we want our plane to work with what is out there to the highest possible degree. The trim wheel sound plays whenever the stab trim is moving. There is a sound for fast and one for slow trim. So if the sound is playing, chances are that the trim is moving, maybe ever so slightly - this could be due to an electromechanical pickup on your hardware fluttering between two values, for example. 2.) Yes, VNAV can be buggy, we are aware of that. You did right - if it doesn´t work like it should, revert to more directly controlled modes. 3.) Its hard to say what went wrong without at least a series of pictures or even better yet a short movie, showing the LEGS page and the two displays (EADI and EHSI) in the cockpit. Cheers, Jan

Cameron is right - this is something that hits pretty much every new user - create an exemption for the X-Plane folder in Windows defender. Cheers, Jan

Hi Jim, we did fix a lot of LNAV tracking problems with the latest update...but yeah, it could be that some more are lingering. Hard to find this stuff - if you get a case that is readily reproducible, we´d be grateful to hear about it! Not sure on the FOV, but I think the "IXEG view system" is also a good candidate for getting cut with the next update - X-Plane´system is all that is needed, in my opinon. Cheers, Jan

Michael, if the "jerky" situation happens when you MOD the route - you need to create an exemption to Windows Defender (live scan) excluding the whole X-Plane folder. It interferes with accessing the database (trying to real-time-read all data going in and out) and this tanks down the framerate. Cheers, Jan

I am trying! But I keep getting "installation error". Update rejected.

Need to turn on WXR SYSTEM switch first, just like in the real aircraft. Jan Alternatively you can install the aircraft another 57 times - and then it should work!

You may want to ask that question in the TBM900 forums. Good luck, jan

Well, the master caution lights and the Fire warn bell cutout don´t really make a sound when you press them, they aren´t switches, they are more like press-down-to-contact types. Cheers, Jan

Not quite sure what you are talking about... Cheers, Jan