Litjan

No, at -200 the airplane is slightly pressurized and the doors and windows can not be opened. Remember - low cabin alt = high cabin pressure The real reason is that the outflow valve in this condition is "almost closed" (to enable the pressure to build), so no air can rush into it during rotation and hurt the passengers ears. The slight pressure also seats the windows into the frames, so they don´t rattle on takeoff (just a nice side-effect). Jan

I upped all warning sounds a bit with the next update... Jan

Roger, thanks

Glad you fixed it - out of curiosity - what is ITOW? Jan

http://forums.x-pilot.com/forums/topic/9202-cmdexe-windows-start-opening-straight-after-takeoff/#comment-96789

Hi Ron, ok, that was a shot from the hip We had this crop up a lot initially, usually attributed to conflicting plugins (please remove temporarily, then reboot X-plane) or outdated operating systems (Mac)... Does this help? Thanks, Jan

I´d have to think hard about it to get the behaviour of the altitude alert right off of the top of my head - maybe someone can post the snippet from the real FCOM? You might be suffering from the "can´t hear certain sounds" syndrome, though - usually attributed to conflicting plug-ins. I THINK you should at least hear the C-chord sound once when triggering the alert, after that the light keeps blinking without sound. I agree about the LYNDY4 arrival, but this is a different problem. Jojo reported that the restriction wasn´t imported correctly and he added it manually. We will look into why the restriction wasn´t imported initially (had some other reports about that, too) Jan

Remove or update JAR ground handling

Hi Jonathan, your assumption is correct - for now we disregard any altitude restrictions that are WAY ahead of the T/D - the reason is that it is very hard for us to determine if they should be part of the CLIMB or part of the DESCEND? Maybe we should never climb above FL195 until passing TNP? We will revisit this problem at a later time - for now just descend to 195 manually in time (you can enter a new CRZ alt of 195 in the Cruise page and do a cruise-descent with 1000fpm). Jan PS: Altitude alert will never be heard if the autopilot flies the plane.. You will hear it in manual flight if approaching the MCP alt too fast, or when straying from it for more than 300 feet (iirc)

lanmancz is partly right: You need the little black placard for both manual and standby operation - not for auto. Flying in manual is an absolute emergency, fallback mode. You want to somehow keep the aircraft pressurized - any movement of the thrust levers will change the influx of air, and you would have to change the position of the outflow valve - try it, it is fully modeled! In standby you will set the CABIN ALT to departure elevation -200, then switch to FLT. During cruise you set the CAB ALT to the suggest value according to your cruising altitude. When descending, you set the CABIN ALT to landing elevation -200. This pretty much mimics what the AUTO mode is doing, too. Jan

You most likely flicked the "light test" switch on by accident. I really wonder if there is something amiss with your computer, because the problems you are describing are pretty much not seconded by anyone else? I hope you can figure it out, Jan

Thanks for the praise, Marshall! The FMC is progressing nicely towards a point were reliability is much improved! We have not started on the "yet to come" features, though, still concentrating on the odd crash and fixing some bugs. Cheers, Jan

Totally correct. The disengage bar removes electrical power from the Flight Control Computers, which also drive the FD´s.The disengage bar is more of an emergency device, when nothing else will work in disengaging the autopilots...It is NEVER used in normal operation (although a lot of simmers seem to use it extensively, not sure where that habit started). Jan

There are rumours that there was an update to GndHandling that might fix this issue... but not sure. One of our testers got GndHandling recently and never had any problems. Jan

Thanks for the report - but without proper log files it is almost impossible to see what was going wrong. Can you read the "bug reporting guide" in the documentation (sorry, it is in English)? We at least need a movie, a gizmo-log.txt and ideally a debug.txt Vielen Dank, Jan

Thanks, mmerelles! I am sure everyone who posted here read this post? http://forums.x-pilot.com/forums/topic/9419-if-you-have-problems-some-tips-inside/#comment-97935 Jan

Hmm, we are getting some reports on this - but most people can hear them fine... We don´t know why that is, yet. Can you please remove (temporarily) all other plugins except for gizmo - then restart X-Plane. You have to physically move them from the plugins folder, just clicking "disable" won´t be enough. Thanks, Jan

Hmm - but the flight-spoilers deploy on touchdown? Jan

The replay mode is sometimes a little buggy - since we had to work around X-Plane not recording custom datarefs for the replay. The flight-spoilers come out at touchdown (wheel spinup), the ground spoilers only after compression of the right main gear strut. So on supersmooth touchdowns, there can be a noticeable delay, too. Jan

Can you guys with the micro-stutters try this? Jan

Very interesting report - I will make sure to include that in my "recommendations in case of problems" list! Thanks for reporting back on that! Jan

Can you try with a default airplane? Jan

Hi Xander, I experience the same - but this is attributed to X-Plane´s physics modeling in tight turns. It just bleeds energy very fast...maybe we can tweak the ground model a tiny bit better... But here is my offer - you run that single engine up a bit higher and forget about the cooldown time - and I will pay for all the extra maintenance costs that you will suffer! Jan