Litjan

Hmm, I think they are just fine, compared to a real-world B733 flight-deck . Is your bright/dim switch on bright?

Thanks for the nice words. The most common mistake for the TO/GA mode is to NOT switch on both FD´s. The Takeoff mode won´t work unless you do, the go-around mode will, though. (Even pop up the FD´s automatically if they are off). VNAV is very flimsy, currently - it does not take changes or complex procedures well. So for now we recommend to use it with care, and revert to more basic modes if it doesn´t act like you expect. Which is exactly what you did, good piloting judgement displayed right there!! We expect to give VNAV a thorough overhaul after the plane was made XP11 compliant. So a wild guess would be sometimes next summer... Happy landings, Jan

Thanks for the report - yep, this should be fixed with 1.1, iirc Jan

When you arm the emergency exit light switch with the battery on, the emergency exit light will illuminate, making the whole cockpit bright. Thats what it is there for. Once the main buses are powered (APU or GPU), the emergency exit light (it is the white light on the back wall) will extinguish again. Jan

And further improvements are inbound with the next patch (1.1)...

Do you have BOTH flight-directors on? That is a prerequisite to TO/GA working.

Yeah, there is a lot of life in the 737-300, we are nowhere finished with it, yet. I personally could see a -400 and -500 (they are just variants) as an expansion. Not looking further than that for now. Jan

Hmm, very interesting... have you tried to bind a button or key to "toggle left thrust reverser" (or whatever this is called) and see if you can close it again, after it opens?

Yeah - and where is the brake chute on this lame excuse for a 737? And the RATO´s??? I want my money back, pronto.

Well, you can see that one reverses is actually open. So I wonder how that happened - do you maybe have a button mapped to that (by accident)? If you are running one engine at full thrust, and the other at full reverse - I wouldnt be surprised to see in the real world (on a wet surface) what you are seeing on the vid... Jan

All your bases are belong to us!

http://forums.x-pilot.com/forums/topic/11730-gizmo-updates-betas-mac-os-sierra-important/

Hi Jon, it looks like X-Plane crashed. I am not an expert, but the usual suspect is a conflicting plugin. Please post your Log.txt (main X-Plane folder) so we can take a look. IF you want to start troubleshooting, disable ALL plugins except for gizmo64 and pluginadmin, then see if it runs stable... I am sure we will find out what is going wrong... Cheers, Jan

Ok - then you either did it wrong or something is wrong with your computer setup. I have not had a single report of the sim freezing with our 737 AFTER users excluded the X-Plane folder from their antivirus. Maybe re-check carefully that all antivirus programs running on your computer are NOT checking the X-Plane folder. Good luck, Jan

Did you create an exception for your X-Plane folder like mentioned in this thread? Or this one: http://forums.x-pilot.com/forums/topic/12240-solution-to-freeze-and-stutter-when-modifying-the-route-in-the-fmc/ Jan

Thanks, I edited the original post. I couldn´t verify, as my computer is not affected by this. Cheers, Jan

One problem that comes up again and again is the seeming freezing or locking of the computer when adding a modification to the route in the FMC, like a direct-to on the LEGS page. Here is the solution. It is unlikely that we can fix this on our end, so I will pin this info. What: When modding the ACTIVE route in the FMC, the framerate goes down and the computer does not respond fast, anymore. Why: When the database for the navaids and fixes gets accessed, Windows Defender, Avast, and other anti-virus programs check the in- and out traffic for viruses. This slows the computer down a lot. Solution: Create an exclusion in your antivirus program, excluding the X-Plane folder from instant checking.

That is a very good question! I don´t know where to start. Really...

Yeah, I fully agree on your asessment of current VNAV status - but you can still fly them using planning and FL CHG or V/S (or - gasp - manual flight!)

Yeah, thats what I figured. Flew there quite a few times in our 747-400s. We always started one engine at a time when there (usually its two simultaneously) because of this very issue... Cheers, Jan

For me our 737 descends perfectly on VNAV as long as the arrival is not complex (no restrictions) and there is no wind. The plane plans and flies an ECON speed PATH descend very well (even more precise than the real aircraft, due to the "perfect" simulation environment). Jan

As long as you can get over 20% N2 you are ok. It is the lower limit to introduce fuel. I bet that the engine would still start OK even at 18% - you just need to monitor the start even more closely for a possible hot-start. But of course I would never do something like that, as it is against procedures . I would rather cancel the flight (if they have no air-start-unit) and send all 130 passengers into some shady hotel in whatever nice area you are that has a 7,300 MSL airport . Cheers, Jan

Poodster is right, the VNAV part of our FMS is not very good at handling multiple restrictions. And it´s certainly not designed to work like the Airbus´ one (thank god!) But to really be able to see what the problem was, we would need a lot more information. What STAR/Transition where you trying to fly? Can you post some screenshots, detailing the problem? For now treat the predictions of the FMS with a bit of doubt and be prepared to revert to a more basic autopilot mode to meet your descent restrictions. The aviation industry see the ill-fated dependency of unskilled pilots on "fully managed" automation with growing concern. Pilots need to learn their airplanes from easy to complex...not start with LNAV/VNAV and hope that the autopilot gets them to their destination in one piece . Don´t take the fun of flying away from yourself. Its not a movie to enjoy with your feet up and a box of popcorn . Cheers, Jan

Hi everyone, we would like to give all of our loyal customers a short update on the work going on behind the scenes. As you are all aware, we are working on patch 1.1. It will include a number of additions and fixes to our 737, some of which we hinted at in our sneak peak thread: http://forums.x-pilot.com/forums/topic/11745-spot-whats-new-v11-spoiler-alert/ We are not quite ready yet to release the full list of features and fixes, especially since we want to make sure that we can actually include the items in question and also run a more thorough test on this patch than we had the time for on the last "hotfix" type patches. For the same reason we won´t commit to an ETA at this point. As we draw closer to release, I will update this post with more info on 1.1. We know it has been a very long time without updates and we thank you for your continuing support in spite of this! Happy landings, Jan

It is actually the APU putting out less air pressure at high altitudes - and sometimes people forget to turn off the packs before they start the engines, too...