Coop

The AFM switches are on custom commands, these can be found through the X-Plane command browser for Keyboard and Joystick commands. All afm commands will be prefaced with "afm"

The M20 Ovation III and Acclaim are not compatible with 11.50 yet, we are waiting on a fix for the synthetic vision system to allow Vulcan compatibility. (It can load just fine in OpenGL mode) @jcallum The log attached has a crash induced by xPilot, not the M20 Collection.

Regarding range keys being reversed. We use the default X-Plane commands which RXP overrides when installed. We don't command the RXP GNSs directly. The HSI will be fixed in the next update.

We are adding the ability to enter the aircraft menu to the Top X-Plane menu bar as well, to help reduce any confusion

Are you using the Backcountry panel mod? The black panel with that is quite a bit darker than default.

We have quite a few optimizations of the interior mesh coming with the next update that should hopefully fix a lot of the performance issues. Yes, a glass-reflection-disable setting will be added to the menu with the next update.

Woah, apparently so. Did you click and keep dragging or what happened to cause that? Good idea on adding the current weights, etc.

Those issues all sound like the Gizmo plugin is not running. If you can attach your "log.txt" file, located in the X-Plane 11 directory, after loading the plane, we will have a better idea on what is going on.

Something appears off with that click spot, we are looking into it.

We will be integrating our G5 and SR22 system for display configuration through the next update.

We have a tester that runs it with a networked setup. There will be a few steps to get it all working, but it should work, as long as your primary machine is the one which display's the aircraft panels and all hardware runs through that same machine. If all the other machines are purely for external visuals, it should work.

Hi! Regarding the interior brightness, I would recommend checking your monitor's gamma setting, our graphics are tuned on calibrated monitors, appearances can be different on different monitors. You can also try turning on the cabin light, which should brighten stuff up a bit as well. Regarding SVS, I have forwarded this on to the SVS developer, not quite sure what is going on there, something seems up with the mesh parsing possibly. Regarding tail wheel handling. We are constrained by LR on the ground handling characteristics. There isn't an X-Plane setting to put the plane in an easy mode. Keeping the engine in Beta and being on top of the toe brakes is the most important thing for handling - the plane is a beast! We also include the retract tricycle variant for this reason, which has much easier ground handling.

Can you provide your log.txt file with all plugins enabled?

Hm, gotcha. I will mess around and try to replicate the issue, that is an odd one.

Love it! Thanks for sharing

Looking at the picture attached, the altitude is armed to -600 ft, so that could cause issues (assuming you aren't flying below sea level). Odd about it continuously climbing, perhaps your CG could be out of limits and you are running out of trim authority?

Glad it is working now

We are waiting for the Vulcan compatible version to implement librain

Ah, that one isn't tied into the persistence system, I will log that.

The cockpit lights require HDR to be enabled (Graphic settings on High), if not then the only lights X-Plane will render are the "lit" textures as they won't render dynamic lights. Both of these are being adjusted for the next update, so it should get a bit brighter both with and without HDR.

When it is ready

We will see what we can do. The non-preselect mode is because the "Arm" button needs to be manually selected, where the KAP-140 with altitude preselect will always arm the AP.

Starter Isolation switch is necessary to be on, it is a physical disconnect for the starters' power.

I did some testing to see if I could replicate. It seems that X-Plane decides to enter some sort of a semi-pitch change mode when those buttons are hit, but without adjusting the autopilot status datarefs (so we have no way to know!) I will gather some more data and file a bug with LR on this.

Regarding frame rate, all of the G5 drawing is done on a separate thread, then the pixels are copied over during the gauge drawing callback. The library we use for drawing has an update in testing that would allow for asynchronous uploading of these textures to the GPU which should help a bunch with performance, idealy reducing the G5 to near zero for non-thread-limited CPUs. Regarding the dimming function, that is currently not implemented, but it is a highly requested feature so we have it on the list!