Litjan

Hi Daniel, we have had reports of the nav radios failing for some people - here is one case where it was probably some hardware interfering: Maybe you can try the "reboot gizmo" trick (little flash symbol on the right-side pop-out menu)? And the EFB turns on - tada - when you push the power button on it . (You are not the first one to not see that, no worries!) Cheers, Jan

As Cameron said. I have the sound for that ready, but it will be part of the "FMOD" sound upgrade which is a few months into the future...

Off the top of my head there are just a few minor differences. In the real plane the spoilers don´t have to be armed for the autobrake to engage - if this is the case in our aircraft then this is a bug (but I will have to file with Laminar to resolve it, as we use their autobrake system). I don´t think you can engage the autobrake after landing, at least I was not aware of such a function and it was not mentioned in the manual. If you try to move the selector to one of the autobrake settings with your speed above 60 kts would simply show the DISARM light. When the autobrake gets disarmed after landing (your points ii-iv) the DISARM light will stay lit until the selector is moved to the OFF position. Cheers, Jan

I see what is happening: The waypoint you are flying to was getting BYPASSED (means the plane could not fly over it because of the turn radius) - and appearantly this was by more than 2.5NM lateral distance, so the waypoint never sequenced (got deleted). The plane is - however - following the magenta track, it does not "know" that it missed the point. The cure for this is to fly "direct to" the point you are actually flying to - in this case ANC. Then the flightplan is "in sequence" again and the plane will behave normally. To avoid this happening in the first place, make sure that you have no "bypass" points in your route - often the speed of the plane is too big in that case, or the waypoints are at too acute of an angle. Cheers, Jan

I have seen font problems in relation to the X-Plane Vulkan API. If you are running X-Plane Beta 10.50 that could be the problem. It would be up to Laminar to fix that. Cheers, Jan

Hello Krzystof, you are right that the sideways traction of the nosegear is not as good in X-Plane as it is in real life. Laminar Research is aware of it and will improve it in the future. Like Iain said, it is important to keep the steering angle of the nosegear below a "critical" angle for it to work. Otherwise the nosegear will "stall" and just slide without much friction (gliding friction). To help with that: 1.) Keep your CG at 20% MAC or less (more pressure on nosewheel) 2.) Limit speed to <10 kts in turns 3.) Only move the nosewheel very slow and do not deflect it too much. It will not "steer more" if you deflect it past the critical angle. Taxiing a real airliner is very much about passenger comfort and you will feel getting "thrown left and right" much more than in a small plane, because you are so much further from the center of the turning point - so naturally you will apply and decrease tiller input very deliberately. I have no problem taxiing the IXEG 737 on dry surfaces when applying real life speeds and turning inputs, but I agree that the margin for error is much smaller than in real life. I hope that Laminar will fix this in X-Plane 12. Cheers, Jan

No it wasn´t. The root cause (in the new gizmo beta) has not been found yet. If it really bothers you, you can always go back to the stable version. I choose to enjoy the much smoother performance of the new beta and live with one gen bus not getting powered - nothing important on that one anyway ;-) Cheers, Jan

Yes, I think the light level is pretty good the way it is. I realize that the surfaces in X-Plane are far less reflective (bumpy) than a real runway, so it will look like the lights are a bit too dim. Turn on the taxi and landing light when you approach a building, and you will see that they are already so bright that they will almost burn everything in their way. It is also a common misconception that landing lights must be super bright so they illuminate at least half the runway.... not so. Cheers, Jan

No problem. I did a very brief search and came upon this post: https://forums.x-plane.org/index.php?/forums/topic/217345-ultra-weather-xp-v26-issues-situation/ ...so it seems that this also affects the Zibo and the "Pocket rocket" and getting fixed by the developer. Cheers, Jan

Hi Mooze, we have had some similiar reports, and users "fixed" it by either running OpenGL (which hints it may be a problem with 11.50 beta) or by uninstalling Ultra Weather XP. If that doesn´t help, please follow this: Cheers, Jan

Hi 3rdwatch, thanks for the feedback - exactly the type of stuff we are looking for! And no worries about the Zibo, it is definitely the airplane we get compared to the most, if not only for the close likeness of the aircraft types modeled. I never installed the Zibo myself...just the same as P3D - I guess my idea of making a simulation experience is not trying to mimic or copy something else - but to fashion it after my experience as an airline pilot flying the aircraft. That does not mean that one can´t learn from other implementations and sometimes it is not necessary to reinvent the wheel . I will look at the buttons and switches you mentioned, sometimes it is as easy as adjusting the length of travel for some manipulators or increasing the "hitbox". Cheers, Jan

Thanks for the kind words! We are really sorry for this inconvenience...but as long as you stay away from manually manipulating any waypoints/fixes with those "forbidden" letters you should be fine for now... You can always "manually" make a company route and drop it into the "coroutes" folder, then load it from the RTE page. Just make a simple text file with an editor of your choice and change the filetype to .fpl. Here is an example routing: EDDF ANEKI Y163 HERBI Y164 OLBEN DIRECT MONIN W112 SOSON EDDH Cheers, Jan

Thank you for the report. The problem is known and fixed for the next patch (soon!). You can read all about it here:

Hello lionell88, the bug is known and will be fixed very soon. You can read about it here: I am not sure which field you are talking about, can you post a screenshot for me? Cheers, Jan

Do me a favour: When running with the latest XPUIPC version, open the Dataref Editor (plugins), search for XPUIPC and manually set the dataref ixeg/733/hardware_overrides to 1. Then try if you can move the thrust levers? Cheers, Jan

I will put it on the list of things to look at - I personally have no idea why it doesn´t work, but Tom may, he is into cockpit building and such... Cheers, Jan

Thanks for that report, SUAS! Ben is continuously working on Gizmo and it certainly is worth exploring the latest betas he posts! Not sure what is going on with your FlyWithLua - I run it on my installation (with the smartWinch script for soaring) and it seems to work flawless...however I don´t use SkyMaxx. Cheers, Jan

We kow that VNAV responese can become wrong. But your post shows me that you do not know how to fly the 737 in other modes. Please follow the tutorials on autopilot and autothrottle use and you will see that is totally wrong. needs some more explanation. Which airport, which approach? Can you provide a screenshot? We would like to see the case where the autopilot in LNAV is not following the magenta line, so we can fix it.

Can´t really say none taken. I fly the plane many hours daily (1.31) and the autopilot behaves completely predictable for me. VNAV is still not working as it should - we never said that it does. I don´t think it has become worse. I am all for freedom of speech, but getting on here and making unsubstantiated claims of "unflyable", "unpredictable", "terrible" etc. is borderline slander. If you can´t get things to work I am sorry for you - we are ready to help you if you provide details of what is going wrong - but if you just feel the need to vent, let of steam and rage, please take it elsewhere. Jan

When using the nosewheel there is an effect that is similar to a "stall" of a wing. The wheel will put out force corresponding to it´s "slippage" - until you pass the critical angle and it starts "gliding". This effect is real - try driving a car on ice or snow and see how gentle movements of the wheel help in keeping in control - once the car starts sliding, it is very hard to get it back under control. The problem in X-Plane is that the force put out by the wheel under a certain "slippage angle" is way too low. So people tend to naturally increase the steering angle to compensate, entering the range of free gliding (stall) where the actual angle becomes irrevalent. Try to use small movements, like jaguado points out. Try to steer smoothly and deliberately and control your speed to be less than 10kts in turns. I will keep pushing Laminar to make this more realistic. Cheers, Jan

This really surprised me - because there was no change to the VNAV calculation at all in 1.3 or 1.31. But hey, if you say so...

Yes, that is unfortunately happening - we will have a fix for this shortly. You can read about how it happened here: Cheers, Jan

I know, otherwise I would not have offered that

If you can post a picture of an in-service Lufthansa 737-300 with the yellow welcome panel on it - I will personally start making that livery for you. Cheers, Jan

I think so - because there is an option to get Navigraph data in the XP1100 format, which forces to have different names for the "same" STAR, if it serves multiple runways (and has a different lateral path for each one). Cheers, Jan