When you are creating a scenario in VR-Forces, you usually have complete access to all of the simulation objects in a simulation model set (SMS) and can create as many as you want. However, in the real world, commanders do not have unlimited resources. They are constrained by their Order of Battle (OOB), which specifies the men and material available in a hierarchical structure. VR-Forces now supports the creation of OOBs. You create an Order of Battle in the context of a scenario. However, once you create an OOB, you can export it and then import it into other scenarios. This lets you quickly create new scenarios that use the same OOB for training or scenario development.
Here’s a quick look at OOBs. (As always, full details are in VR-Forces Users Guide.)
To create a new OOB:
If you are working from an existing scenario, you can add the objects in the scenario to the OOB individually or all at once. You can edit the OOB by adding, removing, renaming, and organizing into units.
Once you have an OOB, you can populate a scenario by adding objects from the OOB to the scenario. You can use an OOB along with the Simulation Objects Palette (the honor system) or you can constrain scenario creators to only use the OOB for their exercise.
There is a key difference between creating objects from an OOB and from the Simulation Objects Palette. When you select an object in the Simulation Objects Palette, you can create as many instances of that object as you want. When you create an object from an OOB, you can create only one object for each object on the palette. If your order of battle needs 25 HMMWVs, then you add 25 HMMWVs to the OOB. When you create a scenario, you can add one HMMWV to the scenario for each one in the OOB, but no more than that.
Suppose you want scenario creators to use the Order of Battle to create simulation objects instead of the Simulation Objects Palette. The simple way to do this is to choose View -> Window Layouts -> ORBAT Scenario Creation. This window layout adds the OOB Palette to the window and removes the Simulation Objects Palette. This is the honor system approach, since anyone who understands how to hide and view GUI components can just open the Simulation Objects Palette.
If you really want to hide the Simulation Objects Palette, do the following:
In the GUI, open the Window Layout Manager, delete the Scenario Creation layout (you can always restore it from the factory GUI layout file), and close VR-Forces. Then in ./appData/settings/vrfGui/default_guiSimpleScenarioPlayer.gui comment out the line that configures the Simulation Objects Palette:
<!-- <menuitem itemname="EntityCreationPalette"/> -->
Restart VR-Forces. Use the ORBAT Scenario Creation window layout. Users will not be able to open the Simulation Objects Palette.