Litjan

Hi! In one of the updates the displays were a bit "cleaned up" - the effect that you show on your pictures was kinda cool, but really a bit too intrusive. A real display is rarely that dirty, and if it is the pilots will wipe it clean pretty quick, because...we need to see stuff on those ;-) Here is what it looks like on my end right now:

And once you turn up the rendering settings high enough to get HDR you can use the cockpit flood light (dim or bright) if things are still too dark. In addition you can use the map lights (over the pilots head) to spotlight certain areas of the cockpit (they swivel) - and if that is not enough illumination you can grab the flashlight (mounted to the side of the pilots) with the mouse and this will illumnate a small area around the mouse cursor to help you see stuff better. The real 737 has a light built into the control stand of the thrust levers that backlights the trim unit indicators, so they are a bit easier to see than the one´s in our plane. Thanks, Jan

Hmm, that is too bad - but of course, there is still the option to remove your other plugins to test if they interfere. Cheers, Jan

hmm - any Gizmo error can have unpredictable results on all systems. So as soon as you have a Gizmo error, consider the flight flawed! If you do, please post those with a screenshot and the log.txt in the relevant forum so we can see what the problem is. There should be no Gizmo errors on your flight at all - note that you can not change any altitude or speed restrictions in the FMS (yet).

No, the real aircraft is pretty reliable when capturing the ILS - but then again you are the first one to report problems with this in 7 years of selling this aircraft and thousands of users flying ILS approaches with it. So this makes me believe that you are doing something unique - not wrong, but different from everyone else that makes you have these problems. It must be something weird that is confusing the capture logic - you could try to "reboot gizmo" before trying a new approach, this should clear out any data variables that the AP logic might have engaged from previous flights.

Yes, I can imagine that maybe some values for deflections get confused when resetting the aircraft in that way and create a brief "captured" logic but then deflect out of bounds... so that the autopilot rejects following them from now on. So it is especially important to NOT set the APP mode until the reception of the ILS is steady after unpausing.

Wow, thanks for doing this detective work! I will try to verify your findings and see what is going on with that. Cheers, Jan

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