Coop

It shouldn't be, assuming the ignition key is set to both at starting, as well as mixture rich. You can try loading without those hooked up to see if something is causing the issue there.

I'm not seeing anything in the log file, you can try deleting the NA_Record/State files in X-Plane 11/Output/SR22. Additionally, make sure that your throttle is set to idle when you are loading in with the engine set to load on - if it isn't at idle, the instantaneous change can break the engine.

Hi Ernest, Yes, something is coming. It is a total remake of the whole aircraft. More to share on this in the next month or so.

In order to debug what is going on, we will need you to send us a copy of the X-Plane log.txt file. You can find a guide to get this file here: How to find the X-Plane log.txt file?

Hi, Currently 1.2 is shipping with the Islander integrations, the main update has been sent to the store to get sent out to everyone soon.

Turning on the Audio panel, then switching to the GTN should work. The persistent systems should leave the audio panel on on future flights.

Under the menu item for the SR20/22/TN, there will be an option to "Toggle Aircraft Menu" in that menu, you can find the Load Manager tab

The issue lies with AMD's driver exclusively, there is some discussion here on the AMD Vulkan driver's GitHub here: https://github.com/GPUOpen-Drivers/AMDVLK/issues/179

Most likely, with whatever scenery is in that area, it is leading to you running out of VRAM. I would recommend turning down the texture resolution setting.

From the SR22 item in the menu, select the option to show the aircraft menu. Within there, select the Load Manager tab.

Make sure to use the custom Load Manager in the SR22 Menu. If you prefer using the X-Plane load manager, you can turn on "FSE Override" on that page and then use the X-Plane settings.

Hi, This is a X-Plane bug in the carbureted engine model, we've been told that a fix is in the works.

The only option (besides waiting for AMD to fix their drivers) would be to turn off Vulkan.

Most aircraft aren't rendering custom displays, and for those that are, I would assume most are using a Lua interpreter which has a bit different of a pathway for rendering.

Hi Babbo, Yes, this arrises when custom rendering is done in the OpenGL bridge (the only way for addons to draw in X-Plane), and the issue lies squarely in AMD's driver. Sadly there isn't anything we can do except recommend turning off Vulkan.

Thanks for the video, something must be going on behind the scenes somewhere, as we haven't seen that before.

Hi, Did you run the G5 installer after running the Islander installer? I believe what happened was the Islander G5 plugin was overwritten by the manual installer. Try re-running the Islander installer, then loading the aircraft, that should get it back up and working.

Currently the G5 only attaches to the primary GPS source.

Most likely this is a conflict between overrides, and the audio panel is turned off. You can turn on the audio panel using the left-most knob.

I am going to guess you are using the Vulkan renderer with an AMD GPU. This system is very broken in X-Plane due to AMD driver bugs, that have been reported to AMD. Turning off Vulkan is the best method to fix the flickering. If that is not the case, in order to debug what is going on, we will need you to send us a copy of the X-Plane log.txt file. You can find a guide to get this file here: How to find the X-Plane log.txt file?

We do not include the GTN units themselves, purchasing from RXP, as it sounds like you have, is needed. Regarding the config, we have some additional fixes for 1.0.2, but it seems that there are certain bugs on RXP's side that need to be addressed, which we don't have control over.

Can you record a video of what you mean? We aren't interfacing with the RXP avionics directly, so there shouldn't be anything caused by that, unless RXP is breaking the rendering pathway on your computer. For the sake of debugging, I'd also recommend charging the batteries on the Islander through the Islander menu.

Thanks for sharing Nico, we've already got it removed in the (currently still WIP) 1.0.2 update. Deleting the RXP lines is something you can do in the meantime though.

I am showing the Gizmo plugin loading, can you send a screenshot of the plugins dropdown in X-Plane?

Hm, they shouldn't be connected and we haven't heard anything else on this. Do the G5 popups shown anything?