Litjan

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

I do not remember. But I think it works the way we have it now. Jan

Thanks, Pierre - let me know what happens. I think the lateral distance is set to 2.5NM - so whenever you pass by a waypoint further than that, it will not sequence. We will tweak that in the upcoming weeks, for now when it happens just fly direct to the next waypoint (insert into LSK 1L, execute) Jan

Thanks, will try to find some more info on that... Jan

No, it is not modeled on this aircraft. Jan

That is right - the switch is held up magnetically in the up position when the parameters are met (power to the autothrottle computer, etc.) - when you push the disconnect button, this power is removed, the magnetic solenoid releases the switch and it is springloading to off. It will also disconnect 2s after touchdown, for example. Jan

While that is a relief for us - I still hope that you can get it sorted out to enjoy your virtual aircraft! Good luck, Jan

Hi guys, this was something we changed during development - initially we had the EXEC button light up (just like in the tutorial video), but later we decided that it should only light up when there is a route that can be executed. In a way the EXEC button is the trigger for the FMS to start "working with the new route". And if you only input PERF data without a route, there is nothing to "work with". So once a route is activated, changing (or even entering anew) any value on the PERF INIT page will give you an EXECute light, because now a route will be influenced by your changed performance parameter. If you don´t have an active route, you will not get the EXECute light. Jan

Hi guys, thanks for the nice words and feeback - I think we are getting to the point where the plane works reliably and satisfactory within the limits of what we set out to do. Next will be adding the "missing features" as outlined in my initial post about that. We will spot/introduce some bugs during this process for sure, and I envision us doing the odd hotfix until 1.1 - but they will not be coming at a weekly basis, but rather "when having enough to warrant one". Please continue to report all findings, it is easy to get accustomed to little peculiarities, but we want the plane to work as the real one does, without having to "work around" or "avoid" certain things! Happy flying everyone, Jan

Thanks, poodster, I will verify and add for the 1.1 list - we can´t fix stuff like that in a hotfix, but it will go into the first real "installer" patch. Jan

Hi Tony, if you want to do it correctly, don´t use the disconnect buttons. The A/T disconnect buttons on the sides of the throttles are not used in normal flight, instead you disarm the speed mode just like you did. By disarming the A/T alltogether, you disable the speed reversion protection modes, too - something deemed too dangerous when carrying over 130 passengers ;-) I could imagine that you are flying in very bumpy weather, and the speed mode is re-engaging in speed reversion mode to stop the airplane from going too slow or too fast? I would really need a video to see what is going on. Also notice that the speed mode will automatically engage whenever a new pitch mode (alt hold, GS, vertical speed, etc.) engages, this is normal and a safety feature. Jan

Correct

We are aware but have not been able to figure out how to fix it. Maybe you can ask with the maker of the VATSIM light .pngs. For now we have only found out that using HDR makes them square, but not why... Jan