Litjan

The standby horizon is on the Battery bus - but the standby altimeter and the standby airspeed indicator are on the standby 28V DC bus. I remember hearing the "woodpecker" (standby altimeter vibrator) come on in the morning when we did the standby power test (this test was removed from the normal cockpit preparation procedures sometimes in the late 90s). The standby power in some models (newer ones) will also be on on the ground - you don´t need to move the standby power swicht to BAT to enable it. In the older models it switches off when on the ground to avoid draining the battery too fast if the pilots forget to turn of the BAT switch after leaving the aircraft. So in those newer aircraft the standby power buses are always powered when the BAT switch is on and the GEN buses loose power. I think what we don´t have quite correct is that you can also hear some "airflow" or "cooling fan" noise when the standby altimeter vibrator comes on. This is a problem with the sound file...I recorded it in the real 737 when the aircraft was powered normally - so you can hear that equipment cooling fan sound in the background. In the real aircraft you would only hear the vibrator sound. Cheers, Jan

The sound that you are hearing is most likely the standby altimeter vibrator and the gyro of the standby horizon? Cheers, Jan

Hi Xiropillo, I can not confirm on my end what you are seeing - but we used to have a bug in the standby power distribution when the aircraft was on the ground, if I remember correctly. Tom has fixed that, but I am not sure if it went into the last patch... When you are on the ground, switching on the BAT switch should power the Battery bus (the hot battery bus is always powered). When you move the STBY PWR switch to BAT then the standby buses get powered (both AC and DC) - and you will additionally gain the standby instruments (like CPTS altimeter, airspeed, and EFIS displays). You should not get power on the generator buses - this is easily confirmed by trying to turn on the ELEC HYD pumps, for example. They only work when the GEN buses are powered. This is the behaviour with my version - but again - maybe the latest release version did not have that fix yet. Cheers, Jan

My guess is that you forgot to switch on the air conditioning packs - it is hard to tell because only a very small portion of your panel is in your screenshot. If the cabin altitude becomes excessive, the pressurization will fall back into standby mode - but even that will not help, as there is no source to build air pressure in the cabin. This is pretty much the scenario that caused the crash of the Helios 552 flight. Cheers, Jan

The purple bars ARE the flight-directors. Of course you need to turn on the FD switch to see those - but they will only show if they also "direct" something. In other words - you need to have a mode working for them to direct you. For example you could only have HDG SEL engaged - then only the vertical director bar would show...since there is no pitch mode "directing" (no horizontal bar). Jan

This is in fact quite complex. The autothrottle will work without the flight director. You can use it in N1 (full power) and MCP SPD mode. Just push the corresponding buttons on the MCP. It is also dormant (when armed) to trigger when the TOGA buttons are pushed or when the speed protections kick in. To actually have the autothrottle work in the COMBINED modes, you need to have the FD or AP on. Then - if a COMBINED mode triggers, the autothrottle will respond as well. For example: You push the FL CHG button on the MCP. This is a COMBINED mode which will engage the pitch mode (of FD or AP) to maintain the speed set on the MCP but will ALSO (thats why its combined) trigger the autothrottle to go to N1 (for the climb) or RETARD (for the descent). Cheers, Jan

1.)Extending the flaps to 1 is generally enlarging the wing area to the rear with very little curvature added. That is why the center of lift is moving backwards - producing a nose-down momentum. It is actually quite pronounced in the real aircraft. If you don´t counteract the nose-down trim shift the nose will actually go down and the aircraft will loose lift as a consequence. 2.) When you start the APU, the generator buses (which are powered by the ground power) are not used - only the battery can produce enough current to start the APU. Thats why you see the high discharge and also why all the lights connected to the battery bus will dim during the APU start - even with ground power connected. Cheers, Jan

Hi Dgyu, try to "output" your joystick values to the screen - that way you can see if your joystick axes are indeed center (value 0) or if they are off-centered or spiky. Go to the tab "DATA OUTPUT", then click on the leftmost field in row 8 (Joystick Aileron/Elevator/Rudder). In the IXEG Preferences pop-out menu move the slider for "Joystick CWS Deadzone" all the way to the right. Also doublecheck if the hardware profile that is assigned in X-Plane to be used with the IXEG 737 is the correct one and that no conflicts with other axis exist. Let me know what you find out, Jan

Hello Eduardo, could it be possible that you assigned an axis to throttle by accident (or automatically) on your joystick or other hardware? In that case this would always "override" your other attempts to move the throttle. Some hardware has additional little devices that count as "axes". Also be aware that X-Plane nowadays has different "profiles" for the hardware that can change from aircraft to aircraft - so one plane may work fine and another may not because the profile changes. Cheers, Jan

Alright, I am pretty sure that this will be your solution - increase the setting for that center null area. The real 737 has either the mechanical lock-out bolts that you can hear whenever you move the yoke (click-click-click....) or the engagement is locked out electronically on the more modern MCPs (which we model). Cheers, Jan

Thanks for the clarification, Tom! I wonder why we didn´t see this one before... I will put it on the bug list. Cheers, Jan

Hello Eduardo, the throttle should normally work - unless it is being operated by the autothrottle mode. In that case only the autothrottle can move them. When you disengage the autothrottle, you need to re-align your joystick throttle with the 3D throttles in the cockpit (synchronize them) - for this we provide a "ghost throttle" that shows your hardware position until you "grab" control of the 3D throttles in the cockpit again. Let me know if that helped? Jan

Thanks for the feedback - I will let LR know. Jan

My money is on your joystick being not centered when you try to engage the autopilot. This is modeled according to the real autopilot which can not be engaged when the control wheel is deflected from zero. You can adjust the size of this "zero zone" in the preference settings, if you have a spiky joystick this may be necessary. Let me know how it goes, Jan

Ok, I am seeing the exact same thing...I wonder if this bug has always been there or if it was introduced by a recent update. Fabiosko, you said that you only saw this happening after updating to 11.41? Thanks for any further info, I will file a bug with Laminar Research... Jan

Ok, interesting - I will see if I can reproduce it on my machine! Thanks for the report, Jan

Unless you have a hardware (or gfx driver) problem of some sort it has to be something you added to X-Plane beyond the vanilla install. Your report is the only one regarding this problem - if it was a systemic one we would get more reports on this, I am sure... Cheers, Jan

Turn OFF the option "show vortices" in the IXEG preferences menu. It is not compatible with the latest X-Plane versions anymore. Cheers, Jan

Yes, this is the only time I have heard about this - are you running some sort of lua script or anything else that changes the artwork or light intensities? Let me know how the further troubleshooting works out, but I don´t know what else could be causing this... Cheers, Jan

Hmm, the landing lights should have no effect on cockpit lighting...are you running with HDR on or off? Cheers, Jan

I have never seen those - maybe they are the "cockpit tooltips" that come with X-Plane? Or you have installed something else that is causing that. Maybe someone else knows?

Hi there - I once had a similiar problem when trying to download ActiveSky - it turned out that the problem was the way my computer was hooked up to the internet - I had basically two routers to pass through, and once I hooked my computer directly into the first one (bypassing the second one) it worked ok! Maybe something to try... Cheers, Jan

Mmerelles is right - the PROG page is not working properly - we have not implemented an accurate fuel planning (including wind, enroute fuel burn etc.) so the page is just showing some rough values... The ACARS function will not be implemented, it won´t work without simulating a background "operations" backend that would provide the info that ACARS usually shows. The used fuel button and reset fuel buttons should work - note that you need to press it for a while and I think you need to have the engines shut down or be on the ground or something like that (just like in the real aircraft). It is normally only used during the preflight cockpit preparation, not in flight. Cheers, Jan

Hi Mike, it could be that your gizmo plugin is not working - because something went wrong during the installation, like a wrong path specified or such. The default startup state for the 737 would be with engines running - if it starts up looking "dead" that means that you have not installed it correctly. The DRM is the "digital rights management" query where you have to enter your unlocking credentials to register your computer and unlock the plane. Cheers, Jan

Hi Mike, this is the first time we have encountered this issue without being able to solve it with the above steps :-( I really don´t know what else to suggest, in a "normal" configuration moving the mouse against the left top and right top screen edges should result in the menues popping out. Is the aircraft running normal? DRM registration worked? Are you running any sort of third-party programs that change your mousepointer, Windows desktop, etc? Cheers, Jan