Custom data conversion for those aircraft models for which not all SimVim parameters work by default. You can open or join the discussion about conversion, custom datarefs/commands for your plane model.

The downloaded conversion (*.dat) file must be placed in the folder of the aircraft it is used for - the same folder where the aircraft's "*.acf" file is located.

If your plane model conversion file already exists and available for download in the table below, then you don't need to make your own conversion, just use it.

1. If the data file for your aircraft is available but not finished yet and you want to  participate in editing this conversion (and know how to do this), please ask us to give you access to the community converter by the links (on the names)  in the table below.  Also, you can ask us to add an aircraft you want to the list. 

2.  Before using  the community converter (and getting access to it), you can try to use (and learn how it works) the "Personal Converter"  for creating your personal .dat file only.

The community converter is he 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:  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.

Click "Link to Converter" (plane name) to edit the aircraft if you have access (ask if you need it):

Link to Community Converter Conversion File Converted Comments
DA-62 - Aerobask Download List Finished (updated 21 July)
TBM900 - HotStart Download List Finished (updated 21 July)
Piper PA-44 Seminole, Alabeo planned
Cessna 172 - AirFoil Labs Download List
King Air 350 - AirFoil Labs Download List updated 21 July
B1900 - Carenado Download List updated 21 July
Baron B58 - Carenado List Just started
Embraer E195 - SSG Download List --> Discussion    (file updated 21 July)
Embraer E195  - X-Crafts Ask
Challenger CL300 - DDen Download List updated 21 July
Eurocopter EC135 - RotorSim Download List updated 21 July
MD-80 - Rotate Download List updated 21 July
Boeing B757 - FlightFactor Download List Note: please use correct parameter names (updated 21 July)
Boeing B727 - FJS Download List Ask if you want to edit (<20 params currently) updated 21 July
Airbus A319 (320) ToLiss Download List Inconsistent parameters names present!
Airbus A320 JarDesign Download List in progress, about 110 parameters so far..
Airbus A320 - FlightFactor Download List The "publish.txt" file is needed
Robinson R22 - DreamFoil List Just started, few parameters
AS350B3 - DreamFoil


Note:  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.


Apr 9 in Custom Aircraft by

1 Answer


Note: 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.

The very bad thing is when the plane developer script checks every custom dataref for every virtual switch in every X-Plane frame , and in this case, when you use standard commands  for a switch  that should definitely work, but the standard dataref always resets to the position of the virtual switch because the plane script checks it in every program cycle.

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.

May 2 by