Why are custom datarefs used so excessively in some aircraft models? In this case every assigned parameter, for any input/output will work either with standard X-Plane functions or with a function programmed in the SimVimX plugin, with external SimVimPanel program or hardware gauges: As example, you can download the "barebone" King Air C90 in the Download section. A virtual plane model has no any cockpit interior, no instrument panels, no virtual switches and annunciators, and no custom scripts. If X-Plane has not yet implemented this feature, and the virtual plane model does not include it either, the RSC parameter works with a function programmed in the SimVimX plugin, and this function may have different behaviour depending on the aircraft type or equipment model type.ĥ. If the SimVimX has this functionality programmed in the plugin, the conversion can not be needed.Ĥ. In this case the SimVimX parameter should be converted to the custom aircraft data. X-Plane has not implemented this functionality, but the virtual plane model includes it and uses its own commands/datarefs for it. In this case the SimVimX/RSC parameter may need to be converted to the custom aircraft data, but no necessary.ģ. X-Plane has implemented this functionality, but the virtual plane model uses its own custom commands/datarefs for it. The real switch assigned to the SimVimX parameter works as is, turning the aircraft system on or off, and the virtual switch image is also changed:Īlso, the SimVimX may have a specific function programmed for this systemĢ. Also, for toogle operation the related standard X-Plane command or two (up/dn) commands may be used. The aircraft developer uses only position bitmaps for the switch image, and the standard X-Plane dataref is used as refernce value for changing the switch image on the screen (0=OFF, 1=ON). Let's see for example how a simple toggle switch assigned to SimVImX parameter for some aircraft system works with different aircraft models which can be one of the X-Plane standard, or free downloadable model or payware model.ġ. Real panel control and virtual plane data As a result, if we take any 10 different virtual aircraft models of the same plane (from different developers) we will see thousands of datarefs/commands instead of tens (maybe hundreds). The X-Plane development team can gradually add more commands / data for new functions that can be used by aircraft developers directly in their plane models.īut, most of aircraft developers create hundreds of their own "custom" commands/datarefs for every simplest function though they even have no any reason for this, because they would easily use existing X-Plane commands/datarefs instead, for most functions. The same control switches are represented on each plane, so we could only expect ONE set of commands for ALL planes, as was originally done in X-Plane, which can potentially have all the necessary command names for the controls found in any cockpit. In real aviation there are almost no "unique" controls that are found only in one specific aircraft, most of them are unified for all aircraft. What about datarefs and command in X-Plane? The SimVimX data structure allows to have the configurator database compact, having unified names for all controls, independant of plane type and especially model developer.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |