Coop

Hm, it should follow what's on the G5, not the top OBS needle, but it sounds like you are seeing the opposite? Setting the OBS NAV1 gauge is what is driving the response of the AP for you? It could be a bug in the X-Plane AP perhaps, but I haven't seen this myself. Does this also present when tracking a VOR?

It appears this is still being ran from inside the zip folder (Windows can be very finicky with things like this). Try dragging the installer exe to your desktop and running it from there.

Hi Alex, I've PMd you a new version of the plugin to debug this issue.

Can you record a video showing what you are seeing when trying to log in?

Just X-Plane 12

Do you have "start with engines running" selected in X-Plane? That will bypass any persistent bits.

That isn't something currently planned, but something to consider. I believe that config is much more common with the DA40 XLS and prior (non-NG variants).

Right now the G500 doesn't read the approach segment of the flight plan (that support was finally added to the X-Plane SDK recently, and we do plan on adding that) so that is likely where the discrepancy comes from.

Thanks for the report, I've got this bug filed

I think the product you'd be interested in is this combo of the G6 aircraft (discounted for home use, non-BATD/AATD) with the RealSimGear Perspective+ avionics: https://realsimgear.com/products/realsimgear-perspective-software-suite?variant=41433847300182 This requires the RealSimGear Perspective+ stack (GCU479, 2x G1000s, etc.) at minimum in terms of hardware to work.

@MAD0460Was anything happening immediately preceding the crash?

The Intel macs are most susceptible to some performance issues, these products will soon be migrating to the next version of the activation system, which should help mitigate this.

Very soon, should be with v2.1.1

This isn't currently implemented or planned, but I'll log this to be tracked to consider in the future

afm/sr/switches/fuelSelector is a dataref you can set to authoritatively set the fuel selector. -1 = Off (left side) 0 = Left 1 = Right 2 = Off (right side)

We've identified the issue and will be rolling out an update within the next week

This is expected behavior with the round gauge altimeter, it does not contain the same altitude correction logic present in the G1000

Try setting "disable_mtuploader" to 1 in "M:\X-Plane 12\Aircraft\X-Aviation\SR22 Series\TorqueSim SR22\plugins\sr_systems\settings\settings.cfg"

The DA40NG is getting packaged up now and should be releasing very soon

Interesting, it appears this is crashing within X-Plane itself. This isn’t something we’ve seen ourself.

Here, you can attach it to a reply

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?

VPATH is something that RXP/GTN provide, it isn't something we have control of. I'm not totally sure on what you are asking on it, but that would be something to talk to them on. The DFC90/Entegra won't automatically fly the VPATH. X-Plane currently doesn't have any weather radar APIs available, thus isn't a method for drawing that. Rain should depict on the windshield, but X-Plane 12.1 did make some changes to that system that are yet to be integrated. The fleet will be getting 12.1 updates over the coming weeks and months

The v2.x SR20/22 are only compatible with X-Plane 12. The installer will revert to the last compatible version of v1.x of the SR20/22 if the aircraft is being installed into X-Plane 11.

Hi Thomas, RealityXP has their own menu of settings for configuration accessible from the X-Plane menu bar -> plugins -> RealityXP GTN, then for the GTN750 device 1, there should be an option to open the settings dialog. If you send screenshots of those settings, I can see if there is anything apparent with those settings on why the CDI is frozen.