Litjan

No, you have to send me one of your homing pigeons, and I will let if fly to you with a message about the new update when its done! Jan

Yes, you will get a notification by email.

Yes, we are fixing a couple errors in the LNAV code that would cause this. I think you should see almost all of these gone with 1.1. For now, keep watching the AP like a hawk!! Cheers, Jan

Hmm, let me guess, you are using XP11 and you are not reading many forums related to XP11, right? Here, let me help you with that: http://forums.x-plane.org/index.php?/forums/topic/110304-ixeg-737cl-and-more/&page=2#comment-1134164

Hi Jan, Thanks for the kind words - I know some planes are affected, and I know that the "default" aircraft in XP11 will be working fine again in the next beta... The payware aircraft will be updated when XP11 is final - Ben Supnik told everyone to wait until then. Cheers, Jan

Working on it! Au revoir, Jan PS: Day before yesterday fixed some bugs with Nils on the TCAS (some online-traffic staying fixed in position relative to aircraft, erroneous RA´s when X-Plane AI aircraft spawn....) Yesterday fixed a bug with Tom relating to aircraft not flying straight to first point on SID´s with long, straight initial segment (like LFPG 27L RAN1AD, for example)...

Yeah, we override the setting that X-Plane provides (at least we try to) - happy to see that you got it sorted. Jan

XP11 not supported yet. Cheers, Jan

We may revisit this at a later stage. The problem of A/T not setting correct thrust in some conditions is also on the review list. Thanks, Jan

Thanks for the nice feedback! We will need to re-tune the aircraft when XP11 is "final" - if you feel REALLY enterprising you can do this: Disclaimer: All this at your own risk. Don´t come crying if you *** up your aircraft and run out of activations because you need to re-install your messed up aircraft file. FIRST: MAKE A COPY OF THE .acf file!! Run the aircraft in XP10 at a certain speed and altitude, i.e. 5000 feet and 250 kts. Output "drag" to your screen. Note the value. EDIT: At 250kts, 5000´ and 100.000lbs (45.450kg) this should be 6460lbs of drag. Open the aircraft in Plane Maker for XP11 (root folder) and browse to Standard/Fuselage/Section Play with the value for "body coef of drag" (you will need to increase it) until your results for 5000 feet and 250kts match up with XP10 (6460lbs of drag) The results for other speeds won´t be perfect (since the shape of the drag curve has also changed for XP11) - but will get you back into the ballpark. Jan

XP11 is not officially supported. Lots of changes to drag, so this is not surprising. Jan

Excellent, happy to hear that! Happy flying! Jan

So I guess G-Data was the problem? Can you confirm that its solved for you now?

Thats the spirit!

Czien dobre, marpilot, Are you running X-Plane on an external disk like a USB stick, a memory card or a mobile harddisk connected with a USB cable? Are you sure you have excluded the whole X-Plane folder for ALL antivirus programs you may have running? Many users have installed some programs "by accident" that they don´t even know about like avast antivirus etc. I am positive that it is a problem specific to your computer, and not a problem with the plane, as thousands of other users are running it just fine. We will try to help you, but ultimately you have to find out what is slowing down access to the navigational database that is residing in the X-Plane resources folder. Jan

Hi Michael, the "bleeding off" is certainly academic/legal, and a prerequisite for landing-distance-calculations to be legal. The shorter the landing distance in the book, the better the plane sells. So it is advantageous to calculate touchdown with "Vref" instead of the minimum Vtgt of Vref+5. If you are approaching in high (and usually gusty) winds, it would require you to pretty much retard the thrust levers to idle when crossing the threshhold to bleed off 15kts of speed additional until touchdown. A recipe for disaster, as there would be no instantaneous power available in case of a sudden drop-shear or required go-around (spool times). And usually landing distance is not a factor for the 737, especially not in situations with strong headwinds. If you approach with a solid speed additional, you will need to fly the plane onto the runway, taking care not to bump the nosewheel first (usually you will fly with Flaps30 to give you a better controllability, anyway (higher speed -> better control, less driftangle). Chop the thrust levers at touchdown. Jan

Boeing recommends to add half of the headwind component + the full gust factor. The minimum additional to the Vref is 5, the maximum is 20 kts. So the additional for you would have been cos(75deg) * 31/2 + 9 = 4 + 9 = 13. Your approach speed would be Vref (140) + speed additional (13) = 153. You would fly this value (153) until passing the threshhold, then bleed of the steady wind component but keep the full gust factor. Target touchdown is 149. Jan

This seems to be a result of a new jet-engine tuning for pb12 of XP11. The engines idle too low, and can not accelerate from this low RPM. You can adjust that in planemaker: Open "Plane Maker.exe" in the main X-Plane folder. Click File - then Open then load the IXEG 737-300 Click "Standard" then "Engine Specs" find the "lo idle fuel adjustment" and increase the value until the idle RPM is about 22%N1. (I don´t have this installed on my laptop, but the current value is probably 0.6 and you may want to increase it to 1.1 or so...) Hope this helps, Jan

I guess the biggest problem in this case was that you did not engage the autopilot. You can still clearly see FD in green on your EADI - it would be CMD if the autopilot was flying... Jan

Thanks for reporting back -. and of course your kind words! I am also currently flying the A320 in the real world - but I miss the 737 very much! Happy landings and don´t get caught up in the high winds these days! Cheers, Jan

Hi, yes, that is likely the cause of the "UNABLE CRZ ALT" - another message you may see is the "CHECK ALT TARGET". UNABLE CRZ means just what you said - the route is deemed to short to make the cruise altitude. You may either change the CRZ alt, or you can simply clear the message and continue regardless. The CHECK ALT TARGET means that your MCP ALT setting is in disagreement (direction) with your set cruise altitude. For example you are flying at 10.000 feet, your MCP ALT is set to 5000 but your CRZ ALT is set to 35.000 - if you try to engage VNAV it will throw that error... Hope this helps, Jan

I have to try it, and I think it used to work correctly: The trailing edge flaps can be extended and retracted with the toggle switch. The leading edge flaps will only "fully extend", but never retract. Extending the leading edge flaps is achieved with the "standby hydraulic system", which will start to operate when the alternate flaps switch is activated. Jan Edit: I just checked, and it works correctly. If you can find it work in a way it should not, please make a short movie and post it for me to look at. Thanks, Jan

I agree that this thread is hard to find (it is only the second pinned topic in the "bug report" forum, with the cryptic title "Solution to freeze and stutter when modifiying the route in the FMC" - but I will give you a hand and find it for you - heck, even copy and paste a link for you! Ping me if you need any further help with that! Edit: Sorry for being sarcastic, and that you are having a problem with our plane. But we can´t really make the solution to the problem you encounter more obvious and prominent, I think. I don´t know what kind of "altitude error" you had, but with the solution mentioned in the thread you should be able to retain control and at least fix that problem... Cheers, Jan

...and you can reboot gizmo via the right-side pop-out window (the little flash symbol)... Jan