Litjan

Hi Mandretti, judging from your video, everything looks to be set up correctly and I can not understand why the G/S mode is not capturing. It should do so within 0.4 dots deviation. The usual troubleshooting advice would be to (temporarily) remove all add-ons and plugins - or maybe just post a log.txt here first, sometimes we can learn something from it and give you a more precise hint at what could interfere. The biggest red flag is "fly with lua" as that opens up the door to all possible weird scripts that can basically mess with everything. Cheers, Jan

Hi Mandretti, if I had to bet I would place my money on some weird interaction with X-Vision. If this happens again, that would be the first thing I would try to change - remove it temporarily and see if that helps. Good luck and let us know how it goes, Jan

Check that the installer did not put a new folder "fmc_data" into the folder "fmc_data". There should only be two subfolders in that folder, like I wrote above.

Yep, that is the one! You should have two Subfolders in it, navdata and sidstar

Hi Oskar, most of these problems are from not installing the Navigraph database correctly. It is not enough to install them to X-Plane, you need to install them for the IXEG 737 specifically. Cheers, Jan

Yep, that is the part...it is unfortunate and we hope to fix this in the future!

Yes, this is not working yet. You can not change or add any altitude or speed constraints to the waypoints. VNAV is not working correctly for descent yet, as noted here: https://forums.x-pilot.com/forums/topic/8526-things-that-are-not-going-to-be-in-v133/

Glad that is there for you - you can probably improve the experience a bit more by tuning down the "airflow" sound of the airconditioning pack flow. In the real plane this is probably the loudest sound in the cockpit (until you start going pretty fast) - but we provided a slider to tune it down because people complained that it is too loud. I wish I had a slider like that when I flew the real plane .

Like Cameron said - they aren´t working...yet. We had already implemented the interface on the Cabin Attendant interaction panel (that you get when you click on the Cabin Call button), but not gotten around to making the doors actually open and close (except for the cargo doors). Cheers, Jan

Thanks for pointing this out, we will see to fixing it in a future update!

Hi and welcome! Yes, this should be possible. Start in the cockpit, open the door, move the camera view with the regular keys to the position you like, then save that view with CTRL-NumPad key. Let me know if this worked? Cheers, Jan

Hmm, that is weird - there definitely is the sound that you describe, so I wonder why you can not hear it! Make sure that all your sound sliders in the IXEG preference menu (bump mouse left side of screen to show it) are at maximum. Let me know if that helped?

Let me guess, you are running XPUIPC? It is an old addon that is not supported anymore by the developers and does not work with the IXEG. There is one version (not the latest) that does work, though. Cheers, Jan

If using the Warthog (I have the same) just assign the small throttle axis on the right side of it to "reverse thrust". Then after landing simply pull it back to modulate reverse thrust.

The rattling sound you hear is probably the vibrator for the Standby Altimeter. It is a basic instrument that works by measuring air pressure and for increased accuracy (removal of hysteresis error) it has a mechanical vibrator that "taps" it many times per second, just like you would tap an old barometer to read accurate air pressure. We called it the "woodpecker" - you will get used to it ;-) Cheers, Jan

We are currently discussing the details, but I think I can safely say that the IXEG 737 will be made compatible with XP12.

Hi Christopher, thanks for reporting back on this - it might help others with the same problem!

Hi Christopher, yes, FSUIPC seems to be problematic, although most people have problems with the thrust levers not working anymore...lua scripts could be as well, or maybe just some hickup with the preference files... Maybe you can start to slowly bring stuff back and watch for when it stops working. Good luck, Jan

Hmm, can you pinpoint what you have done on your system (installed new stuff, etc.) between when it worked and now? For what its worth, the spoiler and flaps are best operated with "buttons" - because they go into distinct detents or positions and are not designed to be moved "gradually". So assigning buttons to extend or retract them notch for notch works best. Otherwise you will have to carefully juggle the assigned lever to hit the correct detent - which is important, because some logic of the aircraft systems (warnings, autospoiler, etc.) depend on the positions being exact. It *should* work with a lever as well, though. Make sure that you don´t have FSUIPC installed (or only the compatible version, which is not the latest). If all else fails, deleting the contents of your "X-Plane 11/outpu/preferences" folder can help, but note that you will reset all options to default (including joystick profiles etc.) when doing that. Cheers, Jan

Hello Mandretti, the most probably cause is that you passed the "active" waypoint at a distance of more than 2.5 nautical miles. This can happen when you do not fly on LNAV and simply fly past it too far abeam - but it can also happen when the speed of the aircraft is high and the turn angle acute - which makes the FMS calculate an intercept turn that "flies by" the actual waypoint...and sometimes too far. This second behavior is something that we still want to fix, as the real plane does not skip the sequencing when on LNAV (and just misses the point by its own "fault"). To cure this when it happens just click on the next point you want to fly to (this will copy it into the scratchpad) then click on the top left Line Select Key to insert this waypoint, this will effectively tell the FMS to navigate DIRECT TO that waypoint. Cheers, Jan

Hi Patricio, thanks for sharing your solution! As far as I know there are a few different versions of XPUIPC and the IXEG seems to not work (throttles not moving) with the latest one, but it works ok with a version that is a bit earlier...maybe something to try? Cheers, Jan

Bummer. For what it is worth the plan is to migrate the sounds to the FMOD platform as we make it fully compatible with the upcoming XP12 platform...that should change a lot of things sound-related and will be worth trying out then. Sorry I could not help any further, Jan

Hmm, this is really puzzling - we have had some reports about sound problems, but never anything like this where it would just pause and then come back. I really don´t know, either - especially since it was working for you before. Maybe some Windows update? When you fly a real airplane and suddenly your engine quits - my instructor always told me to UNDO the last thing that you did before it happened. The problem is remembering what it was...

Hmm, can you show me a log.txt with all those plugins removed? Just these lines here are a smoking gun, I think... FlyWithLua Info: Start loading script file D:\Steam/steamapps/common/X-Plane 11/Resources/plugins/FlyWithLua/Scripts/B2VolumeControl.lua FlyWithLua Info: Finished loading script file D:\Steam/steamapps/common/X-Plane 11/Resources/plugins/FlyWithLua/Scripts/B2VolumeControl.lua FlyWithLua Info: All script files loaded successfully.

You need to get rid of all of this stuff: Loaded: D:\Steam/steamapps/common/X-Plane 11/Resources/plugins/AutoGate/64/win.xpl (Marginal.AutoGate). AviTab version 0.4.6 Loaded: D:\Steam/steamapps/common/X-Plane 11/Resources/plugins/AviTab/win_x64/AviTab.xpl (org.solhost.folko.avitab). 2022-02-01 19:53:49 BetterPushback[xplane.c:539]: This is BetterPushback-v0.48 libacfutils-0e818a4 Loaded: D:\Steam/steamapps/common/X-Plane 11/Resources/plugins/BetterPushback/64/win.xpl (skiselkov.BetterPushback). Initializing Enhanced Skyscapes 2021.10.29! Loaded: D:\Steam/steamapps/common/X-Plane 11/Resources/plugins/Enhanced Skyscapes/win.xpl (BiologicalNanobot.enhanced_skyscapes). FlyWithLua: Your system path is D:\Steam/steamapps/common/X-Plane 11/ FlyWithLua: System Dir: D:\Steam/steamapps/common/X-Plane 11/ FlyWithLua: Plugin Dir: D:\Steam/steamapps/common/X-Plane 11/Resources/plugins/FlyWithLua FlyWithLua: Plugin Scripts Dir: D:\Steam/steamapps/common/X-Plane 11/Resources/plugins/FlyWithLua/Scripts FlyWithLua: Plugin Internals Dir: D:\Steam/steamapps/common/X-Plane 11/Resources/plugins/FlyWithLua/Internals/ FlyWithLua: Plugin Modules Dir: D:\Steam/steamapps/common/X-Plane 11/Resources/plugins/FlyWithLua/Modules/ FlyWithLua: Plugin Scripts Quarantine Dir: D:\Steam/steamapps/common/X-Plane 11/Resources/plugins/FlyWithLua/Scripts (Quarantine)/ FlyWithLua: Plugin Version: 2.7.31 build Nov 3 2021 14:15:47 Loaded: D:\Steam/steamapps/common/X-Plane 11/Resources/plugins/FlyWithLua/64/win.xpl (CarstenLynker.FlyWithLua.NG). Loaded: D:\Steam/steamapps/common/X-Plane 11/Resources/plugins/SAM/win_x64/SAM.xpl (stairportsceneries.plugin.aos). [0.0000] Terrain radar plugin: version 1.27.0.61cb9ab1.xplm301 [0.0000] Terrain radar plugin: int ver 102700 [0.0000] Terrain radar plugin: plugin directiory is, D:\Steam\steamapps\common\X-Plane 11\Resources\plugins\TerrainRadar\ Loaded: D:\Steam/steamapps/common/X-Plane 11/Resources/plugins/TerrainRadar/64/win.xpl (drgluck.plugins.terrain_radar). Loaded: D:\Steam/steamapps/common/X-Plane 11/Resources/plugins/VolantaPlugin/win_x64/VolantaPlugin.xpl (volanta.plugin). I count 8 plugins, of which quite a few are very invasive and problematic. My money is on fly-with-lua, though.