The community converter is the way of cooperation that allows several users not to repeat the same work over and over again, discuss all issues related to this model and create working conversion files more effectively.
Note 1: Please don't use irrelevant, mismatched parameter names from the SimVim database list to convert the data for which you have not found appropriate SimVim parameters, use the SimVim configurator layout maps or ask us to add the absent parameter to SimVim database. The conversion file (in the table above) can also be edited by other people who have access to the "community conversion tool". Discuss any questions related to this aircraft's conversion file in this thread to collaborate with other editors and avoid misunderstandings.
Remember, you don't need to "convert" every input parameter for your plane even if you see that it has its "custom" dataref/command for this parameter (switch, button, LED).
Especially for most of standard X-Plane functions that always are used (and can not be avoided to be used) by any plane developer, such as autopilot, all radio, navigation and many other functions.
If you have assigned the function for some hardware switch, but you don't see that the same switch on your virtual panel doesn't flip, it doesn't mean that the system in X-Plane is not affected. It can work as needed and you just have no "visual" representation on the screen (that you don't need when you have a "real" MCP/panel..).
In most cases it is just animation of the on-screen switch for which the developer included additional commands/datarefs.
Of course it's bad when the plane developer script checks the custom dataref value for the virtual switch in every X-Plane frame, in this case, when you use standard commands for a switch that should work, but the standard dataref always resets to the position of the virtual switch value. It is bad programming practice that takes much processing time (especially for hundreds of datarefs and don't let using standard commands).
In SimVim every used dataref is changed once - only when an action was actuated, and doesn't checked in every frame.
The SimVim plugin program is in "idle" state 90% of the time and takes zero (0) of all X-Plane program cycle.
The same goes for SimVimPanel program.