Litjan

I would put some money on the fact that the missed approach is containing a VECTOR... These go on forever. Jan

Hmm, this is very unusual - we have NOT seen any crashes to desktop so far that I can remember, so I would venture to say that something beyond our 737 must be involved... Jan

Because the file type is not supported...anymore . The reason and discussion is here: http://forums.x-pilot.com/forums/topic/10578-105-no-more-airbus-extended-coroute-flp/ Cheers, Jan

Oh no, there are quite a few excuses in the repertoire of an airline pilot. Birds, CB´s, bad LNAV coding...

Hmm, ok - very odd. Do you do consecutive flights - i.e. land, park the plane and then take off again? Jan

Hi Ethan, I am not expert on these logs - they are all just a bunch of characters for me ;-) I would suggest you start the standard bug incompatibility confirmation protocol. Remove all plugins except gizmo and pluginadmin, reboot X-Plane. Then try again. We found out 99%+ of all problems with this approach. Thanks, Jan

Hi, I can´t download the attachment you placed. Can you describe the crash? Was it a gizmo console opening, or X-Plane crashing to desktop, or the whole computer freezing up? Thanks, Jan

You can install aircraft wherever you want to - just navigate to the folder in the aircraft selection dialog. I am sorry, I am out of ideas. Jan

Thanks for the info - I will take a look at that! Jan

Most likely due to not having a valid E/D point, - i.e. having a route discontinuity. Or you don´t have the PERF page filled out. Or the MCP ALT is not set right. Do you get a message on the CDU when you try to engage VNAV? I suggest you work your way through the tutorials, I am sure you will find the step you are missing there. Jan

Nope, this is not what my Classic´s yoke moved like. Maybe the NG has faster flight-controls? Jan

No, if the autopilot and flight-director are off, the A/T will only kick in when it´s reversion modes are triggered. But if either AP OR FD (or both) are on, it will engage in MCP SPD on any pitch mode change - except for a FL CHG descent, in that case it will engage in RETARD. Jan

That´s why many 737 pilots find flying with the FD on tedious - you have to keep commanding "deselect SPD mode" to the pilot monitoring. Every time you change from FL CHG to ALT AQC, then again at ALT HOLD, when changing to V/S or FL/CHG or G/S, and so on... I think some airlines allow, or even encourage flying manually with the autothrottle in SPD mode - which I think is bad practice, because it leads to uncontrolled pitching because you never know when the A/T adds or removes thrust... Jan

We had a case like this before: http://forums.x-pilot.com/forums/topic/9778-after-update-strange-instruments-dispaly/#comment-100416 The guy installed the aircraft again into a different folder - now had two aircrafts sitting in X-Plane, both trying to run at the same time (that would also explain your bad framerate in the screenshot). Make sure you uninstall the aircrafts, and also make sure that you install the aircraft into the correct folder: X-Plane\X-Aviation (NOT INTO the aircraft folder)! Jan

Hmm - what kind of axis assignements do you have going? Any hardware assigned to the flap lever? Jan

Hi and thanks for the report! the conditional waypoints are a very hard challenge for the FMS. We will check this one out and see where things went wrong...but hey, in the end you would end up at RWY 04, right? Cheers, Jan

Thanks for the report and the detailed info! We will try to reproduce this error and fix it! Thanks, Jan

Hi cmb, I just checked - due to some internal FU at Laminar Research, the airport I submitted in December 2015 was not included with 10.45.... so what you are seeing is correct. You can download the package here, though: https://gateway.x-plane.com/scenery/page/KLAX Cheers, Jan

Hi André, we are simulating V10.7 Cheers, Jan

Hi André and thanks for the report! Oh, and welcome to X-plane, too! Yes, we are aware of a parsing problem with the Navigraph dataset we are having... Tom is investigating that! As for your disconnects, it is very hard to see what is going on without more info, screenshots or even better a short video. Some users had problems with setting the CWS deadzone too small (so joystick input would disconnect the AP), or flying past a discontinuity would also send you out of LNAV. We are simulating an older FMC version, so the NG´s will not always compare to ours... Happy flying, Jan

Hi Super27 and welcome to X-Plane and IXEG! I wouldn´t say no - but there is certainly more change from a -300 to a -400 than from a -300 to the -500. More overwing exits, different temperature control... In the future we would like to pick off the easy derivatives, but we have to weigh if the additional work is at least on par with the additional sales we would get from it. Cheers, Jan

Hi afcad, I am really sorry that you are experiencing problems and can´t fly the 737 yet. Your problem is very unique and most likely some sort of special combination of your hardware or software setup, mistake during installation or activation hickup. But let´s try to find out what is going wrong. What is the hardware specification you are using? What is the type of operating system, your CPU, your graphics card? Please remove all other plugins for X-Plane from the resources/plugins folder (except for gizmo and pluginadmin). Then reboot X-Plane. Please verify that your activation works and that you got the "your addon was activated" popup window after you activated? Did you report your problem to the X-Aviation store support system? Thanks, Jan

Not COMPLETELY right... you should be able to initiate a cruise descent by entering a lower cruising altitude. Or just use V/S to start the descent. Jan

This is how the manufactures wants you to do it: You calculate Vref. This is 1.3 times the stall speed at 1G. Now you add: 1.) At least 5kts 2.) Maximum of 20kts 3.) half the steady headwind component 4.) the full gust factor You fly with this speed until 50 feet (crossing the threshhold), then you bleed off the everything, except of the gust factor. Touchdown with Vref + gustfactor. Example: Runway 36, Wind is 300/20G30. Vref is 130kts 130 + 0.5x20x0.5 + 10 = 145kts. Touchdown with 140kts. Jan

It should look like this: Jan