Coop

Yes, if you are in calm winds, these airspeed values should be close to each other.

I don't have any idea on what is going on there. The installer should just be placing the files, we aren't doing anything to lock folders or anything that I know of.

To get the auto-advancing of waypoints, there is a checkbox "Auto adjust CDI to GPS DTK" that needs to be selected. It is shown in this image: (from https://afmsim.com/g5-integration-guide/)

Did you run the manual G5 installer in addition to the initial main installer from X-Aviation? The C172 G5 should come downloaded ready to go, running the manual installer on top of that could overwrite the installation. If that's not the case, I notice you are running an AMD RX480 with Vulkan enabled. The AMD drivers for Windows are very buggy with X-Plane in Vulkan mode which could be causing the G5s to not show.

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?

If you select the real weather option, it will use the current weather conditions. Besides that, I believe the only other option is manually specifying the temperature.

Regarding the sound, give this a try: With the oil temperature, we will be taking a look to modernize the flight model to XP11.50 with the coming update. Not sure what is going on with OAT. I haven't seen that as an issue before, are you set to using custom weather, and manually set the temperature?

I've never seen that crash before. Nothing specific is being output to the log file, so I don't quite know what is causing it. Did you bind the Pocket Rocket custom commands to the Honeycomb, or are they all using the default commands?

Hi Mark, Are you using any scripts or something that could be trying to set the altimeter setting? Based on that, it sounds like something is overriding the stby baro setting.

Gizmo isn't used on Linux. If you can send your Log.txt file, that should help narrow down what is being failed to load.

This is an obscure one, the most likely is if you have some sort of physical hardware installed that is turning off the underlying G1000. We also need the log.txt file to be able to debug anything, as well as screenshots of what is going on.

Autopilot integration is not currently in the G5. We have worked on getting it integrated and it will ship in 1.3.0

The G5 has its own altimeter setting reading off of the X-Plane Standby Setting. The G1000 and G5 are not cross linked and changing the altimeter setting on both would be required.

The G5 for the M20 has a patch file to download with specific instructions, please see instructions and download link here, in the aircraft able at the bottom of the page: https://afmsim.com/g5/

Something seems to be toggling one of the Entegra and/or autopilot popout commands before the aircraft is fully loaded and causing the crash.

Hi Mike, Yeah, we figured out what was going on in certain cases, fixed and will be coming with the next update, 1.0.3

Feel free to send us an email- sales@lecomp.net to discuss options

In the top bar of X-Plane, there is a option titled "Cirrus SR22" (or SR20/SR22TN, depending on which aircraft you have loaded). Under there you will find the option. You can also open it by hovering your mouse on the left edge of the X-Plane window and a red tab should appear, clicking on it will then have an "Aircraft" button.

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.