Coop

X-Plane 11.50b15 broke our 2D rendering pipeline. We have already worked on a fix with LR that has seemed to work in limited testing. Hopefully it should be rolling out early this week.

Can you upload the log.txt file? X-Plane 11.50b15 broke quite a few 2D rendering pipelines and Laminar has a fix coming soon for that, but I want to confirm something else isn't causing this.

If the knobster can trigger commands, then yes, it could be used to be the G5 knob.

Yes, we need to override the avionics switch for proper behavior of a few other aspects of base X-Plane, this has the downside of the GTNs being tied to the main bus instead of avionics. We are looking at potential ways to get around this.

Can you share your log.txt?

I've DMd you the 1.1 beta to try out, that might help with compatibility.

I would recommend trying again by re-running the installer.

The plugin shipped supports back to OS X 10.12 so the second bit mentioned above is not the issue.

Is this file at the location "X-Plane 11/Aircraft/X-Aviation/Cessna 172SP G5/plugins/G5/mac_x64/g5.xpl" It is most likely either that file for some reason is missing or OS X is not loading the plugin, as it is compiled for MacOS 10.15 (though I should have some backwards compatibility to at least 10.14) and you are on 10.13. I am looking into that on my end to see if I need to get a separate build with more backwards compatibility.

From the looks of it, it appears that the X-Plane can't find the G5 plugin at all. Did you copy the installation from your other computer, or did you run the Mac installer?

Can you send the log.txt file after loading the aircraft so we can get a better idea of what is causing this?

The aircraft with a 3D integration are shown on our G5 Wiki here, the B58 is not among supported aircraft. To integrate yourself, we have a guide here, but 3D integration requires access to source objects.

It looks like you have quite a few other plugins installed, my guess is one of them is messing with X-Plane's autopilot details. If you can upload your log.txt file, we can perhaps gain a bit more insight on what is going on.

Yes, the commands are all viewable through the command setting windows for both joystick and keyboard binding. All of our commands start with afm/islander/cmd

Perfect!

The commands/datarefs are still there, no commands were removed from the plugin. We simply switched the in-sim manipulators to use the toggle datarefs to help with usability.

The LR G1000 uses quite a bit of CPU time if you are CPU limited (which it sounds like you might be). With high objects set, X-Plane can really start to struggle. We will have some further tweaks coming, but our plugin uses a very minimal quantity of CPU resources besides the default LR G1000. It could potentially be a VRAM usage issue, we have 2K texture packs available, linked at the bottom of the page here: https://afmsim.com/m20-liveries/

Can you check to see if the brakes have failed in the maintenance manager?

Most people have had quite good results with the experimental flight model, both work well. We are going to be tuning for the experimental flight model soon, but for now you can go with either.

Can you send your log.txt file located in the X-Plane root directory after attempting to load the Islander?

The brake handling is configured through X-Plane itself, we don't have a custom braking logic in place. We do however have a custom chock system with the brakes to simulate the chocks. Perhaps the chocks are engaged?

Hmm, I am not quite sure, what options are checked in RealityXP Settings?

This latest log again does not show Gizmo plugin being installed. X-Plane plugins shouldn't be deleting themselves, so my guess would be some overactive antivirus seeing a false positive.

I do not have access to a source object with GTNs integrated, as such I can't integrate it.

Yes, the HSI is getting a rebuild with the new 3D following Cirrus release, same with annunciations on Nav 2. DME should be functional, same with fuel flow, can you send a screenshot of those not working, along with your log.txt?