mfor

Edit: Misread what you were saying. From the video it seems like the dataref might not be updated every frame (since then you should be able to move it about 35 (or 25/2) degres per second. In that case try Ben's dataref to see if that is faster. If not what you can do is use some sort of local desired value which you can modify quickly, i.e. don't read the set heading (only at program start or when idle) and just do the calculation on a locally stored value that you then write to the dataref.

Hmm it's fairly fast for me, do you really need sub-millisecond responses for heading data? Or do you mean on your hardware side? If so it might be possible to create a plugin that exposes a custom command and handles the dataref reads/writes.

Test an aircraft that came with x-plane itself (e.g the 737-800) - do you have the ILS problem there as well? No (ILS works in x-plane aircraft) => Problem with your IXEG installation, try reinstalling it and discuss things here. Yes (problem with the x-plane aircraft as well) => Problem with your x-plane installation, try repairing/reinstalling it and contact LR http://www.x-plane.com/support/

Not sure if this does what you want, but you can set MCP heading (and altitude) by simply writing the values into sim/cockpit/autopilot/heading_mag sim/cockpit/autopilot/altitude

Interesting, I presume this is because x-plane ignores the ILS data and only the ILS data, so you'd get DME and other stuff from the updated source and LOC/GS from the file mentioned in the blog post ($X-Plane/Custom Scenery/Global Airports/Earth nav data/eartch_nav.dat) It appears you can edit it fairly easily though, e.g. EDDC appeared 6 times: 4 51.14605278 013.78412222 703 11050 18 40.830 IDRE EDDC ED 04 ILS-cat-II 4 51.12263333 013.75188333 755 10975 18 220.806 IDRW EDDC ED 22 ILS-cat-I 6 51.12746111 013.75621667 755 11050 10 300040.830 IDRE EDDC ED 04 GS 6 51.14081111 013.77459444 703 10975 10 300220.806 IDRW EDDC ED 22 GS 8 51.11698611 013.74552222 755 0 0 40.830 IDRE EDDC ED 04 MM 8 51.14976111 013.79049444 755 0 0 220.806 IDRW EDDC ED 22 MM Changing the values for GS and ILS-cat-I to 10975 from 10970 causes x-plane to use 109.75: Not sure if that has any unwanted side effect though.

The DME is showing in the video, so it only seems to affect the ILS. Again I'd suggest you try a default LR aircraft to see if this is general problem or just with the ixeg 737, check the log and try a repair/reinstall. Also, do you have any other plugins installed? Maybe try disabling them to see if they are messing with the ILS reception. With more people experiencing it, this could be a bug with the 737 of course, but this should narrow it down, so Morten, Litjan & Co know it's a problem on their end.

I think the approach in CYQB does not have DME. Things I would try now: set up a headwind and see if it is working now try a different plane to see if it's a ixeg737 only problem. If it still isn't working and you've double checked x-plane's failure settings, I'd start considering a botched (nav data) install. Are you using custom nav data? Maybe there's a clue in the .log file. Otherwise try repairing the installation. If the problem persists with the default planes as well, you should check with Laminar Research and maybe file a bug report.

There are no ILS needles in the EADI showing, meaning that you don't receive the ILS signal. Since you seem to have tuned the radio correctly, I assume that the signal is not being sent (unless you have some sort of X-plane failure activated). This happens if you activate the "disable downwind ILSes" option in the map and are trying to lock onto the ILS of a downwind runway, as is the case in your picture. So open the map (m) and see if that option is checked. If it is, un-checking should provide you with an ILS signal. Edit: It should look like this: Note the magenta needles on the EADI and the F/O's VOR/ILS display.

You'll hear the configuration warning when you advance the throttle and parking brake is set flaps not set properly trim outside of takeoff range speed brake not fully retracted If you run into this problem after a previous flight then most likely the trim has been moved out of the proper range during approach/landing. Other people had problems with an axis assigned to the speed brake, which caused it not to be fully retracted.

Worked fine for me just now (KSFO 28R, navigraph data) - what airport/ILS did you have problems with? Can you reproduce it? Screen shots? The general procedure is to catch the VOR first and then intercept the glide slope from below, so you don't miss it.

Try switching off the draw wingtip vortices option - I think other people have reported that option to cause flickering. Edit: See

Well i guess you could save them yourself but since the flight model is not updated to match the new ground effect calculations the behavior will be wrong/weird.

Well you can look up real flights using flightaware & co: http://flightaware.com/live/flight/EZY8247/history/20170925/1255Z/EGKK/ELLX/tracklog (that's EGKK to EGLX which is not that far away) That said, 370 is much more realistic although I think that's for a light 737 (for me the FMC usually recommends around 350 for optimal crz altitude)- 130 would be for a really short hop.

You can tweak the water's appearance via the water/fft_amp1-4 and water/fft_scale1-4 datarefs: If you want a great all around experience you will have to dynamically change those values according to your AGL using a plugin/lua script.

Just like you can have modified scenery you can also install custom Nav data to match the current airways and fixes (see for example https://www.navigraph.com/) If you didn't install a package like that you're running stock nav data. Looking at the pictures the altitudes definitely look weird: descending mid route and then climbing again. Not sure what would cause this. Does this happen every time you enter that route or only after a previous flight? Which SID and STAR did you choose? Can't seem to reproduce it on my system, but I do have custom nav data installed.

Entering the origin airport will indeed reset the route as you've discovered. The "UNABLE CRZ ALTITUDE" happens for me when for some reason the FMC thinks the aircraft won't make it to that altitude on that route for some reason. The route may be too short (doesn't seem to be the case here) or there are some weird altitude restrictions or problems in the nav data. So you if you encounter this again check the legs page for altitude entries and change them if needed. Also, sometimes the FMC's altitude calculations can just glitch-out. In any case it would help if you could state the exact route you entered (and custom nav data if any), so the devs can look at it. Distance increasing is often a case of a missed waypoint. The FMC then wants you to go back and fly over it before continuing. Entering a new next waypoint will fix that.

Still weird that it shows no (or too low) frequency but correct AC voltage, if it is off shouldn't both be zero?

1) Put them on the same FMC (sub) page or do you mean always and automatically? Don't think that's possible. Edit: Or are you talking about the EHSI displays? In that case see 2) 2) Turn the F/Os ehsi selector to map. You can make both EHSI display the same information though, by setting the EFI selector on the overhead panel to "both on 1" or "both on 2"

Well I suppose as soon as the main gear has touched down you need to center the rudder quickly anyway.

I'm setting it to 0.154 for the armed position in my little plugin and automatic deployment works just fine. If there's a better way to do it I'm sure one of the devs will chime in.

"ixeg/733/hydraulics/speedbrake_act" works for me.

Make sure no other plugins are interfering - for example there was (is?) an issue with terra haze messing up the lighting. For the engine gauges you can select the "steam gauge" option in the preferences, which replaces the digital engine instrument with classic needle based ones that are much easier to interpret with a quick glance. And the fuel gauges are hard to read IRL as well from what I've read. Having said that here's a screen shot of how it looks on my system for reference:

Well there's a Flight Operations sub forum.... .... and we've been moved there

Better Pushback works fine with IXEG here. I think there's a thread about xEnviro and CTDs. Might be a good idea to test without any (active) plugin and see if your installation is stable then.