Litjan

No - this is still a mystery to me. When you press the APP button with a localizer within capture criteria, the autopilot will initially bank towards the course you have set on the corresponding side. This would explain the sudden banking when you engage APP (and have additionally set the ILS frequency of the runway you are flying to, but NOT the corresponding inbound course). The autopilot has no means to trim the aileron or rudder, so if the plane is truly mis-trimmed after you disconnect the autopilot, something else must be at play. Do you have any other third-party plugins (fly with lua, etc...) installed? Again, to truly solve this I would need to look at a video of what is going on - texting here in the forums is like describing whats special about the Mona Lisa on a postcard... ;-) Cheers, Jan

Ok, that is the reason - you don´t push the APR button when doing an RNAV approach in this aircraft! It is not an A320 (thank god). You fly RNAV approaches in LNAV and VSPD (VNAV is not authorized). Cheers, Jan

Hi, the first thing that comes to mind is that you have set up malfunctions within X-Plane and a flap was not working. This would result in an asymmetric flap extension and a resultant roll. It is curious that you would get that (random) failure on two consecutive flights, though. To further troubleshoot this problem I would ask you to somehow take a video of the incident so I can check your flight for other possible reasons (icing, incorrect speed, asymmetric thrust etc.). Cheers, Jan

Guys, so far the track record of these issues has been pretty clear - in all cases there was some other plugin installed or other hard- or software problem on the users computer that made X-Plane crash when the IXEG 737 is running. At the risk of sounding like a broken record: Remove all your other plugins (temporarily) then see if the 737 runs fine. Then add them back (in batches) to identify the conflicting one. Jan

That looks very nice! Happy landings!

Glad you found the problem - it could be something as simple as your memory filling up over your session time, but I am not an expert on that. You seem to have 32GB of RAM, that should be enough, but then again you have more addons than I can count Cheers, Jan

It amazes me how much people can pile into their X-Plane installation and STILL have it running...without their computer imploding and turning into a black hole . Honestly, I can´t even begin to start speculating which of your hundreds of plugins and scenery add-ons may interfere with another one. You will have to try for yourself. Cheers, Jan

No idea, really (I can for some odd reason never see the attached log.txt files here) - if the whole simulator crashes then this is usually not due to our coding. Standard protocol applies: Remove all other plugins (not "firing them up" doesn´t count, you need to physically remove them from the Resources folder), then slowly add them back to see which one is offending. Quite often the offending plugin has a newer version available which fixes it´s behaviour. Another thought is running out of RAM - this often happens without even installing anything new, just by picking a specific area to fly in or having other processes running in the background. Cheers, Jan

Cameron is right - if you see the heads of the pilots in the cockpit it means that you have not activated your 737 with the authentification servers, the gizmo plugin is not running and all functionality of the plane is not working. Please follow all instructions for the installation exactly and activate your license for this plane, then it should work. Cheers, Jan

Hello Pateador, we have had some problems with the pop-out side menus on multi-monitor installations (XP10 and XP11 both). Often the reason was that the "bump" was not detected because the coordinates of the mouse are not detected correctly. Can you try to run the IXEG aircraft with just one monitor activated and see if that works better? Thanks, Jan

Hi, this is a known issue - it will be solved with the next update. One of the textures (mcp) was accidentally set to "outside glass" instead of "inside glass". Thats why it is affected by the outside light. No idea why its only affected by the turnoff light, though... Here is how to fix it: Cheers, Jan

Oh, thats 1.1400001%, then!

We are aware of it. The problem appears when you re-save the .acf file in a later X-Plane version...which is necessary if you want to fix the "steering problem" another update brought. So its a tough choice to make. We hope to fix this in an update! Cheers, Jan

Hello Robert - you are seeing the back of my head . This is normal when the Gizmo plugin is not running. But Gizmo is necessary to run the IXEG 737. Maybe you were running an old version of Gizmo? I think someone with more knowledge about the coding and Gizmo could chime in... Cheers, Jan

Hi Robert, I am totally at a loss what is going wrong there. My advice for you would be to try to run the IXEG on a clean, vanilla, totally no-other-addons or navdata updates X-Plane system. It may be that you have something interfering, like a wrong set of nav-data in the relevant folder or something else. We haven´t seen a crash like that when starting the aircraft in a long time (years) - so it must be something with your installation of X-Plane (other than the plane itself). Cheers, Jan

Hi there - we mimicked the flightcontrol speed of the real aircraft when making this addon. I have done countless flight-control checks in the 737 during my life, and it does take quite a bit to move the yoke from stop to stop. This is due to the mass of the flight-controls themselves (ailerons, spoilers and elevators) and the maximum speed that the hydraulic can move them. I know that there is some "out of sync" movement with a joystick due to this - because the joystick can move really fast. If we had allowed that - we would see unrealistic fast control response on our model. The Airbus family suffers from this effect in real life - the joystick (they call it flightstick, because it is no joy to fly that plane) can move very fast - with the flight-controls lagging behind. Thats why its hard to control an Airbus precisely in gusty crosswind conditions, pilots tend to overcontrol and they tell you to "move the stick less, the flight-control computer will keep it straight for you" - but that doesn´t work, really. I can fly the IXEG 737 as well as I could fly the real aircraft (whatever that means ;-)) with the current setup. There is a possibility that you have set up your flight-control response in a way that makes it not sensitive enough around the center...this would require quite large movements to have a solid effect on the flight-control-surface. Check your response curve in the joystick setup menu and make it more or less "linear". The trick to fly an airliner precisely is to use trim all the time - you want to be able to fly it with just two fingers on the yoke, really. Unless it gets really turbulent, of course - but even then its rare to use full travel - although it does happen in extreme winds. I can´t remember ever running against the stops, though - and I have landed the plane in some pretty bad conditions... Cheers, Jan

Its not that I am triggered or irritated - more amused and confused that someone who seems to think that X-Plane will be obsolete shortly is still asking for updates to it. I agree that we haven´t delivered on the updates to the shortcomings of the 737 as we intended to do - for reasons outside my control. But I think we have been transparent as to why that didn´t happen and apologized for it as well. I do not agree with your asessment that the IXEG 737 is not compatible with X-Plane 11.41 as you stated above. It is not using some of the latest features to full extent, but that does not make it incompatible. Jan

Well, this is what you said: "The bottom line is the base sim, in the FIRST ALPHA TECH build, is shaping up to run roughshod over XP and P3D. Don't be afraid to accept the idea that XP may be relegated to a distant second best flight sim again by FS2020. It's OK. Really." https://forums.x-plane.org/index.php?/forums/topic/198035-msfs-2020-update/&page=6&tab=comments#comment-1814359

Well, going by your statements in various other forums we don´t really need to spend any effort to fix them anyway, right?

Hi Gareth, thanks for investigating and especially sharing the results of that with us! Naturally there is no blame to place - sometimes things just don´t co-exist well, it seems - although we do (did) take care to not violate anything when writing the code of our 737. The 737 is indeed a labour of love - for no one less than for me - and while it certainly has it´s shortcomings, I am alway happy when someone enjoys it! Cheers, Jan

Hi there, we have not heard of any problems or incompatibilities with the newest X-Plane versions. To avoid a graphical glitch (not cockpit textures in certain situations) please do not use the "show vertices" option. If you experience crashes this hints at a problem with third-party downloads or your hardware (overclocking, damaged RAM, etc). The only way to find out is to remove all other plugins and then see if the crash persists. If it doesn´t then add the other plugins slowly to find out which one is incompatible. Let us know if you find out which one is the problem, please. Cheers, Jan

I would have to try and grab the sound somewhere without infringing copyrights - so I can´t just leech it off some other program. Let me see what we can come up with... Cheers and happy new year! Jan

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