Litjan

Hehe, we are all pilots here! If you can fly the IXEG 737 you are more of a pilot than most real A320 drivers

Let me know how that works out for you!

Hi Dozo, Why don´t you assign the TQ axis to "yaw" instead of "nosewheel tiller"? Cheers, Jan

Hi axmiha, I didn´t spot anything dubious in your Log.txt...but I would still recommend to "remove" your plugins to a safe folder, just for a testing run - both for the weird lighting and also the sound bug. I haven´t heard anything like that sound effect you describe, but to rule out any interference with other plugins it would be interesting to see if these issues persist if you temporarily move them out of your plugins folder? Cheers, Jan

The officially required ones, plus whatever the passengers and crew brings for their reading pleasure... Jan

Hmm, no, this is actually the first time I hear this... normally people with that problem have installed a mod or hack at some time that makes the streetlights more bright or so - often then forgetting they ever did that. So far your case is the first of the lighting level being messed up without the user changing art controls beforehand... Often users are reluctant to post Log.txt files because they suspect that it really is some plugin they have installed but can´t live without, so they don´t want it to be true Jan

And please let us know if that works for you? Cheers, Jan

Hi there, I am fairly certain that you are experiencing a CTD due to one (or more) of your numerous plugins not playing well with the 11.50 beta. Since we see many of these cases, I have prepared a post with some troubleshooting tips, which I link here. I would be very interested in your results... Cheers, Jan

No, I don´t remember. I moved the viewpoint to give you a better view of all necessary instruments "at a glance". The real "default eye position" according to the Boeings manual would be further up and front - so with a normal field of view you could not see much of the engine instruments, let alone the gear and flaps... If it is not too much trouble - just change the value, save the file, then reload your aircraft in the "developer menu". It takes a total of 30 seconds... do this a few times until you are happy and it would be maybe 5 minutes. Jan

Hehe, but he is right - it would probably improve the "Ground handling", too . Cheers, Jan

Hi Rich, we don´t really model anything here - it is simply the X-Plane flight model. That being said, it is correct that in stable, coordinated single engine flight you would normally need both rudder and aileron to counteract the yaw and (since the rudder is not on the centerline of the aircraft but extends above it) roll. The correct technique, however, is to fly with ailerons neutral, so you have full aileron capability in case you need it (crosswinds) and also to avoid the roll spoilers extending (increased drag). If you fly like this, the aircraft will not be in coordinated flight (the nose is not pointing exactly where the airplane is going) and the ball will not be centered. You can alleviate this a bit by "holding the hurt engine up" - this way the plane is still uncoordinated (ball not centered), but the nose will point in the direction of flight...this is what is being taught in twin props, because here the performance in a OEI situation is so much more critical. So in conclusion - push the rudder until the plane stops rolling around the longitudinal axis - then steer the plane´s direction by using the ailerons as you normally would...accepting the ball not being completely centered. Cheers, Jan

Yes, you can revert the default view by changing the viewpoint in planemaker. Or you can set up your own views with either the IXEG view menu or (recommended) the default X-Plane view menu: Move your head and then save the view with CTRL-Numpad. Recall the view with Numpad. Chees, Jan

I agree that the ground handling is not what it should be. It will be improved - when Laminar Research improves ground handling. This is in progress. For now you can follow the advice I gave in the Patch 1.30 video. The new ground handling takes some getting used to - and I would even go as far as saying that some bad habits that crept in with our more foregiving "scripted ground handling" are now showing. Cheers, Jan

We limit the speed that you can dial in on the MCP - like in the real aircraft. The lower speed is dependent on stall speed, which changes with the angle of attack. If a plane is operated in gusty conditions, this angle of attack varies - and so does the maneuvering speed. Your normal Vref will give you 1.3 times the 1g stalling speed. So if you stall at 100kts at 1g (just level flight, no "pulling up") your approach speed will be 130kts. If you fly in gusty conditions, you must add speed on top of this (don´t want to dig this out, but I explained the formula at least 5 times already ;-)), up to 20kts. So in moderate windy and gusty conditions you should fly the approach at Vref+20kts. If your speed is set at that speed, it is unlikely that the minimum speed should shoot that high (and change your selected speed). To go-around: Push the TO/GA buttons (twice for full go-around power). Raise your nose to +15deg pitch and retract your flaps to 15 degrees. Once a safe climb is established, raise the gear. Cheers, Jan

Hello axmiha, we had a few reports of this - and they were all explained by the user running a plugin or script that changed the lighting or colours in X-Plane. If you want to post your Logt.txt I can take a look if there is anything running that could cause this. Cheers, Jan

Thanks a lot - we are putting the finishing touches on 1.32... I will shoot a short promo video with its features in the next few days and then we should have it out to finally squash that N-S-W-E bug... Cheers, Jan

Yeah...this issue has been known since day 1 of version 1.31 and you can read all about it here: Chees, Jan

Hi Rich, thanks for the feedback and the nice words! Cheers, Jan

Hmm - that is odd! Lets see if I can reproduce that and we possibly get some more reports. There has been some work on the internal "timer" function of Gizmo, so this may be related... Thanks for the report! Jan Edit: tried a few times with latest Gizmo Beta (20.06.25.0140 on Windows, 11.50b11) and could not reproduce it. I will certainly keep an ear open for it!

That is already included for next patch! Cheers, Jan

Hi - we were hoping to have Patch 1.32 (with the new beta included) out by now - but it will take a few more days. You can get a newer beta here to carry you over: Cheers, Jan

Hi Ian, I have not seen this type of behaviour - there is a bug with the animation of the FLT ALT window when using the mouse-wheel, but not on the MCP SPD selector. I sometimes have a "reversal" problem, where I drag to the right to increase, then drag back left to decrease a bit - but the value keeps increasing. Annyoing, but most likely an X-Plane bug (we use 100% default X-Plane manipulators). Also make sure you can rule out "command speed limiting" - which interferes with your selection to avoid moving the speed cursor into over- or underspeed situations. Often the minimum speed is limiting and may change due to current angle of attack, flap setting, etc. Cheers, Jan

Hi airfrance... we know. Here is all about it: Patch should be ready in a few days. "Unflyable" is not the correct term - just don´t use manual entry of waypoints starting with N or S or ends with W or E. Sorry for the inconvenience!! Jan

Well, in theory the glideslope transmitter is creating a glideslope that looks like a very wide, flat (3 deg) funnel. It stretches out in all directions, even though the promulgation characteristic is strongest towards the approach side. So it is not impossible to receive the glideslope in any direction of the antenna. The Below Glideslope deviation alert (Mode 5) is armed when a valid signal is received and the radio altitude is less than 1000 feet. The warning should be inhibited if the course selected on the MCP is differing from the IRS heading by more than 90 degrees. Cheers, Jan

Hi, it looks like you have some button or axis assigned to your pitch trim. We are using the default X-Plane trim commands, so you should be able to see/cure this by using the controller setup interface in X-Plane. Another possibility is that you have fly-with-lua or XPUIPC installed and have mapped some function to the "trim nose down" command. PS: (We don´t have MCAS, so thats not it! ) Cheers, Jan