Litjan

Hi guys, yeah, the ESC thing...beyond IXEG´s control, fortunately . Good to read that you are making some progress, Bruce. If the new OS is no help, here is another hint regarding the thrust reverser-slowdown: Try to disable the option "Show custom animations in replay" in the PREFERENCES menu and try again? Yes, Benjamin, holdings are not yet implemented (as mentioned on the list we published many months ago here: http://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v10/ We tried to be upfront with these shortcomings, but I think many users were not aware of this list... Jan

You can do both. Use instant if realistic is too slow (or doesnt work on the center tank) Jan

Most of these problems were attributed to some sort of live virus-scanner, like windows defender, avast, etc. Try to disable your scanner and try again. If that works, you can set your scanner to not check the X-Plane folder...that should be sufficient. Jan

Hi, we will tune the VNAV performance heavily in the coming weeks - it looks like you found a bug and that should be cured during the next quality-pass on vnav calculations. Jan

Try to disable and see if you still get the effect?

No, the ECON speed flown is influenced by current wind and adjusts with changing winds. Jan

Hmm, interesting... do you have any plugins running that change the artcontrols, like Terra Haze or such? Jan

Hi, I will look for that behaviour - thanks for the report! You know that you can always (while stationary on the ground) change the fuel in the GROUND SERVICES menu, don´t you??? Jan

Hi Benjamin, I am no authority on this - but I would assume that for good measure you should exclude the whole X-Plane folder. While it might be enough to simply exclude the airplane folder (you can certainly try!) I think we also poll the default apt.dat to find coordinates for "smaller" airports continuously (so you can see them on the map). Jan

Hi Matt, as soon as you get the console the first time, all bets are off. Consider the code to be "out of sync" and various things are not going to work anymore... To really help reproduce the crash, we usually solicit certain .txt files - you can read up on that in the included documentation (bug report guide). Otherwise it is near impossible to recreate the cause, there are simply too many factors. Once you get the console, close it, then bump your mouse on the right edge of the screen and click the "bolt" symbol to reboot the gizmo scripts. Then you can continue your flight. Only caveat: If you started the whole thing in "turn-around" or "cold and dark" then this will be the state after reboot. But you can work around that by clicking the option "ready to fly" before you reboot gizmo. Good luck, Jan

Hi, what exactly are you observing? We have a fix for the plane spawning with 0 fuel inadvertantly. We also have a fix for the center tank not filling/emptying on "realistic" speed. Did you observe something different? Thanks, Jan

Thanks for the report, Matt! The FMC shouldnt crash, period. We will look into that. Just a word of advice about the "optimum altitude": It does not take distance to fly into account. It purely looks at the current weight (and speed, if not in ECON). So it is quite possibel that you will get an UNABLE CRZ ALTITUDE warning, even if the optimum suggests that you should climb to it. I will try to replicate your crash - if you get another one, be aware that you can "reboot gizmo" while flying and at least you get a responsive FMC back (though you have to re-enter your data) Jan

I just checked on our model: 2000 feet of altitude, 48tons (105.600lbs) 280-250 takes 27s and 2.0NM. 250-210 takes 42s and 2.7NM. I checked one of my movies from the real aircraft - and it takes 33s to go from 240 to 210. Thats roughly 11s per 10kts (less at higher speeds, more at slower speeds) - so another 10kts for the 250-240 and we are coming out at 43s (vs. the 44 I have in our model). I am pretty happy with that! Jan

Thanks for narrowing this down! Will try to reproduce and add to list... Jan

Hi - this doesn´t sound like intended behaviour! Can you beef this report up with some pics or even a short video so we can see what might be going on? Thanks, Jan

Hi and thanks for the report! Could it be that you have "random failures" selected? I am not sure if "trim runaway" is a x-plane failure, but that is the only explanation I could think of. For the engine fire - yes, that is a known limitation. You need to reload the .acf file to get that working again - the fire-handle cutting the fuel supply does not reset on gizmo-reboot. We will look into that. Jan

Thanks for the report! Jan

Sure - it isn´t very prominently featured, I admit. Go to the "First Flight" Quickstart guide and check page 4 (PREFLIGHT). Here it says: • Configure your joystick as desired. We recommend that you set X-Plane's stability augmentation to 0, and the control-response sliders should be at about 25% Happy flying, Jan

Nah, I will just leave it here because someone else might run into the same problem! There are no "wrong" bug-reports - I am happy for every report we get (MUCH better than a user being frustrated by something and won´t even bother to post) - and I am all the happier if we can clarify things. Jan

Whoa, that was a "difficult birth", as we say here in Germany . Happy that mother and child are well, happy flying now! (You waited long enough!) Jan

I think there is nothing that prohibits this function on ground, too. Except that usually the airplane doesn´t climb or descend much when on the ground . However - if you are RIGHT on the edge of triggering this function, and the pressure changes, or you taxi downhill, or the plane settles a foot during "spawning", you might very well get this alert. I am not sure why you can´t enter V-speeds after that, it might be a different bug (unable to access TAKEOFF REF page) - we have yet to investigate the erroneous switch to "air mode" while the plane is still on the ground. Likely an initialization problem, like Tom suspected. Jan

Thanks for the nice words! - if you select R-TO from the N1 LIM page, without entering a TASS first, you don´t have reduced thurst, and therefore I would expect TO to display. Jan

Good to hear that!

Are you sure the IRS is aligned (position entered and accepted, no flashing ALIGN, etc.)? Can you double-check, please? Thanks, Jan

Get me one, too, will ya? Implementing a "quick align" function is on our list - it will probably not be on the PREFERENCES list, because I think this should be something like "recharging battery". I don´t want to teach users bad habits, i.e. waiting with the align process until they are ready to taxi. If you "mess up" you have to admit and go to that special "failure" menu to fix it . But making someone wait for 13 minutes because of a simple (newbie) omission is a bit harsh, I agree. Cheers, Jan