Litjan

Will forward this - thanks! Jan

Thanks for the reports, everyone! We will take a look and see what we can find out! Jan

Excellent, thanks!

Hi, this is correct, the FL CHG mode will switch at a different point than the FMS. I am not sure what the underlying logic or algorithm is, we simply tried to mimic what the real plane does. The FMS switchover is a bit more involved - the FMS knows what the desired "new" speed is, and can switch over at the exact right altitude. The FL CHG has no idea what kind of MACH no. the pilot wants to fly after switchover, so it just does it at a "safe" speed. It´s up to the pilot to catch this switchover and adjust if desired. Jan

http://forums.x-pilot.com/forums/topic/10166-slowing-down-braking/

Hi sirtopper, the engine driven pumps are variable-dispacement piston type axial pumps and they can output 3000 psi at very low rpms. If you would run a lot of consumers (i.e. flaps, gear) at this low rpm you could probably see pressure drop a bit sooner. Theoretically (no leakage) you could even maintain pressure in a closed system without any type of pump action (think of the brake pressure accumulator), but I think we timed the pressure drop to the rpm after the real aircraft. Jan

Hi Bruce, the ESC is the "Eurovision Song Contest" held yesterday in Stockholm. Off-topic banter ;-) Be aware that Mac computers have a function that vastly decreases CPU frequency when they get too warm. They seem to be more prone to this than "normal" computers, so what they lack in raw computing ability they make up in style and design, it seems . One of our developers also had this problem and solved it by putting one of these cooling pads underneath. Could this be the case in your random slow-downs? Jan

Not "bad" at all - I invite all reports like that - even if they later turn out to be "working as intended". Report everything - then we will sort out what´s quirky and whats not! Keep ´em coming, please! Jan

And you will get a blank roll mode when you press the TO/GA button in the air (GA mode). The roll bar will provide commands to maintain the same ground track you had when the buttons were pushed. Jan

You are correct. The valves are controlled with AC power (but operated by bleed pressure), so when all power fails and you are on battery, the bleed supply will just stay the way it is. In addition, the indicator needs power to "move the needle" (it is not springloaded to zero), so you would not see a change in pressure anymore, either (for example if you shut down the engines now). Jan

Oh! no, thats not what it should be like. I didn´t get what you were talking about, sorry. There you go again: A picture says more than a thousand words. Thanks for the report, Jan

You will also see a reversal of the "winglet" effect at higher speeds. The most benefit is during slower speeds with a higher angle of attack. The induced drag is higher, and the winglets are more effective in reducing it. At higher airspeeds the parasitic and form drag prevails, and the extra frontal and surface area of the winglets shows. From a pilots perspective I find the effect most noticeable during slow-speed descents. Especially when you are a tad high anyway, and ATC asks you to reduce speed "minimum clean" to stay behind some slow-poke that is getting paid by the hour . The extra "2 percent" efficiency gain during typical cruise speeds is something that only "really really great" pilots can "feel". I can´t. Jan

Hehe - some suggestions (all from the real airplane): Use a flashlight (there is one in X-Plane, too) Use the dome-light (this is what pilots usually turn on first when they enter the cockpit at night) Use the emergency exit lights (just flip the guard closed, they will light up if there is no power on the generator buses) Jan

Ok, I will take another look, thanks for the report! Jan

It could be that you have to use the FO brightness control knob on the FO´s side to control FO´s side brightness ;-)

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