Litjan

Noted, thanks! Jan

Hi Bernt, I will try to replicate this - stay tuned! Jan

Thanks for the report - will verify! Jan

Try to disable "show custom datarefs in replay" in the PREFERENCES menu. This will help with the crashing, but you cant see the spoilers and reversers in replay anymore... Jan

Hi everyone, please help us scrutinize this - with every patch - despite careful testing - there is the chance that we introduce new bugs or don´t quite get the old ones (anyone said "spoilers"?? ). Would love to hear your feedback on this and keep the reports on bugs (in the support forum) coming! Highest priority of course are still the gizmo-softcrashes - though I do hope that we have reigned these in further signifcantly with this patch. Happy landings, Jan

Thanks, Tim!

Hi guys, I think the issue you are seeing reported in this thread may actually be a bug. When turning directly to a new waypoint, the plane should just make a simple turn, not re-intercept the line between the current position and the new waypoint. We will look at that during the tuning phase... Jan

Thanks gentlemen, nothing for me to add here. And thanks again for the report, Tom - especially the .84 issue should be fixed in 1.0.3 - the autopilot will now retain the current commanded speed when switching from VNAV to another pitch mode. Jan

You are not alone. There are probably quite a few 737 pilots out there that don´t really understand the system and why the airplane manufacturer introduced it. Jan

Could be that we mixed that up - thanks for the heads-up! Jan

Excellent, Thanks! Jan

Hi Bernt, be advised that "looking back" at the ground services GUI while fueling will immediately stop the fueling process - is this what is happening to you? Jan

Very interesting! Can you do a DEBUG.txt output after you put in the route? That way we can analyze a lot easier! Thanks, Jan

Known, not easy to fix! Thanks for the report (actually VERY surprised that we haven´t heard a lot of complaints about this one already!) Jan

It looks like some sort of ground radar return... In the real plan I would say you picked up the spike from a military radar station, but we don´t model those... It might be an artifact in the terrain tile - tilt your radar to +5 and see if it persists? Jan

Don´t push her that hard! You might actually be against some sort of performance limit - hot weather, high weight, icing... Do you see the engines at full power or are they throttling back to avoind going over 0.79? Jan

Hi Tim - I am not familiar with auto info labels - how are you getting those? Thanks, Jan

Please don´t . By the way, the cabin can never have less pressure than the outside - there are big, flat depressurization panels that will simply "flip in" to make sure that never happens. You can push them in during outside-check to test them. Jan

Thanks for this interesting report! We took some measures to avoid displaying takeoff speeds and approach speeds on the EADI speed tape at the same time. So this is probably whats kicking in, here. We figured that setting approach speeds would be a higher priority than setting take-off speeds, hence the bias. Jan

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