General information, rules

Question

In this section users can collaborate on making SimVimX conversions for custom aircraft models, sharing and discussing their conversion files.

Some notes about conversions:

1. All aircraft models included in X-Plane by default do not required to make user conversions for them.  If some of these aircraft use few custom datarefs along with the default ones, the conversions for them are already included in SimVimX.

2. Several custom conversions for the aircraft models listed o the SimVimX website page are freely available for download as separate conversion files, which can be used with the plugin right away (placing files into the SimVimX plugin /conv/ folder, or loaded into the conversion tool to continue working on them, in case some parameters still require conversion for that model.

I'm continue working on these plane conversions, checking all I/O functions but you can  post your suggestions here about some entries that are not included yet.

Answer 1

!! Rules for creation conversions for public sharing:

1. Before making a conversion for a custom plane, assign needed I/O  in the CONFIG mode of this config/conversion tool to add them to the main data config file (.cfg),  and then  test every assigned SimVimX keyword first without conversion with your plane.
    
2. If a parameter keyword is working as-is it doesn't need to be "converted" even if your plane model uses custom datarefs. If you assign all the keywords correctly, many of your plane controls probably will work as-is.
    
3. If you see that your plane model uses "standard" X-Plane dataref/command for some function, it's not considered as a "custom" and once you assigned such parameter in the config file it should work as-is.
    
4. The conversion tool doesn't allow the use of standard X-Plane commands and datarefs (such as "sim/cockpit2/..."). This is done to prevent confusion and save time, as all standard commands/datarefs needed for cockpit functionality are already assigned to relevant SimVimX keywords, and will work by default, so making a conversion using the same datarefs would be redundand.
    
5. Use only the relevant I/O SimVimX keywords in the configurator maps when creating the main config file, don't assign random keywords for your custom conversion.
    
6. If you can't find suitable parameter to assign in the existing list, you can ask me to add it to the database and configurator. Before that, you can temporary use custom I/O keywords from the [Generic I/O"] section for functions that you need to test.

Please carefully read the complete guide of conversion here before making conversion.

Comments

I used Ground_Call for

laminar/B738/push_button/grd_call

But, new version of simvim converted Ground_Call to Ground_Crew_Call.

Ground_Crew_Call seems not used laminar/B738/push_button/grd_call.

Can you check your new Ground_Crew_Call at SimVimX.dat ? please