To properly display this page you need a browser with JavaScript support.
Create Objects vsTASKER can convert all OMT data structures to C++ data representation and DataModels.
Doing so, it will become straightforward to import/export data from/to the RTI using either 1.3 or 1516 version.
When the checkbox is ticked, all data structures will be created into the selected Model folder.
A new folder can be created by changing the name on the list-box field.
vsTASKER will use the name of the folder to automatically name the basic, enum, struct and array DataModels.
These structures will contains all C++ type definitions extracted from the OMT database.
Objects and Interactions will all be listed with the same name as in the OMT database, prefixed with hla .
Generate FedItems When checked, this option will force automatic generation of all OMT Objects and Interactions as FedItems (one per each) as Publisher and Subscriber.
If they already exist, confirmation for replacement will be asked.
With huge federation, this option can lead to numerous (and useless) FedItems generation.
Most of the time, it is a better practice to create FedItems (in publish or subscribe mode) manually, from the SOM panel.
Optimize Selection When this option is selected, vsTASKER will only select Objects and Interactions that are used (enabled) as FedItem in the SOM part.
What to Generate To force vsTASKER to generate Entity Catalogs based on OMT Class definitions, simply check the Objects and/or Interactions that will be used in entities.
They will be generated in Entities::Catalogs and will be using with their counterpart DataModel.
Invert Selection Change the selection mode of the above list.
Mapping Select in this panel all objects whose corresponding DataModel must be attached to new created entity in the Catalog.
