Litjan

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

Oh, only about 5000 times... Yep, I will definitely try to reproduce that weight bug - very likely it is one variable that is not reset... thanks for the report! Cheers, Jan

Yeah, I see the throttle going up and down with your hardware throttle...could be due to the way we overwrite that value, not sure. Nils implemented that 10 years ago ;-) I think it is only like 2 percent - that will not amount to a whole lot of thrust. And if you don´t want that - don´t play with your throttles! ;-) With your 1200fpm rate of descent the plane was still decelerating very slowly - as I would expect it. Nice landing! :-) I see the weight problem! Is that happening for you only on "second" flights? Or also when you initially set up your first flight? I just tried on my end (first flight) and it worked as expected, but if you say it happens on subsequent flights I will do one and check... If all else fails, reboot gizmo before doing your return flight (little arrow on right-hand pop-out menu). Cheers, Jan

Hello Krzysztof, yes, the problem is known and Tom and I are working very hard to fix it. It is described in detail here (the 4th point). We hope to have the next patch ready in a week, approximately... Best regard, Jan

Hello luis, go check if it is possibly caused by the first point mentioned here? Best regards, Jan

Thanks for the report, Ian - I will see if I can reproduce this! Cheers, Jan

Hi Krzystof, no, I didn´t catch the addition to your post... You run a lot of plugins - many of those are known to cause conflicts or affect the inner workings of X-Plane. I am sure it is one of them affecting your APU. To find out which one, follow this (point number 4) Cheers, Jan

Hi Ian, your first issue sounds very much like a pound/kgs conversion problem. Make sure you have set the preferences up correctly for your preferred units and enter those correctly, too. I haven´t observed any problems with the fuel weight getting calculated correctly, but you never know...maybe you can snap a screenshot when it happens? The speed not bleeding at 1000fpm is not what I observe - you need about 1200 for idle at 210kts (minimum drag) or about 1500 at 250kts. Make sure that you have no other plugins interfering. 31% N1 is normal for "flight idle", we overrule the hardware throttle position when at idle to at least have the engines maintain that (while in the air). When using the weather radar with ANY third-party weather addon all bets are off. Nothing was changed with regard to its operation since 1.2. I have observed the glideslope warning, too. I think in the real aircraft this would maybe not pose a problem because the signal is weak on the other side of the antenna, I am not sure. I could not glean any information on this mode beyond that it will sound if you are "below the glideslope" (varying frequency and loudness). There is no logic to check flap setting, rate of climb or anything else to suppress those for climbouts.That being said, I am only aware of one airport in Europe (LFML) that requires the DME off of an ILS for a SID - there used to be a departure out of Orly like 20 years ago...and then there are the Brits, of course . We will use the new setting in planemaker that was enabled with 11.50beta11 that always "forces" experimental flight model on. I also like it. Cheers, Jan

We have some reports of sounds not playing nice with WMR headsets... also running any other addons that create sounds (like ambient wind, birds chirping, etc.) may possibly interfere with our own sounds. Cheers, Jan

Hmm, thats a new one... can you post a Log.txt file so we can see your hardware capabilities and other plugins which may interfere with the sound system? Is there internal engine sound? Are the engines running? Do you have your volume up? Can you hear other sounds (APU, airconditioning packs, electrical hydraulic pumps)? Cheers, Jan

I will see what is going with that and report back! Gracie, Jan

Hi Torbinator, make sure that you don´t mistake the noise of the running air-conditioning pack for wind noise. I have changed the default settings for the "turnaround" state so that one pack runs (to keep the passengers comfortable). To test, simply turn off the pack before going to the outside view. Cheers, Jan

When you set up your VR configuration in X-Plane there is an option to show the green "manipulators" - not quite sure what the option is exactly called, but you will find it. It is in the same menu where you choose between "realistic" and "ergonomic" yoke and also enable/disable the VR-mouse pointer. Let me know how it works out for you! Cheers, Jan

I just tested the mouse in VR and for me it works flawlessly on the overhead panel (and everywhere else). Here is something to keep in mind: Our manipulator clickspots move with the switch. So in case of a "click to toggle" switch like the yaw damper, the clickspot will move away from your mousepointer once you click the switch! You can see that the little "hand" turns into an "arrow" at that time. You will then have to move your mouse again until it touches the switch (and turns into a little hand) again to toggle the switch a second time. Cheers, Jan

We are working on the fix!

Thanks for the feedback, guys. I don´t know about the sounds - I would think that it is some sort of resource problem - first thing I hear about it and don´t experience it on my computer. But then again I usually set the flight up in 2D and only then switch to VR, maybe that has something to do with it. I will try. The manipulators in the VR cockpit are tuned for operation with a VR controller, I have to try with the virtual mouse. But the yaw damper switch is a simple "click to toggle", so I can´t see why that wouldn´t work. I will report back! Cheers, Jan

Hi Krzystof, are you running the beta version of Gizmo? It improves "smoothnes" of the simulation a lot. You can also get that latest beta in the post I mention below. If you are already running that, I would still need you to follow this: so we can rule out any conflict with another plugin. Cheers, Jan

...and in addition to that: I have "relaxed" the requirements of the speedbrake to be "fully down" to not trigger the takeoff configuration warning horn. It used to be at 0 (and not a single bit more), so a sloppy lever or mouse-move may have put it at 0.00000001 - and triggered the warning. Cheers, Jan

I have two buttons on my joystick assigned to "speedbrake down a notch" and "speedbrake up a notch" (or whatever those are exactly called) and it works nicely. Maybe try that? Cheers, Jan

Hi Benweston, I checked the SID. The reason for this is that our FMS assumes that you will accelerate to 250kts fairly quick. That is the reason for the BYPASS of waypoint D161D - the radius would be too large for it to make the turn without overshooting the calculated intercept point for the leg to the north... I think the real FMS may do a bit better in this case (you can see how the route draws good before you ACTIVATE the route)...but this is a tough SID to fly for our FMS and therefore was not handled perfectly. You did the right thing in flying it manually/HDG SEL, though. There are a few SIDs in real life that I always flew like that (DEGES2S in LSZH or SPI7C in EBBR) because it is more efficient. Others (DET2G in EGLL) must be flown in HDG SEL because the FMS would bust the first turn going too wide... So the pilot always has to monitor the performance of the automation, you won´t get away with a "but the FMS flew it that way! It is not my fault!" Cheers, Jan

No idea - I don´t have the Better Pushback plugin, I don´t think we did anything to the green planning lines and this seems to be not a widespread problem (at least its the first complaint I heard about BP and the IXEG 737). Maybe you can find more help at the BP support forum? Good luck, Jan

No worries at all - the button is pretty inconspicuous (on top of the EFB) - and I made Tom make one (before the tab was always on) - because I thought it looked odd to enter a "cold and dark" cockpit and the laptop is running. Background story here is that we have EFB´s in our real aircraft, too - of course. Procedure is to shut down the EFB when you shut down and leave the aircraft, but some people simply forget (he who is without sin may throw the first stone!) and when the battery goes dead, so does the display of the EFB (even though the tablet itself is still running in its docking station). So sometime during the night the tablet will reach low power and go to sleep mode. But for some odd reason it will not wake up from it again, UNLESS you take it out of the docking station, flip it open, and hold down the power button for a few seconds. The problem is - we are not allowed to do that - it´s considered a maintenance task. So basically if you are on an outside station in the morning with no company maintenance available, you would have to contract a certified engineer, fill out a bunch of paperwork, do a million phonecalls (incur a few hundred Euros of cost) and delay the flight for a minimum of one hour. Or break the rule, take the laptop out, start it up and be done with it. Which I would never do, of course. Hence my obsession with the power button Cheers, Jan

Me neither! As I always say - Checklists are for the bad pilots - the good ones never forget anyway... Cheers, Jan