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/
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.
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?
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.
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?
I have not seen an XSaitekPanels configuration created for it yet, but there are commands and datarefs available for every switch so it should be possible to create a configuration, assuming that it can be user-configured.
The Gizmo plugin does not appear to be loaded/installed. This plugin is installed inside the global plugin directory and cannot be remove as it is what activates the aircraft.
OAT indicator is the gauge attached to the windshield behind the magnetic compass.
The cabin heat is shared with the pilots, there is no separate control for them.
Yes, that would be magneto 1 on the right engine if you are starting the right engine. I will check the rest of our documentation to see if we have a typo.
Most likely the engines got flooded with too much fuel, make sure to have the fuel pump be turned on only right before starting each engine side to prevent flooding.
The G5 integration requires having a license to the AFM G5 Instruments. You can purchase a license from X-Aviation here: https://www.x-aviation.com/catalog/product_info.php/afm-instruments-p-163
I'm not sure how the HC Alpha triggers commands, but I can confirm that those commands are functional on the plugin side (just loaded up and tested by binding to keyboard).
afm/islander/cmd/switches/gpu_Off turns off the switch
afm/islander/cmd/switches/gpu_On turns on the switch
afm/islander/cmd/switches/gpu_Toggle will toggle the switch.
The only thing I am seeing in the log file is potentially the in-sim ATC causing the CTD, I am not seeing anything to signify the PR is crashing. If you can provide more log.txt files from when this happens perhaps we can get a chance to see what is going a bit more clearly.
We don't have an installer for previous versions.
That sounds most likely to be a missing Microsoft Visual C++ Redistributable. You can follow the guide here to get that installed: https://torquesim.atlassian.net/servicedesk/customer/portal/1/topic/81283878-8875-4bdf-90fa-f832f9b98002/article/128188431