Litjan

No - but try to open the sliding window after putting the FLT/GRD switch to FLT(with packs operating). Edit: To FLT, obviously.

The reason and explanation is in the post above yours . The reason for the "pressure bump" Hotdawg mentioned is that the outflow valve would be in the "far open" position, leaving a big hole in the aft lower section of the fuselage. As the plane rotates, air pushes against and into that hole, creating (uncomfortable) overpressure in the cabin. If you place the switch to FLT while still on the ground, this hole is almost closed, as the outflow valve is almost closed. Another benefit is that the cockpit sliding windows do not "rattle" in the guiding rails, they are pressed firmly into their sockets by the overpressure. Cheers, Jan

That is still planned.

The ELEC pumps usually stay on "all day" - you turn them on in the morning (before the first flight) and then shut them down in the evening (when leaving the aircraft). You need to have clearance from ground personell to turn them on, often the guy doing the outside check will knock on the plane skin and then give you a thumbs-up when all flight surfaces are clear (because they can move when turning on the ELEC HYD). You do need AC power to turn them, so you will need GPU or APU supplying the main AC buses. They are turned on very early in the preparation, because running them has the advantage of supplying power to the brakes (in case the accumulator wears down during extended ground time) and also being able to spot leakage during the outside check. You will normally not turn them off during "the day" - the only reasone I can think of right now is the supplementary procedure "Push back with no bypass pin installed" - where you need to depressurize the A system during pushback. Cheers, Jan

Ben is right - the headshaking is simulated by moving the camera position in the cockpit - when using VR, the camera position is overruled by the VR headset.

No new advice, really. The navdata packages from Navigraph and Aerosoft have installers that let you specify which add-on you want to install navdata for. After you provide the correct path it will install the navdata into the correct subfolder: /Aircraft/X-Aviation/IXEG 737 Classic/fmc_data Good luck! Jan

The good thing is - the 737 Classic does not have any brake temperature indication . On the A320s I fly these days we are not allowed to take off if brakes are warmer than 300C - and this can be a problem when taxiing out for a longer distance. Fortunately we have brake fans on those that we keep running, still when going to runway 25 at EDDS on a warm day with a heavy 321, it can be a problem. tl;dr: Idle thrust is fairly high on high-bypass engines and most pilots wish it was less...in real life, too.

Hmm, I am not an expert on how those variables work, but it seems strange to me that the blue GRD PWR AVAIL" lights up but the switch doesn´t work... I agree that it would be nice to be able to access this - and other options - in VR as well. The workaround I would suggest for now is to simply use the APU. There are no noise restrictions while flying in X-Plane and it can do everything that a GPU and ground air can do as well. I have placed the request for a programmable button/key into our list of enhancements again - it will probably be a quick addition, but I can not say when the next update will be available . Cheers, Jan

Nope.

That will work! (But you must then click the red flashing P/RST button with the mouse as well to silence the warning). Even better is to assign a joystick button to "AP disconnect" (I have to check the exact name of the command when I get home). You can click that twice (first to disconnect the AP, then to silence the warning). Cheers, Jan

If youi disconnect the autopilot the correct way (by toggling the AP disconnect button on the yoke) the FD bars will remain on. If you toggle the autopilot off by using the autopilot disconnect bar (like a lot of simulation pilots do erroneously) you remove power from the FCCs (flight control computers) and this will also turn off the flight-directors. This bar is only to be used in emergencies, like when other ways to disconnect the autopilot fail. Alternatively you can also use the autopilot engage/disengage buttons to disconnect the autopilot (or move the yoke over the limit, but this is really just another emergency way to do it).

You can fly without the experimental flight model, but downsides is less accurate performance parameters and lacking of some features unique to the "experimental" flight model, like refined downwash calculations. If you are a layman just droning around for fun, chances are you won´t even notice the difference. Cheers, Jan

You can use the preference slider to move it far "down" - to keep it out of view. Does that help?

When the airplane is very light, it will naturally have less rolling friction and will accelerate the most with idle thrust. Make sure that your throttle is fully at idle, though (sometimes hardware is not calibrated properly). N1 at idle thrust should be about 21%. A real 737 at idle thrust and light weight will easily accelerate to 60 or more knots... Cheers, Jan

Difficult to see...always in motion, the future is.

For the 737 Classic the IXEG is modeling you will set the orange carot to the barometric minimum. So for 08L at EDDM it would be at 970 feet. Back then when the plane was made pilots still had the ability to memorize the "thousand" of the DA/MDA . If you fly a CATII or CATIIIa approach with a decision height, you can set the RA DH window to the required decision height, i.e. 50 for a CATIIIa approach. In this case you will get a "minimums" callout. Some pilots set the DH to 200 for a CAT I ILS approach, but this is wrong. A CAT I approach does not have a decision height, it has a decision altitude. Therefore referencing a "height" (with the radio altimeter) could make you bust your minimum (if there is a valley in front of the runway, for example). This distinction is important. A HEIGHT is always a distance above the terrain, an ALTITUDE is a barometrically referenced altitude. There is no "decision height" for a LOC approach. A non precision approach (like LOC, RNAV, VOR,...) will have a MDA (minimum descent altitude). A precision approach will either have a decision altitude (DA) for CAT I or a decision height (DH) for CATII/III. There are approaches without decision height (CATIIIb), they will instead have an alert height (usually 100 feet RA), but the 737 Classic is not able to fly those. Cheers, Jan

I am sure we can, what is your problem?

I don´t think it is getting developed anymore...there are some versions floating around somewhere on the internet - but I am not aware of an official website or support forum.

Hi dongjin2, we use the standard X-Plane model for the autobrake. If it does not allow autobrake operation before the nosewheel touched down - therefore this is not possible with the IXEG 737, either. You could file a bug report with X-Plane to get the autobrake behaviour changed. Correct piloting technique for the 737 is to use spoiler on touchdown (autospoiler deploy, backup manual spoiler deploy), then derotate, then apply reverse thrust. The autobrake will also have a (short) delay before it activates, otherwise the nose would slam down. You are correct that the system behaviour is not exactly as in the real plane. Cheers, Jan

Unfortunately we won´t be able to fix XPUIPC, we don´t have access to their code and can´t patch it. Cheers, Jan

The autobrake system is working fine for me. Make sure that you don´t accidentally toggle them off by applying (manual) brakes. The autobrake system is supplied by X-plane logic, it is not a custom system. Deceleration rates are correct, though. Make sure to not accidentally disarm the autobrake by toggling the (manual) brakes. Cheers, Jan

Thanks for the nice words!

Hi! Yes, I have that tracked as a bug - and we hope to eventually add that functionality as well! Sorry for the inconvenience! For now please lean over and use the Captains CDU to do it. Happy landings, Jan

Not yet. You can easily make the necessary change in the .acf file yourself, it is not encrypted or anything. Just open it in planemaker, go to "Standard" then "Author" then click the checkbox for "Always Use Experimental Flight Model" - save and exit. Cheers, Jan

You only need to install the Navigraph data for the IXEG 737 correctly and it should work. There is nothing else to it. Maybe try to run the installer that comes with Navigraph data again, paying close attention to the options? I think you need to pick the correct data format and also the correct installation path. Which specific procedure is missing? You say a lot of them...that sounds like something went wrong with the installation, I think. Cheers, Jan