Note: this configuration step should be used only if you have a custom aircraft for which some parameters are not working with default SimVim assignments.
Generally, your cockpit controls will work with the configuration you created as-is, for all default X-Plane aircrafts, most freeware planes, and for the custom aircrafts already included in SimVimCockpit database by default. If some of the input controls assigned in the configurator do not work in your aircraft model (or work incorrectly) with the parameters you assigned to them, it can be because:
The "Input Test and Conversion" tool allows you to test any of your assigned inputs interactively, and if some of them needs custom re-assignment, to convert them and test instantly.
If the ID/Name has not appeared in the text field, that means either you haven't connected the input correctly (check your wiring)
or you haven't assigned this switch/encoder yet in the configurator.
If your virtual plane reacts correctly to this input you can go to step #2 again and activate and test the next input function.
! Before conversion you need to prepare the list of custom commands and datarefs needed for your cockpit that are provided by your plane model developer.
The set of options that will appear in the data conversion window depends on the input type the plugin reads from the configuration. The way how the particular parameter should be reassigned depends on custom commands or datarefs available specifically for this parameter in your plane model. Below you can see 2 or 3 options you can choose for any input control.
For one momentary button you can assign either one custom command or custom dataref value, depending on what option is provided by your custom plane developer. Of course, using the command is preferred.
To convert a custom parameter assigned for encoder control you have only two options - your custom aircraft model is provided either with two commands (usually and preferred) for this function, or one custom writable dataref:
A parameter assigned for toggle switch (On/Off) can be converted in 3 ways - your custom aircraft model may have two commands (preferable), or you can use custom writable dataref with two On/Off values. The third option, which is often the only one available in some custom planes, is just one toggle command that is OK for a virtual on-screen panel, but for real switch you need to synchronize the switch position by reading the related dataref:
3-position toggle switch (Up/Off/Dn ) parameter can be converted in 3 ways - aircraft model may have 3 commands, a custom writable dataref with 3 values, or it can often be just two "switch Up" and "switch Dn" step commands. For the last option you need to know what dataref is used to store the switch position, and the value related to the switch central position (which can be -1,0,1 or 0,1,2, etc.)
N-position Rotary switch parameter may also have one of the 3 options to be configured - aircraft model may have N commands, a custom writable dataref with N values, or two "switch Up" and "switch Dn" step commands. For the last option you need to know what dataref is used to store the switch position:
To make entering custom commands easier, you can create a simple text file in your custom plane folder, name it "refs.txt" and add a list of 10-30 commands or datarefs to it.
This list cannot have more than 50 lines and must include only command or dataref string in one line, no other signs ( " , = , ) , no any numbers. When you finish with one list you can replace it with another 10-50 commands/datarefs.