Litjan

yeah...

No.

Ah, ok - the weather radar takes it´s cues from the X-Plane default weather (showing rain where there is rain), so there may be an incompatibility there. Not sure we can/will adress that, but will certainly take a look. Jan

With "good" being the operative word here, this pretty much rules out X-Plane´s default AI traffic (for now). I would look at an online ATC service like VATSIM, IVAO or PilotEdge. Cheers, Jan

A few questions came up and I will try to clarify things a bit: In the default setup, gizmo will pop a little screen every time you start it up. It will ask you to refresh your license, so it loads you up with a full two weeks of "possible offline use". We do this so no one can say that "gizmo phones home behind my back without me ok ´ing it". If this bothers you, you can opt out of this "automatic refresh on startup" (go to the preferences box). Gizmo will then count down your two weeks silently, and ones it runs down, a window pops up and asks you to refresh your two weeks. This is exactly the same process that would happen every time you start up if you hadn´t opted out. The third option is to bring up the refresh box yourself and trigger it manually (if you opted out but plan on going on a trip without internet access, for example). Once your two week timer runs out, the box pops up - and you need to be online to refresh it. If you aren´t you can´t use the program until you are online and can validate again. This is exactly how X-Plane (digital version) does it, too. If there is strong demand to do ALL of this without bothering you (i.e. phone home to refresh silently), it may be possible to add an option for that to the preferences menu. Just let us know. Cheers, Jan

It´s definitely something we want - so it´s not a question of "if" but "when". Cheers, Jan

Sorry, "ferry flight" for a bit longer... Cheers, Jan

No idea, I don´t have xprealistic so I couldn´t say. I was not aware of a problem with x-enviro along with the vortices in XP10, and no effort was made to fix anything in that regard. The weather radar of a 737-300 does not show turbulence. Cheers, Jan

No VNAV work for this patch, unfortunately. We are aware for the need of it but could not allocate the time to really fix this, as we intend to rework the code from the ground up to make it really good (no band-aid patches). Jan

I don´t think adjustements for liveries are needed, they should still work. No fix for the drag problem - if we would fix this for XP11 it would be messed up for XP10. So this will need to wait until the full compatibility patch. Jan

Hi Tom, excellent post and all your observations were spot on! The reason for flaps 15 is the ability to fly a missed approach with flaps 15 without having to use the alternate system (electric engine) to retract the flaps during the go-around. Also interesting may be the fact that you had 10% of quantity remaining in the B system - this is due to the intricate "standpipe" design of the hydraulic supply lines in the hydraulic reservoir. If you have a rupture in the engine-driven-pump circuit (most likely due to engine failures), this highest standpipe will only drain so much fluid overboard, with enough remaining for the electrically driven pump. Should there be a rupture in that system (as in your case), the fluid will drain to the lower standpipe - with enough remaining (ca. 10%) to supply the automatic slat system via the PTU, should the need arise (stall while at flaps 1-5). In a real airliner you would probably divert to the nearest suitable airfield with declaring emergency, after all you are out of redundancy (the standby hydraulic system doesn´t really count) - but in a simulator it is acceptable to continue, of course . But you can see that even loosing half of the hydraulics is pretty much a "non event", piloting wise. You land with flaps 15 and are limited to CAT1 - legally. Plus there is a startle if it happens while you are on autopilot B, which will disconnect with the warble. Technically you could still do an autoland with a single autopilot and the flaps extended via the alternate system to 30 or 40. This would fall under the "emergency authority" of the Captain, and would only be done in very dire circumstances (inability to reach an alternate airfield with CATII or III weather prevalent). Cheers, Jan

No estimate. Jan

Hi, Tom and crisk are right - I believe it will work much better with 1.1 - as you can see in Tom´s picturese (he is running the 1.1 beta). Cheers, Jan

I would bet that this one is fixed in 1.1 - so lets check again once it is life (no, don´t know when :-((( ) and see... Thanks for reporting, Jan

Thanks for contributing to this great community of Classic pilots!

Yes. No, really - you are doing something wrong but it is impossible to determine what exactly from your post. I suggest watching the tutorials on autopilot and VNAV use. Note that VNAV predictions on descent are not calculated correctly in many cases for now (we plan to improve that in the future) - but for climb and cruise it should work ok. You say that you can´t activate speed intervention in descent - but speed intervention is not installed in this aircraft, in fact there is not even a button for it in the cockpit. This confuses me....are you sure you are using our plane and X-Plane? Cheers, Jan

And another one to wet your appetite. Work continues to get the patch out as soon as possible! Cheers, Jan

Hi Jens, I looked at the procedure myself (didn´t even know it existed) and I really don´t see why the Auto mode should trip when the outflow valve moves from close to open after moving the FLT/GRD switch to flight. The plane isn´t pressurized in the first place (packs are off), so opening and closing the outflow valve would cause zero change in the cabin pressure and therefore no "excessive rate" signal to the controller. That being said I must also add that we don´t model the cabin pressure controller down to the last diode, so it is quite possible that there are some test modes or fault detection logics that we don´t model. Thanks for the feedback, Jan

Hi, here are just my quick answers: 1.) The ninja-fixes aren´t hurting XP10 functionality EXCEPT that it won´t be possible to turn left/right during pushback, anymore. I think this is a worthy tradeoff, though. 2.) I have the list ready and will publish it just before we are ready to push the patch out - doing it now will just cause anguish (look-but-don´t-touch type of anguish...) Some people can´t deal with that sort of thing very well and I don´t like the negativity that is springing from that. I will shoot a new preview movie highlighting some stuff soon, though. 3.) Post 1.1 I expect to see an "official" XP11 "compatibility" patch that will fix some things that can´t go in a XP10 patch (drag, annuciator brightness,...). After that we will work on a full XP11 patch (materials, sound) and that should also incorporate more 3D work (cabin, doors, etc.) 4.) Good idea - we will also sticky the necessary steps to get it working in XP11, so that info won´t get buried in a mound of (sometimes not really helpful) comments 5.) F/O instruments should be working just as well as CPT´s side - except for the WXR radar and EGPWS display. This is a fundamental issue that may not be resolved anytime soon. Cabin night lighting will happen, most likely with the new cabin (not in 1.1). Cheers, Jan

The N1 displays will stay blank (refer to the N1 limit page to see the limit) until you start setting the values manually (you need to pull the little knobs out and turn them to do that)... just like in the real aircraft ;-) This is just a fallback mode that is rarely (I never did in ten years of flying the 737) used. Cheers, Jan

Yes, they are working again. Jan

Dang, they are getting on to us! I will immediately message the team members (which are actually kicking back in the Carribean spending the IXEG dollars on luscious cocktails served by luscious waitresses) to come home and get to work again! Cheers, Jan PS: Deleted the other two posts of identical content... we got the message!

Hi dreambox, First off, I gave you a reputation-click because I feel that you are touching a point that is very present for a lot of our customers. But I would also like to add our perspective to some of your points. I think you are correct in your assessment that our patch 1.1 for XP10 took too long already. Cameron and Ben gave the reason for the latest delay (flooding of Ben´s area), but we concede the point, it has been too long. The patch is ready to go out, Ben is working hard to update gizmo so we can roll it out ASAP. No time estimate, though. Here is my take on XP11: When you bought the plane, it was "for XP10". No mention of "...and future XP versions" or "will be upgraded to future versions as soon as they come out" etc. So while we feel the moral obligation (and the business need) to update it to XP11, we don´t feel the need to do a rush job on it and reserve the right to take as long as we want. We ALL have fulltime jobs. We could not allot the time for a XP11 update in due time, with some of us having other obligations that preclude serious XP-dev work for months or even years. We learned about XP11 not earlier than anyone else, and Ben warned all developers to NOT update their aircraft before XP11 was final. XP11 is STILL not stable. In fact 11.01r1 just broke the landing lights of our plane - going from historical evidence we expect XP11 to stay "somewhat unstable" for another half a year, or more. The 1.1 patch will bring some "ninja-fixes" for XP11 users, the worst problem being the sliding at slow speeds/in cold&dark. The remaining problems you mentioned (especially the engine problem) can be fixed with planemaker tweaks you can do yourself. The only thing that will still be off in XP11 with 1.1 will be the drag being too low and the annunciator lights being too dim. Thank you again for the nice words about our plane (in XP10). I assure you we are working on the XP10 update and also on the XP11 compatibility patch. I may actually do my next preview video for 1.1 in XP11 just to show you how well the plane already works in it. Cheers, Jan

Hi apilot, no improvement was made to the VNAV predictions. Also no mid-flight saving feature is in 1.1. If X-Plane crashes mid-flight, I suggest to contact Laminar Research customer support. For most people the simulation´s stability is very good, so it is likely that there is something that can be done for your setup. The usual culprits are incompatible plugins or memory exhaustion (due to excessive scenery loading). Cheers, Jan

And while everyone waits for 1.1 - here is a little preview of the EGPWS we flesh out more in the next patch: