VR-Forces 4.0.3 to 4.0.4 Simulation Model Set Changes

Table of Contents

• Flight Command Controllers
• Weapon Interface
• Radar Modes
• Weapon Enhancements
• Range Rings
• Ammo Select Tables

Changes to the SMS are organized by component or system type.

Flight Command Controllers

Air domain Movement Systems. The flight-command-controller was added to Fixedwing and rotary-wing entities to handle new flight tasks. (For details, please see fixed-WingFlightCommandController.h and rotaryWingFlightCommandController.h.) If you have created your own air domain movement systems, you must add this controller to take advantage of these new tasks and behavior.

Weapon Interface

The target-priorities parameters have moved. They are no longer part of the target selection controller. They are now in the weapon controllers inside the weapon systems, as follows:

• target-selection-controller:
  • Target priorities have been removed from the target selection controller (moved into weapons).
  • The target-select-controller:weapon-system connections have been removed. The target-selection-controller to sensor connections remain.
  • The controller uses DtComponentDescriptor (component-descriptor) for the descriptor type).

Weapon systems:

• Target priorities have been added into the weapon controllers. The target-selection-criteria parameter has been renamed to targeting-control.
• Target priority metadata has been removed.
• For ballistic weapons, the system:target-list connection is now <controllerName>:target-to-acquire. Please see 125mm-gun.sysdef for an example.
• Missile Weapons. The system:target-list input connection has been removed.

Laser designators have the same changes as weapon systems. They also now have the parameter integrated-with-launcher, which determines how target input works (either from the launcher controller, if integrated, or the target selection controller directly if not).

Apache. The laser designator that went along with the laser-guided-hellfire-missile launcher has been moved into the launcher.

The laser-guided-hellfire-missile-launcher system has the following changes:

• Uses the new controller integrated-laser-guided-launcher-controller.
• The laser designator that used to be on the entity is now in this system.
• A new connection (connect missile-launcher:target-to-acquire lasercontroller:target-list) was added to represent the missile launcher providing targets to the laser designator.

Radar Modes

Emitter systems now defines a radar-mode-list, each one of which defines a beam-list so these can be switched at runtime. For more information, please see Section 7.5, "Configuring Emitters", in VR-Forces Configuration Guide.

Weapon Enhancements

In weapon systems the munition-wrapper resource "ammo" has been removed. Individual munitions are now regular resources.

Ballistic guns have two changes:

• Burst fire. Some ballistic guns now fire in bursts. The rounds-per-minute and extra-time-between-bursts parameters were added to the ballistic gun controller.
• Magazine-based reloading. The rounds-per-magazine parameter was added for magazine-based reloading.

Range Rings

• Weapon systems. The range-name parameter was added to ballistic weapon actuators and missile launcher controllers. This is the display name for range items associated with this weapon displayed in the GUI.
• Aggregate OPE files. The range-name parameter was added. The combat-rangecontroller was added to define range rings that can represent disaggregation ranges or subordinate weapon systems.
• Munition OPE files. The range-name parameter was added to the missile/torpedo entity definition to display missile range.

Ammo Select Tables

For weapons that fire a burst, hit probability is for the whole burst.

New weapons have been added, so if you have made your own damage system, you may have to make a new damage table to add new mappings.

[<< Migrating from VR-Forces 3.12 to 4.0.4] [Home] [Top of Page] [Changes to Support the Fire At Target Task >>]