VR-Forces 4.0.4 Class Documentation: VR-Forces 3.12.x to 4.0.3 Simulation Model Set Changes

All Entities

General:
- All OPE and sysdef files have every instance of "tick-period-uses-real-time" set to False by default now instead of True.
- A new general parameter has been added to entities to determine whether they can use the new ground rail movement system (see ground entities movement models below). This parameter looks like the following: (using-rail-movement False)
Weapon Systems. "target-selection" controllers have an additional parameter in the "target-selection-criteria" as follows: (fire-with-spot-report-only False). The parameter determines whether the target selection controller will fire at an entity automatically or not based on the spot report.
Movement Models:
- All entity movement systems have an added "preload-terrain-controller" to allow for entities moving in terrains that page data in (such as VR-TheWorld terrains) to page that data in before it gets to the foreseeable un-paged terrain area. Without the controller, entities would page the terrain data in at the time it enters an area where the data has not yet been paged in.
- Systems including the "path-movement" controller have an added parameter that looks like the following: (register-vrf-specific-tasks True)
Other Systems:
- Systems with "spot-report-generator" now have a "radio-name" field as follows: (radio-name "default")
- Systems with "laser-controller" can be enabled or disabled with the following parameter: (is-enabled True)

Damage Models. Ground entities have changed their damage tables against "Guided anti-ship missile damage" tables to use the cruise missile damage instead of the standard missile damage. For instance "heavy-armor-vs-missile.dmg" is now "heavy-armor-vs-cruise-missile.dmg"
Movement Models:
- Ground movement systems have been split into various sysdef files to support multiple movement systems, as follows:
  - Vehicles can drive on roads and now use a "combined-movement-system" to switch between them. See "ground-wheels-road.sysdef" and "ground-wheels-road-default.sysdef" and "Technical-Truck_1_1_1_222_27_1_-1_-1.ope".
  - Several systems now include the "rail-path-movement" controller if they are to use the road following options as well as a "system-switch-controller" to switch between regular and rail movement systems.
- Disaggregated movement systems have a "convoy-task-controller" necessary for allowing for convoy movement tasks on disaggregated aggregates.

Counter Measures. Several air entities have counter measures defined in the systems section of their OPE files. It is usually defined in an "other" field and more commonly "other-4". See "US-fighter-air-defense-fixed-wing-platform_1_1_2_225_1_-1_-1_-1.ope".
Movement. "flight-kinematics" actuator now has an added parameter for a drag coefficient defined as follows: (drag-coefficient 0.100000)

General:
- Several entities now have a "contact-fusion" controller to tie in several sensor systems into a single place. These controllers have associated connections to connect the sensor ports to the contact-fusion controller for entity detection. New lifeforms should use the "contact-fusion" controller.
- Several entities now have a "target-selection" controller much like other entities. These controllers have associated connections to connect the target selection controller. New lifeform entities should use the "target-selection" controller.
Movement. All movement systems for lifeforms have removed the "human-patrol" controller.