Litjan

Hello Vincent, I would like to hear about the indication lights that are missing with some failures? Be aware that we are not simulating failures per se - so if you trigger an X-Plane failure, only very few will work correctly in the IXEG 737. Mostly because we are simulating the systems with custom code - so if you "fail" the generator bus in X-Plane this will have no effect since we don´t use some of the X-Plane systems. But if you switch something off in the cockpit and the corresponding warning lights don´t light up (example: Turn off fuel pump and the corresponding low pressure light doesn´t shine), this I would like to hear about as it would constitute a bug. Yes, I miss the hold function as well - but if you are really a real 737 pilot and have trouble flying a holding with HDG SEL please let me know which airline you work for so I know what to avoid in my future travels. Sorry for the snidey remark. Jan

Correct - not yet. Cheers, Jan

You can not open the doors - only the door from cockpit to cabin and the two cargo doors. Jan

You need to create an exemption for Windows Defender. Exclude the whole X-Plane folder from the "live scan" - it makes in and out operation (during modifying the FMS route) very slow. Cheers, Jan

Most likely you have a "combined" autoflight mode active - this will actively "seek" the assistance of the autothrottle - for example FL CHG (it asks full throttle or idle power) or the TOGA mode (asking full throttle). If a mode like this is active, "arming" the autothrottle will immediately "activate" it as well. But also simply being in ALT HOLD will still engage the autothrottle if you arm it. Think of it this way: When I flew the 737, there was not a single minute during my flight where the autothrottle was not armed. It was NEVER off. Always at least armed. That way it was always "ready" to help when the autoflight system needed it - especially in an emergency, like a go-around (TOGA mode) or during a speed reversion (preventing stall or overspeed). Jan

1.) Well, you COULD engage the autopilot on the ground in certain modes (like HDG) and it would try to steer the aircraft (with the ailerons, so it wouldnt work). I am not sure if engaging LNAV would work. "Arming" LNAV does not work in the 737 classic, unlike in the NG. So you have to take off with the TOGA flight-director mode (HDG and speed pitch mode) and then engage LNAV when airborne. 2.) You need to ARM the autothrottle (move the little switch to UP), but not ENGAGE it (big difference, as you have found out). Since there is some danger of accidentially ENGAGING the autothrottle, it is procedure to not ARM it before entering the take-off runway. You may want to watch the tutorial videos I made, I explain a lot of stuff like this in them. Cheers, Jan

Hi XL, maybe your problem is related to this: Let me know if changing the nosewheel spring force to 0 as mentioned above helps, please? Cheers, Jan

Yes, it is modeled (it will prevent/remove ice buildup) and it will also affect the air bleed pressure, but no, it has no effect on the EGT. Cheers, Jan

Glad you found the problem - the draw vortices option will be disabled with the next update! Cheers, Jan

Yes, a lot of time the "parental control" is a problem with our plane - it is just so much more addicting than Fortnite! Cheers, Jan

Yeah, sometimes stuff can go wrong during installation with weird effects. Glad that the reinstall fixed it for you! Cheers, Jan

The stability setting may very well be your problem. We STRONGLY recommend to run the plane with artificial stability set at 0. It´s not realistic to use artificial stability at all, and in fact it can interfere with controllability (as we may see in this case). You can play with the joystick response curve if you feel the plane is too sensitive - this would decrease control deflection for a given joystick deflection, which is more what you are looking for. But the artificial stability is a "training wheel" and "instructor is gently holding his set of controls to help" type setting. Let me know how that goes! Jan

Hmm, I just tried again - for me there is enough rudder authority to regain the centerline when an engine fails at V1. (100.000lbs takeoff weight, full N1, V1 at 120 kts for flaps 5). However I agree that the onset of the yaw is very sudden and I deviate from the centerline too far before I can compensate. I am unsure what the reason is for this. The physical forces at play seem to be correct, as there is enough authority (for me) to not only counter the yaw, but also enough to steer back to the centerline against the working engine. It could be that the engine failure in X-Plane is very "sudden" (vs. a more gradual thrust decrease in a real engine failure). It could also be that we are missing the "seat of the pants" onset of yaw cue that you certainly have in a real aircraft, which allows you to react faster/instinctively. There is also the possibility that recent updates to X-Plane have changed yaw forces (better ground friction) to make the airplane depart the centerline faster. I will look into tuning this a bit for the next update - we calculate yaw forces while on the ground within our own plugin (bypassing X-Plane, as it´s ground model is still not acceptable for the fidelity we look for), so it should accomplishable with a code tweak. Cheers, Jan

It is a known bug brought about by changes to the engine modeling in recent X-Plane updated. Cheers, Jan

It is not possible yet. Cheers, Jan

Or - as we say in german: "Again what learned!" We usually aimed to set N1 = grossweight in tons during landings - if reversers where allowed. So for a landing with 45t we aimed for 45%N1. But the reverse thrust levers worked just like the forward thrust levers - no notches (unlike on that "other" aircraft)... Only difference is that you can´t "overboost" the engines in reverse, they were limited to a safe maximum reverse value. Mostly because you can´t afford to fiddle and look down when you are in need for maximum reverse thrust . Cheers, Jan

I just checked in X-Plane version 11.31r1 and it works just fine for me. Make sure: to run the latest version of X-Plane to NOT run any third-party applications that change the way X-Plane looks (like XVision, etc.) Cheers, Jan

Never heard of reverser stages. The 737-300 does not have any. You can set any N1 smoothly between high idle and max. Cheers, Jan

Hmm, ok - this sounded like the other bug another user reported - he was using ActiveSky, I think - and that one seems to have a problem with generating "turbulence" and there is also seemingly a problem loading wind layers into X-Plane 11.30. Not sure about VATSIM. I haven´t encountered anything like that, but I don´t use real weather and I could imagine that if there was a problem with loading real-weather-wind-layers (as it is reported for 11.30) then going from one layer to the next could make this happen. Cheers, Jan

My guess is that you used a third-party weather injection program like ActiveSky or so? Jan

Glad we got this sorted out - we are always bound to have compatibility issues like this as developers of all add-ons work on the cutting edge of whats possible with X-Plane. Sometimes it´s hard to say "who is to blame" (cough - show vortices - cough), but it helps to find out and reproduce these conflicts and let the devs know. Thanks, Jan

I just did a daylight flight in VR (Oculus Rift) from LFMN Nice, France to EDDF Frankfurt Germany without observing the effect described. Cheers, Jan

Thanks for the added clarification! I will check during daylight flight today! My money is on the silver lining plugin. There are a few new problems in 11.30 with add-ons that mess with art datarefs that did not appear before 11.30. One example is our own "show vortices" option - it worked ok pre 11.30, but was really a borderline "hack", and doesn´t work with 11.30 anymore. Laminar will not maintain compatibility with these plugins on the way forward, because it considers them unsupported code to be done at your own risk. So there is a good chance I won´t be seeing this (and so far you are the only user) - and if I put this up with Laminar, the response will be "try without ANY addons installed and see if it still happens. Then add them back one by one, see which one causes it and take it up with that dev!" Cheers, Jan

The GPS receiver on the plane modeled is part of the EGPWS card, which was retroactively fit. It´s signal is then sourced into the FMS. You can see the GPS capability when selecting the second page of the POS page in the FMS. There is no indication of GPS anywhere else, not even a circuit breaker. I don´t know what they file in the U.S., never flew there (on the 737 classic) - and even IF I did I would still have no idea because I never even looked at that code in my life ONCE. Jan

I tested this for a few minutes and so far it works fine on my system. Now you said that it takes a while to show up - I will run some longer tests tomorrow to see if I can reproduce this. Do you have any addons installed like XVision, Xenviro, etc? Or do you run a clean installation? Thanks, Jan