Litjan

Yeah, we never got around to changing that - if I recall the internal discussion it wasn´t as easy to change as I thought it would be. I am actually very happy with the windshield wiper sound - look at this video: https://www.youtube.com/watch?v=36DxYzNTFI4 It is a very loud and crude device. Our (well, especially mine) goal is to make the 737 as realistic as possible - including the not so convenient aspects. I was already overruled and we added a volume slider for the aircondition, don´t expect my help to nerf the windshield wiper sound . Cheers, Jan

Correct - on "AUTO" the cabin lighting will go off/dim/bright dependent on flight phase (crude implementation) - but due to an X-Plane bug the light will spill into the cockpit, even though the door is closed. The workaround is to keep the seatbelts set to ON all the time. Cheers, Jan

Or you can just do it like me - copy the new (Navigraph) data not only into the /Custom Data folder, but also into the /Custom Scenery/Global Airports/Earth Nav Data folder - then you will also use the new and updated data for all ILS approaches. Downsides: The LOC may not be exactly on the runway centerlines (on slightly misaligned airports) and you will be prompted to overwrite the data on every X-Plane update... However: The thing that is really interesting about this is that the OP said that he got the frequency for the ILS (109.75) from the X-Plane map, but X-Plane seems to use 109.70. So there are some possible reasons: 1.) A bug in X-Plane, possibly taking the data for the map from another source than the data for the actual indication 2.) A language barrier problem, maybe the OP took the ILS frequency from another (third party) "map", not the one in X-Plane Jan

The frequency that X-Plane uses is 109.70 in X-Plane and that works fine. The frequency MAY be 109.75 in the real world (it is according to my charts) - but X-Plane uses 109.70. If you see 109.75 on the map, file a bug with Laminar Research, because there may be the old "curated nav data" dilemma at work here. X-Plane will NOT use any updated data source like Navigraph or Aerosoft for the ILS approach information. The only way to change those is to file a bug report on the Scenery Gateway site, so Robin Peel can change the data manually. The reason is that they don´t want ILS approaches that don´t line up perfectly (because maybe the airport isn´t in the right spot). Further reading: https://developer.x-plane.com/?article=navdata-in-x-plane-11 Jan

Here is somethting to try: Tune the correct frequency of 109.70 Mhz for the ILS 22 EDDC (IDRW). I don´t think it ever was 109.75... Let me know how that goes!? Cheers, Jan

Thanks for helping out, mfor! We get this a lot - the "disable downwind ILS" option gets new users all the time . Cheers, Jan

It looks like you are right - you can´t see the inboard landing lights when in the cockpit (even with the window open), but if you move to the cabin and then out of the fuselage (there is no camera cage there), you can. This is not really considered a "valid" view, though - there is a distinction in X-Plane between "in cockpit" and "external" views - and some things (like what to display in which scenario) are defined in relation to that. The light-sources is one example, appearantly (even though you can see it´s effect on the ground from the cockpit). Not sure if this is something we can fix, really. Jan

This is not so totally uncommon in the real plane - sometimes the speedbrake still sits "on" the rail after not pushing it forward all the way - not enough to really be obvious, but enough for the warning to trigger. So the first instinct when you get the takeoff config is to slam on the speedbrake lever . Cheers, Jan

Try to fly with the option "show vortices" in the preferences menu turned OFF. This helped some users! Cheers, Jan

Possibly thrust levers not idle at touchdown? Cheers, Jan

Before the end of a week, yes!

No idea what you are doing wrong, except that you are doing something wrong :-) I recommend watching the enclosed tutorial videos and do like I do in them and you will learn how to fly an ILS. Happy landings, Jan

Before the end of a year!

...and if you find out, I would be interested, too. It may have to do with framerate (recording interval) or with the length of the previous flight (amount of storage space for recorded data) - but that is total guesswork on my side. Cheers, Jan

It "could" be done in 2018. And I am hoping it will, but I can´t promise anything. Jan

Hi, I am not going to stick my neck out with any predictions about the remaining FMS work - but it is high on our priority list. The flightmodelchanges in 11.10 are not something you will notice, likely. They don´t take effect yet (since you are not running a re-saved .acf) and the new (re-saved) .acf is adapting to the flightmodel changes, so the plane will fly just like pre-11.10 . Cheers, Jan

2018. I don´t know if you read the previous info, but don´t expect too much from this interim patch. The only thing you will probably notice is added reflections for the cockpit instruments. Beyond that it is some stability fixes to the FMS, but nothing else. Certainly not enough to mash your refresh button constantly . Jan

Well, the "two step" deployment you see is realistic - at the first touch you can see the flight-spoilers deploy (wheel spin-up) and on the second you can see the ground-spoilers deploy as well (they need main gear strut compression to come out). The wheels are not something we mess with - the amount of smoke is done by Laminar Research and beyond our control. Jan

Sorry, I can´t comment on liveries showing Ryanair

I have seen them behave both ways in both versions - never able to nail down why they sometimes pop, sometimes move smoothly. We had to make a custom logic for the spoilers - LR´s default model of autospoilers and roll spoilers simply does not cut it. Therefore we can not use the default flight-control surfaces, which "replay" captures during the normal flight. So we have to "record" the position of the spoilers with our code, and that is not as trivial as it sounds and leads to this quirky behaviour. Jan

Yes, we are running a complex fluid dynamic calculation. We are breaking the coffeeliquid apart into 50 million particles (I know, a gross simplification), all bound by cohesive forces, calculate Braunian molecular motion (depending on the coffee´s temperature), then apply adhesive forces (where the coffee touches the cup). Finally apply (varying with altitude and geographic location) earth gravitational force and aircraft motion´s force, and we get a fairly decent presentation of a moving liquid. This will only cost you 50 to 80% of available framerate, dependent on your computer. We thought about making the effect optional, but we strive for utmost realism, and this one you just can´t go without (even though you may think you can)! Enjoy the coffee! Jan

And a little hint - look at the coffee liquid during turbulence...

Hi Abiofly, thanks for the nice words! Yes, it takes a while for the IRSs to align - thats why we always turn them to NAV pretty much right away after getting into the cockpit. It can take even longer to align them if you park further up north (we dont simulate that). I think the "turnaround" option is still pretty realistic - in real life only maybe 10% of my flights are really cold and dark, usually you either take over from another crew, or you flew the previous sector yourself. We get the request for detachable, fly-out windows quite a bit - and I don´t say never - but completing the FMC is the first priority after this next interim patch. There is an option to display the CDU on an ipad, I think, Tom has that (forgot the name of that application)... Happy landings, Jan

No, if you do that it won´t fly well anymore! Jan

Yes - we have thought of adding a "quick alignment" option...just never got to that. You can pick the "turnaround" or "ready to fly" scenario, the IRSs will be aligned already, Cheers, Jan