Coop

Thanks for reporting back. We are looking into it, hopefully we will be able to generate a 1.0.2b with some other changes. I'll PM you when we have something to test. Compiled on Ubuntu 18.04 LTS

Slightly different generations, as our SR22s are all based off the G3. The SR22TN uses the IO-550 with the Tornado alley turbo-normalization kit. The SR22T uses the TSIO-550. We have done the SR22TN

The radio and transponder is just using the default X-Plane datarefs for control (as part of the X1000), xPilot should be reading these already, but if they aren't there isn't much we can do about that. Regarding maintenance, we do have a full inspection system. In the SR22 menu, under Maintenance, you can performance the necessary scheduled and as-needed inspections. Output logs are saved to X-Plane 11/Output/SR22. These files will also popup in-sim starting with the next update (as is currently integrated in the Entegra variants).

We've got it fixed in 1.0.2 which should be releasing later this week.

Try checking your junk folder to make sure it didn't get lost. The email would have been sent on March 26.

Hi Mike, that is not currently adjustable, as it is getting the data from X-Plane. We will consider adding that down the road.

Ok, glad to hear the engine stays running now when starting with that selected. Regarding starting the engine, you need to be very precise with the starting technique. Make sure you boost for ~2 seconds. Do not boost for more than 3 seconds, as that can lead to flooding the engine. When you crank the throttle, make sure that it is at 1/4" open, based on the in-sim model. This typically translates to a smaller amount on most other throttles, I am not sure with the Honeycomb. If it isn't cranking over, widening and closing the throttle is a good step to take until it cranks, it can take a few (or many) seconds to turn over sometimes.

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.