Coop

You would probably need to configure the RealityXP unit to output its information to the HSI datarefs, in the GTN650 settings, try selecting all of the top options and see if it shows then.

Just click on the nosewheel and it should toggle and show back up. Just move the X-Plane cockpit camera outside the window and click on the gear

In the g5.cfg file, located in the BN-2T Islander folder, set the g5_mbbarounit row to 1.

The retail installer is hopefully just a few weeks out.

Hi Antonio, I see you have relatively new graphics drivers, what it working properly before you updated to those? I see something is preventing the synthetic vision from initializing.

There is a "version.txt" file in the SR22 Entegra folder, also when loaded in sim, the side menu on the left edge of the screen will show the version number underneath the "Aircraft" button.

The G5 is being migrated to a RealSimGear product, and hopefully with the v2 update, more developers will come on board. Currently, the available integrations can be found here: https://afmsim.com/g5-archive/

That is the GCU 479 which is in later model Cirrus aircraft with the Perspective+ avionics (G5, G6). We model the G3 series which has the GCU 478 with Perspective avionics. The Home key on the GCU 479 displays the navigation map page, returning to there from any other view you may have previously been in.

No, to my knowledge the only option with the current version would be manually positioning the windows.

You can manually wipe everything Islander related by deleting the TorqueSim BN-2B Islander folder in X-Plane 11/Aircraft/X-Aviation. Rerunning the installer will then make sure everything is completely fresh and no preferences are carried over. What are your carb heat levers set to though? This still sounds like (X-Plane's terrible modeling of) carb icing.

The G1000 popouts in the current M20 don't save position. There are bezeled and bezel-less popups available through the X-Plane command setting system to bind to keyboard or joystick buttons.

Hmm, that is really obscure behavior, especially since nothing changed between 1.2.0 and 1.2.1 with the plugin, I'm guessing something got corrupted in the engine files. We can try deleting these (this will reset the aircraft's physics/mx model entirely) The files to delete are in X-Plane 11/Output/SR22: "TN_Record.txt" and "TN_State.txt"

Hm, they are showing the same size on my end. They are loading the same exact background texture itself. I'm not sure what is going on, but I'm guessing its something with how Windows handles the display coordinates with X-Plane. The interface that X-Plane has gives us essentially no control over the windows to ensure they are properly located, we can only pass the data from the config and hope it is positioned relatively logically.

Thanks, I've logged this with the 3D @Attitude and its being worked on

I went through and sanity checked the code for this, to make sure there isn't anything specifically wrong with mfd_y -> I couldn't find anything there. What I am assuming is the case, everything flips out with window positioning when things are positioned beyond the bounds of the screen space. I don't know your monitor resolution, but I'd recommend and trying a smaller _w and _h for the MFD, to make sure it can be positioned within the bounds of the screen space.

How are you leaning the engine? Is this the SR22 Normally Aspirated or SR22TN?

That is what it shows when there isn't anything being caught on the inspection (nothing under Engine Entries or System Entries).

The engine model is purely X-Plane, so something must be going wrong there. Can you try deleting the Islander "prefs" file located in the Islander folder (X-Plane 11/Aircraft/X-Aviation)

Hi Tom, The engine behaviors were not tweaked in the last update, I'd recommend running engine maintenance through the SR22 Maintenance dialog to see if something there has gone wrong.

Can you send your log.txt?

That sounds like the ELT got triggered. The switch to turn it out is by the circuit breaker panel in the footwell.

Hm, this certainly looks specific to your sim, I'm guessing something else is causing this as we can't replicate this on our end. Can you attach your log.txt?

Can you make sure you are on the latest version of the Entegra's (v1.0.2)

Can you try selecting the two "Connect HSI/CRS" options?