Litjan

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:

I am actually in agreement with some of your statements. When we released the plane, it was not "complete". We tried to shed a light on this with this post http://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v10/ . I have tried to be upfront about the shortcomings of the product at the time of release - this was not without debate in the team! It is not normal to highlight the shortcomings of your product in this industry, and if you look at the product description of other add-ons and compare that with the actual product released, you may find some discrepancies there, too . At the time of release we faced the decision to either release (and fix the shortcomings later on) or to stop work on it altogether. I think that the plane, even in it´s current status, does carry value. At least that is what the majority of user feedback indicates to us. It was our intention (and my belief) that the team would be able to provide fixes to shortcomings and the missing items in a more timely manner. I personally feel disappointed about this myself. I can say for myself that I worked in support of the 737 continously in the last 12 months - but I am not a programmer or a 3D artist, so I have to rely on the part of the team in charge of that. Morten stated correctly that the patch 1.1 for XP10 has been done (for several weeks now). I have also completed the interim "compatibility patch" for XP11, including the flight-model adjustments. We have not added the new "material properties" (again, I can´t do that with my lack of 3D-skills), but the plane flies (and taxis!) in XP11 just as well as it does in XP10. We are waiting for Ben and X-Aviation to deliver the new Gizmo version (as Morten mentioned) so we can get the patch to you. It is not in the IXEG´s team´s hands, and hopefully Ben is up to speed again soon after getting hit with the flood to clear this milestone and then we can progress. Jan

And that is not what I was saying at all. I was just trying to provide some insight. Please don´t lay words into my mouth.

I can understand the disappointment and the need to vent it. I would probably feel the same way. We like to maintain an open channel, though. And of course, we value the customers who paid and acknowledge the fact that THEY didn´t do piracy or sharing. I am not saying there won´t be a patch for XP10, and I am not saying there will be no compatibility patch for XP11. But I can´t say, when. And nothing really has changed, in that regard. Jan

No, the project is certainly not dead - but I would say we are at a stage where the speed of progress is too variable to make any predictions. I (and most likely the majority of the team) agree on a good business opportunity lost with the current level of excitement for XP11, but it is what it is. Making money is not everything in life, everyone in the team has their own motivations and agendas and they all come into play in a joint endeavour like this one. We had some setback to motivation as well, especially with the rampant pirating and sharing that happened with our product, and it certainly made some of us wonder if it is really worth our time and hard work. I make less off of the 737 each month than what it costs me to take my wife out to the movies with a dinner at a nice restaurant afterwards - just to give you some perspective. So the business aspect is certainly not that important to me . Sorry that I don´t have any more uplifting news, Jan

Just a word of advice - the plane is not XP11 compatible, and won´t be for some time, probably. The patch to bring the FMS to the stability level from "ok" to "good" even in XP10 is still outstanding, and we can not forecast how long this will take, unfortunately. So if you buy now, be prepared to fly it in XP10 only and only at it´s current status, with the FMS being frail to operate. Cheers, Jan

Cameron is exactly right. Here is a little copy and paste from the product page: Developer: International X-Plane Engineering Group (IXEG) Download Size: 1.2GB Comaptibility: Mac and Windows. No Linux. No X-Plane 11. Cheers, Jan

And just my 2 cts: The IXEG 737 is NOT compatible with XP11. If you want an airplane that is compatible with XP11, buy an airplane that is compatible with XP11. The IXEG 737 is NOT compatible with XP11, and won´t be for some time. If you want an airplane that is compatible with XP11, do not buy the IXEG 737. Buy something else for now, there are quite a few very good options out there. Phew, I hope this makes it across the language (or IQ-) barrier ok. Sorry for being blunt. We do not know when we will get to making the 737 compatible, heck, we have a hard time even getting the much needed patch for XP10 out, for environmental and some othe reasons I can´t discuss here. For that I am personally sorry - for not getting compatibility with XP11, I am not sorry (yet, but I am starting to feel a bit of guilt). It is what it is (to quote a teammember of mine). Jan

Taxi, turnoff and landing lights don´t work on the IXEG in XP11.01b1. They worked until 11.00, I don´t know why they don´t anymore. If you want to help this get fixed, file a bug with Laminar Research. Cheers, Jan

Make sure you read the process correctly. Did you get a ticket number for your support request? If the answer is yes, then wait. (It normally takes up to three business days, but could take longer in some cases). If the answer is no, you did something wrong and nothing will happen. Jan

Not a built-in failure... possibly one in X-Plane (failure menu) or some clash with a hardware axis assigned to the gear lever? Cheers, Jan

Right - the generator switches don´t stay in an "on" position - they will default (spring loaded) to the middle position. To connect the generators you must toggle them to the ON position momentarily. I suggest to watch the tutorial videos on startup from cold+dark, they should clarify the correct procedure. Jan

Thanks for the information, Simon! We hope to get the patch to you soon, our lead developer in Australia was hit hard with recent flooding and is out for unknown time... Cheers, Jan

Hi, you are entering something that is causing the gizmo plugin to throw an error messge - a bug with the airplane. We are trying to fix these right now, and I expect a much better stability with the next update. For now, try to enter the routing in a different way - maybe look at the tutorial videos to give you an idea how they are usually entered, avoiding the crash. Important: Once you had a crash like that, you can NOT use the plane anymore, nothing will work. You need to reload the aircraft or at leas reboot gizmo (using the right.side popout menu). Sorry for the inconvenience, Jan PS: If you want to help us fix problems, make sure you write us exactly what you are trying to enter and in what sequence so we can verifiy and fix your bug.Thanks!

Hmm, I have no idea what happened to you, just some ideas: Maybe you crossed the wake of another (AI) aircraft? The wake turbulence is modeled in X-Plane. Is your joystick "spikey"? If it sends erroneous data to X-Plane, the yoke will move (even without disconnecting the autopilot, this only happens after passing a certain deflection threshhold). Do you have X-Plane´s internal "failures" engaged? They will disable control surfaces as part of their failure repertoire... Cheers, Jan

AND you can output the "icing" datarefs to your screen, if you want to really know if you pick up any ice or not. Jan