Litjan

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

Thanks for the report - I will try to verify your findings and report them to Laminar Research. Cheers, Jan

Well, let me think... It was fine before. Then you installed Xvision. Now it is not fine anymore. Hmm, I need to think over this some more...

The aircraft portrayed (and the ones I flew) have a single GPS receiver - therefore they are GPS approach capable (LNAV minimum - not VNAV minimum). The FMS portrayed is not capable to comply with the newest navigation standards, i.e. it can´t fly arcs with defined radius. Cheers, Jan

Thank you for the nice words and lets see what the update for ASXP brings! Cheers, Jan

Do you have HDR on? Jan

LOL. There is no weather phenomenon like that in the real world - not a microburst, not a hurricane, not a nuclear explosion! You are loosing like 200 kts in 20 seconds - I am not sure what kind of weather you are injecting or what ASXP is doing - but the next time you see your airspeed drop like this, fly the airplane, instead of looking at the overhead panel and working the anti-ice switches until you are in a deep deep stall with no authority on your flight-controls due to lack of airspeed. Immediately put the nose down aggressively, if you have to cut the power to idle to bring the nose down... but first check whats wrong with that weather depiction - the real wind aloft does not change over 100 kts in a few hundred feet, airmass friction will not allow that. Cheers, Jan

Hello novato, normally the anti-ice function of the IXEG 737 should clear out any ice from the engines and the wings. Make sure to turn on both engine-anti-ice and the wing-anti-ice. I don´t have ASXP, so I am not sure if they model ice accretion that could cause what you describe. Even without turning on anti-ice a descent of a few thousand feet should have brought you into warmer air that would have melted the ice, so I am sure there is something wrong with what you have seen. You can output the "icing status" to the screen in numerical values (look for the data out tab and search for "icing" to find the right data to show) - so you can see the icing status of your aircraft and what effect the anti-ice has. Cheers, Jan

Agustin, I need to see the FMA anncouncements in the EADI (the green/white writing on your artificial horizon) to see what is going on. The light in the VNAV button does not say anything about the status of the autopilot. The light only says "this mode can be disengaged if you click the button". If you are in VNAV PTH at a certain altitude and then dial the altitude away (like you did), the mode changed to VNAV ALT. This is not really a VNAV mode, as the autopilot is maintaining the last altitude it held as a safety feature. If you turn the altitude knob DOWN (like you did) while the FMC (and VNAV logic) wants to climb, it won´t engage. I am not sure how elaborate the VNAV logic on the Zibo mod is, I don´t have it or fly it. Jan

Sorry, I have no idea what could be causing it - it works as expected (within the limitations of how - imperfect - we modeled it) for me. Make sure the PERF INIT page is fully filled out and that your joystick is not spiking. Also if you are too far away from the vertical profile, VNAV can not engage. Remember that the FMC is a computer from the 80s - not an iPhone. It will often not tell you what is wrong, with no warning or explanation. Back then the coders expected the user to learn all the limitations and rules when using a computer system. So often sometimes something simply "will not work" and you can´t really tell why. Another good example is the dual-channel autopilot approach. If one of the requisites is missing (like second ILS tuned), the second autopilot will simply not engage. There is no warning message or explanation. It simply won´t. You could often see real pilots sit in the simulator when doing the CAT3a part of the checkride scratching their heads over this.. So without looking at you performing the setup and flight I have no way of telling why it won´t work. But I have a good piece of advice from the real cockpit: If something doesn´t work, do something else that does work. Cheers, Jan

For what its worth I just tried and I can mimic Catstrators effect exactly by turning on the "draw vortices" option. It happens at certain lighting levels, appearantly. With the option OFF everything is fine. Please let me know if you find out that it still happens with the effect OFF! Thanks, Jan

Thanks for letting me know, mikehatch. I will doublecheck on my own installation to make sure we don´t have a new bug with 11.30... Cheers, Jan PS: Please also specify if this is happening with HRD on or off and also if you are using any weather addons (Xenviro, etc.) or other tweaks that change the way that X-Plane looks (lighting, colour, etc.)

Don´t use stability augmentation! It should be a 0. Cheers, Jan

No problem - as far as I know there are no commercial aircraft that are capable (or even legal) to take off with the autopilot on...not even the A320! Here are the training videos: Enjoy, Jan

It is obvious that you have the autopilot engaged during takeoff - annd as designed it will try to do what it is told - and when you push TO/GA the lateral mode "HDG SEL" (heading select) will automatically engage. Now the autopilot will try to fly the heading you have dialed in - on your picture the heading bug is at 089, almost completely behind you. So this is not a bug, it is 100% user error. I advise you to watch some of the tutorial videos on how to fly the 737 - the autopilot is never engaged for take-off! Cheers, Jan

You need about 15 minutes for the IRS units to align - that is the limiting factor, timewise. The startup of the systems and engines can be done in less than 5 minutes. If you want to do everything realistically (checks, tests, including programming the FMS) you would need about 15 mins altogether. Cheers, Jan