Coop

Make sure you have loaded into a livery besides "Default". Most of the other liveries there will support custom tail numbers (except the ones where a tail number is the livery name, as those are designed to match a specific real aircraft)

This isn't something we plan on integrating at this time

The "v" key should also trigger the parking brake to disconnect.

Yes, but a bit complicated. You would need to open the ACF file in Plane Maker, then in Standard -> Landing Gear, uncheck the box for the nose gear that is currently checked next to "Castors", and on that same page, you would need to add nose gear turn degree values, fields highlighted here:

Rudder pedals with X-Plane never give the same level of finesse as the real aircraft which can make it difficult, especially with free castoring. A small bit of toe braking can go a long ways to helping though with taxiing. Some rudder pedals are more sensitive than others, you can experiment with the calibration curve for your hardware in X-Plane settings to see if you can improve the feel for what hardware you are using.

Can you upload your log.txt file? This doesn't look like anything within our control on the aircraft side, but rather something likely with your GPU and X-Plane, but we can take a look.

There is no King Air integration I am aware of for our products at this time. With both products, we include it integrated into the LR C172. There is also integration for both built into the TorqueSim BN-2B/2T Islanders. The MU2 has support for the G500. Also, this freeware B58 states to have integrations for the G5 and G500: https://forums.x-plane.org/index.php?/files/file/73869-beechcraft-baron-58-ultimate-g5-gnsgtn-g500-a-mode/&page=3

The terrain profile was directly tied to the synthetic vision system (and had its own set of issues), and has been disabled. Once XP12.1 with the G1000 improvements comes out, we will reevaluate what features we can add compared to what will then be part of the X1000.

We've figured out the cause of this issue, will be addressed in the next update

From your log, it appears something on your system is blocking X-Plane from loading the SR22's systems plugin. F:\X-Plane 12/Aircraft/X-Aviation/SR22 Series/TorqueSim SR22TN/plugins/sr_systems/win_x64/sr_systems.xpl : Error Code = 5 : Access is denied. This could be one of a variety of things on your system, but most likely this is some sort of an over-active anti-virus software preventing the load flagging a false-positive.

We've got this logged, thanks for the reports

X-Plane still hasn't made available an updated navigation API to expose the approach segment for the default navigators. The approaches will show with the RXP GNSs and GTNs.

Yes, it has been reported to them and a fix is in the works for their next update.

Sometimes we see this on Mac. In the file /Users/olda/Applications/X-Plane 12/Aircraft/X-Aviation/TorqueSim BN-2T Islanders/TorqueSim BN-2T Turbine Islander/plugins/is_systems//settings/settings.cfg, change the line `disable_mtuploader` to a value of 1.

The random failures that would affect the custom systems would not connect over to the retail SR. XP failures that trigger environmental issues (eg. failing an ILS, etc.) or default aerodynamic subsystems (eg. aileron hard-over) would still work.

It is in the works, but as stated before, it is a lower priority than some of our existing products.

Ha! Well that doesn't seem right. I'll get that looked at.

Yes, those are labeled correctly. For the image of the windshield push button, which aircraft is that? On our SR22 G1000, you can see here that it actually is a push-button.

That is the recirculation button for airflow. To enable that, the fan setting must be at max, temperature must be full-cool, and air conditioning must be on.

Thanks for this, I'll get it logged to be looked into.

Low frame rates without mtuploader can lead to flashing. In this case, as it sounds like your system doesn't handle mt_uploader (which we are still working on a fix for on Mac), you would need to change X-Plane settings to increase frame rate, which should reduce flashing.

Thanks for the log. I think your guess there is likely the culprit, something isn't happy with that high of CPU use, and the XP12 Lua subsystem isn't handling it as gracefully as XP11 did.

The previous beta is no longer active. I haven't seen this issue with Gizmo myself before, if you can send your log.txt we can take a look at it.

The FSE Override is only meant to be used in cases where you can't use the custom Load Manager (such as using FS Economy where it sets the payload). Some features are not available when in that mode. Regarding 1. We have our own O2 and TKS system that is active whether in FSE Override or not. We don't use the default system for that, thus the sliders on the default W/B screen mean nothing. Regarding 2. X-Plane handles those units there, we don't. Regarding 3. Again, that would be an X-Plane issue where it isn't saving the weights stored there. Why they work on the default SR22, I'm not sure, but again, FSE Override is not intended to be fully featured, as we have heaps of custom systems that are best interfaced through the custom load manager.

Windshield defrost is on the ECS panel (right of the MFD). The top button is defrost, and set the fan to full.