|
VR-Forces
Computer Generated Forces - VR-Forces
The Complete Simulation Solution
VR-Forces is a powerful and flexible simulation environment for scenario generation. It has all the necessary features for use as a tactical leadership trainer, threat generator, behavior model testbed, or Computer Generated Forces (CGF) application.
Simple Scenario Editing
VR-Forces Computer Generated Forces provides an intuitive GUI that allows you to build scenarios by positioning forces, creating routes and waypoints, and assigning tasks or plans with a simple point and click. You can lay down the basic outline on a 2D tactical map, and then switch to the 3D scenario editing mode to accurately position entities within a complex urban environment. Turn on XR mode to gain a big picture understanding of your scenario, without losing your 3D perspective. Bring up a 3D inset view for any entity to see the world from its perspective.
Powerful Simulation Engine
VR-Forces comes with simulation models for a wide variety of battlefield entities and weapon systems. During scenario execution, VR-Forces vehicles and human entities interact with the terrain, follow roads, move in convoys, avoid obstacles, communicate over simulated radios, detect and engage enemy forces, and calculate damage. Through multi-resolution modeling, VR-Forces can switch between aggregate and entity level movement models “on-the-fly” based on scenario events such as sensor detection or area of interest.

Features
High Level
- C++ toolkit to extend or embed in customer application
- Distributed simulation engine with remote GUI control
- Aggregate unit and entity modeling
- Correlated simulation and visualization
- HLA and DIS compliant
- Terrain Agile, including streaming terrain
- Batch mode for analysis
- Real-time and non-real-time operation
- GUI-based entity and parameter editors
- Distributed architecture for greater scalability
- Plan view (2D), stealth (3D), and exaggerated reality (XR) views
- Entity-specific and global planning.
- Lua scripting for complex tasks
- Helpful utilities: Entity Editor, OPD Editor, Scenario Merge, Terrain Database Tool
CGF Features
Entity tasking:
- Movement tasks for ground, surface, air, subsurface entities, such as Move to Location, Move to Waypoint, Patrol Along Route
- Aircraft-specific movement, such as Fly Altitude, Fly Heading, takeoff and landing
- Engagement tasks, such as Fire Cruise Missile, Lase Target, Fire at Target
- Communication tasks, such as Send Text Message and Send Radio Task.
Entity state management. Instantly set entity state, such as heading, altitude, speed, resources, rules of engagement, and formation.
Entity planning. Plans are created through the GUI and can include:
- All tasks.
- All set state commands
- Conditional tests, such as Entity in Area, Entity Altitude, and Entity Destroyed
- Looping
- Global commands, such as create entity, create tactical graphics, send entity plan.
- User-defined Lua tasks
Indirect fire. Artillery fire and ballistic missile fire controlled independently of entities.
Tactical graphics. Create points, lines, routes, areas, text, and other graphics for informational purposes and to guide entity behaviors.
Overlays. Organize tactical graphics in layers for easy management
Aggregate modeling:
- Preconfigured aggregates.
- Ability to add preconfigured aggregates
- Ability to create new formations
- True and psuedo-aggregate state modeling. That is, aggregates can be represented by all the individual members or by a single notional entity.
- Automatic aggregation and disaggregation of aggregate state to facilitate entity movement, combat engagement, and screen management.
Entity Editor for easily managing entity models and parameters.
OPD Editor for complete management of all entity parameters.
Spot reports and fog-of-war
Manage force hostility relationships
Launch chaff and flare counter measures
Launch tactical smoke
Environment. Set weather conditions and time-of-day.
Scripted tasks. Create new tasks using the Lua scripting language using basic task building blocks.
Scenario Merge tool to merge scenarios created by individual members of a project team.
GUI Features (from VR-Vantage)
- Animations and Entity Effects
- Contrails. A trailing effect for fixed-wing aircraft.
- Explosions. Animations for exploding ordnance.
- Fire and detonation lines. Fire events and detonation events are displayed with lines between the source and destination of the event.
- Flames. Flame animations are displayed for destroyed objects.
- Footprints. A trailing effect for humans.
- Missile trails. A trailing effect for missiles.
- Muzzle flash. Animation for ballistic guns, such as tank cannons and rifles.
- Shadows. Entities can cast shadows on the ground.
- Smoke plumes. Animation of smoke rising from a destroyed entity.
- Tactical smoke. Display smoke plumes created when VR-Forces entities fire smoke ordnance.
- Track histories. Display 2D or 3D ribbons that show the path a moving entity has taken.
- Wakes. A trailing effect animation for surface entities.
- Treadmarks. A trailing effect animation.
Performance
- File caching. Terrain and model data is cached for quick loading.
- Instancing. Models can share resources such as geometry and texture to improve performance.
- Interest management. An implementation of HLA data distribution management that improves performance of simulation with many entities.
- Statistics viewer. Performance statistics. Includes OSG statistics and VR-Vantage-specific statistics.
Third Party Library Support
- DI-Guy characters. Human entities and some animals are displayed using Boston Dynamics, DI-Guy characters.
- GL Studio cockpits. Cockpit displays for vehicles and aircraft created with GL Studio.
- Silverlining environment. Lighting, clouds, moon, and sun are rendered using SilverLining software.
- SpeedTrees. High quality trees using SpeedTree software.
Information Display
- 2D entity labels. Name, entity type, and other entity information.
- 3D entity labels. Name, entity type, and other entity information can be displayed on an overlay panel.
- Compass display. A compass overlay shows the heading of the observer.
- Height-above-terrain lines. Displays the height of aircraft and tactical graphics vertices that are above ground level.
- Intervisibility. Visualizes line-of-sight relationships.
- Measurement unit customization. Users can choose the measurement unit used in the GUI and dialog boxes, such as meters vs. feet and kilometers vs. miles.
- Overlays. A way of organizing tactical graphics as if they were drawn on clear plastic overlays. VR-Vantage displays overlays sent from VR-Forces.
- Radio communications lines. Squawk indicators and communications lines are displayed when radio messages are sent between entities.
- Tactical graphics display. Displays tactical graphics, such as routes, waypoints, and areas, sent by VR-Forces or applications using the Remote Draw API.
- Visualization of feature data. Display lines and points to represent features.
Entity Modeling
- 2D icons. Entities are represented by MIL-STD 2525B icons. Users can chnage the icons used.
- 3D colorized model set. Cartoon-like models used in XR observer mode.
- 3D model set. Entities are displayed as realistic 3D models, with articulated parts.
- Aggregate visualization. Aggregate entities are visualized using translucent volumes. Aggregate type is represented by 2D icons.
- Emitter volumes. Displays electromagnetic emissions, such as radar, for entities in 2D and 3D.
- GUI-based model mapping. Entity types are mapped to VR-Vantage element definitions using the GUI rather than text-based configuraiton files.
- Icon scaling. Increase or decrease the size of 2D icons to reduce clutter and improve viewability of the display.
- Model scaling. Increase or decrease the size of 3D models to improve visibility of models at the expense of realism.
Observer Management
- Attach modes. You can attach the observer to entities so that it moves as the entity moves, maintaining the same relationship to the entity.
- Inset views. Secondary windows that let you view several parts of the simulation at the same time.
- Keyboard navigation. Navigate the virtual world from the keyboard using game-like keyboard mappings.
- Mouse navigation. Pan and zoom the view and move the observer using the mouse.
- Multiple observers. Configure multiple observers to quickly switch between different views and display configurations.
- Saved views. Users can capture observer views and save them for reloading in later sessions.
- Zoom observer. Magnify the view without moving the observer.
Terrain
- Contour lines. Contour lines show the gradient of the terrain.
- Grid lines. Terrain grid lines.
- Streaming terrain. Supports streaming terrain using osgEarth.
- Terrain agility. Create terrains using elevation, image, and feature data from many sources.
- Terrain coloring by elevation. change the color of the terrain based on its elevation.
- Terrain scaling. Exaggerate the scale of the terrain to display terrain relationships that might not be obvious in a realistic display.
- Wireframe display. Display the terrain polygons.
- Ground clamping. In cases where the VR-Vantage terrain is not well synchronized between exercise participants, entities can be clamped to the terrain.
Miscellaneous
- Audio effects. You can map WAVE files to entities and detonation events.
- Ephemeris model. The ambient lighting in the scene varies with the time of day and date.
- Persistent settings. VR-Vantage remembers many display settings from one session to the next.
- Remote graphics. VR-Vantage displays graphics sent by remote applications using the VR-Vantage Remote Draw API.
- Saved display engine configurations. Users can save and reload display engine configurations, which specify the windows, channels, and observers.
- Scenes. Collectively, the environment, time of day, and optionally, the terrain.
- Sensors. Simulates how the scene would look through night vision goggles or infrared.
- Stereoscopic display. Supports active stereo, anaglyphic stereo, and polarized stereo.
- Streaming video. Outputs a video stream of the display window in formats such as MPEG and GStreamer.
- Trajectory smoothing. Calculates a smooth transition between a dead-reckoned location and the actual location following an entity update.
- View control support. Change the observer view in response to remote messages that use the VR-Vantage Control Toolkit.
VR-Forces Toolkit
-
Simulation API. The primary API for the back-end. Does all simulation processing.
- Remote Control API. Allows an application to control the simulation engine. The VR-Forces front-end uses the Remote Control API to communicate with the back-end.
- GUI API. Essentially the VR-Vantage API with additional classes for VR-Forces.
- Terrain API. Manages all terrain activity such as terrain intersections, paging terrain, streaming terrain.
- Many examples of how to modify the front-end and back-end.
Specs
VR-Forces Versions
VR-Forces Versions
VR-Forces 4.1.1 Released April 10, 2013
|
Built with: FLEXlm 11.8, VR-Link 4.0.5, Qt 4.7.4 HLA Support: MÄK RTI 4.1.1 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
Operating System
|
Windows XP (32 bit only), Windows 7, Vista
|
Red Hat Enterprise Linux 5
|
Compiler
|
MS Visual C++ 8.0
MS Visual C++ 10.0 32 bit and 64 bit
|
Default compiler (32 bit)
|
VR-Forces 4.1 Released January 31, 2013
|
Built with: FLEXlm 11.8, VR-Link 4.0.5, Qt 4.7.4 HLA Support: MÄK RTI 4.1.1 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
Operating System
|
Windows XP (32 bit only), Windows 7, Vista
|
Red Hat Enterprise Linux 5
|
Compiler
|
MS Visual C++ 8.0
MS Visual C++ 10.0 64 bit
|
Default compiler (32 bit)
|
VR-Forces 4.0.4 Released July 2, 2012
Maintenance support expires January 31, 2014
|
Built with: FLEXlm 11.8, VR-Link 4.0.5, Qt 4.7.4 HLA Support: MÄK RTI 4.0.4 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
Operating System
|
Windows XP (32 bit only), Windows 7, Vista
|
Red Hat Enterprise Linux 5
|
Compiler
|
MS Visual C++ 8.0
MS Visual C++ 9.0 32 bit and 64 bit MS Visual C++ 10.0 64 bit
|
Default compiler (32 bit)
|
VR-Forces 4.0.3 Released February 9, 2012
Maintenance support expires January 31, 2014
|
Built with: FLEXlm 11.8, VR-Link 4.0.3, Qt 4.7.4 HLA Support: MÄK RTI 4.0.4 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
Operating System
|
Windows XP (32 bit only), Windows 7, Vista
|
Red Hat Enterprise Linux 5
|
Compiler
|
MS Visual C++ 8.0
MS Visual C++ 9.0 32 bit and 64 bit MS Visual C++ 10.0 64 bit
|
Default compiler (32 bit)
|
VR-Forces 4.0.2a Released December 16, 2011 VR-Forces 4.0.2 Released October 31, 2011
Maintenance support expires January 31, 2014
|
Built with: FLEXlm 11.8, VR-Link 3.13.2, Qt 4.6.3 HLA Support: MÄK RTI 4.0.4 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
Operating System
|
Windows XP, Windows 7, Vista
|
Red Hat Enterprise Linux 5
|
Compiler
|
MS Visual C++ 8.0
MS Visual C++ 9.0 32 bit and 64 bit
|
Default compiler (32 bit)
|
VR-Forces 4.0.1 Released August 31, 2011
Maintenance support expires January 31, 2014
|
Built with: FLEXlm 11.8, VR-Link 3.13.2, Qt 4.6.3 HLA Support: MÄK RTI 4.0.4 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
Operating System
|
Windows XP, Windows 7, Vista
|
Compiler
|
MS Visual C++ 8.0
MS Visual C++ 9.0 32 bit and 64 bit
|
VR-Forces 4.0 Released February 3, 2011
Maintenance support expires January 31, 2014
|
Built with: FLEXlm 11.8, VR-Link 3.13.2, Qt 4.6.3 HLA Support: MÄK RTI 4.0.2 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
Operating System
|
Windows XP, Windows 7, Vista
|
Compiler
|
MS Visual C++ 8.0 |
VR-Forces 3.12.0.2 Released September 15, 2011 VR-Forces 3.12.0.1 Released January 26, 2010 VR-Forces 3.12 Released July 23, 2009
Maintenance support expires June 30, 2013
|
Built with: FLEXlm 11.6, VR-Link 3.13.2, Qt 4.5.0 HLA Support: MÄK RTI 3.3.2 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
Operating System
|
Windows XP/ Vista (8.0, 9.0)/ Windows 7 (8.0, 9.0) |
Red Hat Enterprise Linux 4 Red Hat Enterprise Linux 5
|
Compiler
|
MS Visual C++ 7.1, 8.0 and 9.0 |
Default compiler |
VR-Forces 3.11.0.2 Released April 8, 2009 VR-Forces 3.11.0.1 Released November 14, 2008 VR-Forces 3.11 Released March 24, 2008 No longer supported.
|
Built with: FLEXlm 11.4, VR-Link 3.11.1, Qt 4.3.3 HLA Support: MÄK RTI 3.2 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
Operating System
|
Windows XP/ Vista (8.0 only) |
Red Hat Enterprise Linux 4 Red Hat Enterprise Linux 5 Fedora 7 |
Compiler
|
MS Visual C++ 7.1 and 8.0 |
Default compiler |
VR-Forces 3.10.1 Released June 26, 2007 VR-Forces 3.10 Released December 19, 2006 No longer supported. |
Built with: FLEXlm 10.8, VR-Link 3.10.1, Qt 3.3.5
HLA Support: MÄK RTI 3.1
RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper)
DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
Operating System
|
Windows 2000/XP/ Vista (8.0 only) |
Red Hat Enterprise Linux WS 3* Red Hat Enterprise Linux 4** Fedora Core 3** |
Compiler
|
MS Visual C++ 7.1 and 8.0 |
*GNU C++ (gcc) 3.2.3 **GNU C++ (gcc) 3.4.4 |
VR-Forces 3.9.2 Released August 16, 2006
VR-Forces 3.9.1 Released May 4, 2006
VR-Forces 3.9 Released February 7, 2006
No longer supported.
|
Built with: FLEXlm 9.2, VR-Link 3.9.6, Qt 3.3.5 HLA Support: MÄK RTI 2.4.2 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
Operating System
|
Windows 2000/XP |
Red Hat Enterprise Linux WS 3* Red Hat Enterprise Linux WS 4** Fedora Core 3** |
Compiler
|
MS Visual C++ 6.0 SP5 and 7.1 |
*GNU C++ (gcc) 3.2.3 **GNU C++ (gcc) 3.4.4 |
VR-Forces 3.8 Released March 21, 2005
No longer supported.
|
Built with: FLEXlm 9.2, VR-Link 3.9.3, Qt 3.3.1 HLA Support: MÄK RTI 2.2 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
Operating System
|
Windows 2000/XP |
Red Hat Enterprise Linux WS 3 |
Compiler
|
MS Visual C++ 6.0 SP5 and 7.1 |
GNU C++ (gcc) 3.2.3 |
VR-Forces 3.7.1 Released September 10, 2004
No longer supported.
|
Built with: FLEXlm 9.2, VR-Link 3.9.1, Qt 3.3.1 HLA Support: MÄK RTI 2.2 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
Operating System
|
Windows 2000/XP |
Red Hat Linux 9.0 |
Compiler
|
MS Visual C++ 6.0 SP5 and 7.1 |
GNU C++ (gcc) 3.2.2 |
VR-Forces 3.7 Released July 22, 2004
No longer supported.
|
Built with: FLEXlm 9.2, VR-Link 3.9.1 (3.9.1a for IRIX), Qt 3.3.1 HLA Support: MÄK RTI 2.2 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
SGI-MIPS |
Operating System
|
Windows 2000/XP |
Red Hat Linux 9.0 |
IRIX 6.5 |
Compiler
|
MS Visual C++ 6.0 SP5 and 7.1 |
GNU C++ (gcc) 3.2.2 |
MipsPro7.4.2 C++ compiler |
VR-Forces 3.6 Released February 18, 2004
No longer supported.
|
Built with: FLEXlm 9.2, VR-Link 3.9.1 (3.9.1a for IRIX), Qt 3.1.2 HLA Support: MÄK RTI 2.1 (2.1a for IRIX) RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
SGI-MIPS |
Operating System
|
Windows 2000/XP |
Red Hat Linux 8.0 |
IRIX 6.5 |
Compiler
|
MS Visual C++ 6.0 SP5 |
GNU C++ (gcc) 3.2 |
MipsPro7.3 C++ compiler |
VR-Forces 3.5.1-ngc Released December 18, 2003
No longer supported.
|
Built with: FLEXlm 6.0, VR-Link 3.8.1-ngc, Qt 3.1.2 HLA Support: MÄK RTI 2.0.3-ngc RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
SGI-MIPS |
Operating System
|
Windows 2000/XP/NT |
Red Hat Linux 8.0 |
IRIX 6.5 |
Compiler
|
MS Visual C++ 6.0 SP5 |
GNU C++ (gcc) 3.2 |
MipsPro7.3 C++ compiler |
VR-Forces 3.4-ngc Released July 8, 2003
No longer supported.
|
Built with: FLEXlm 6.0, VR-Link 3.8.1-ngc, Qt 3.1.2 HLA Support: MÄK RTI 2.0.1-ngc RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
SGI-MIPS |
Operating System
|
Windows 2000/XP/NT |
Red Hat Linux 8.0 |
IRIX 6.5 |
Compiler
|
MS Visual C++ 6.0 SP5 |
GNU C++ (gcc) 3.2 |
MipsPro7.3 C++ compiler |
VR-Forces 3.3-ngc Released March 6, 2003
No longer supported.
|
Built with: FLEXlm 6.0, VR-Link 3.8-ngc, Qt 3.0.5 HLA Support: MÄK RTI 2.0-ngc RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
SGI-MIPS |
Operating System
|
Windows 2000/XP/NT |
Red Hat Linux 7.2 |
IRIX 6.5 |
Compiler
|
MS Visual C++ 6.0 SP5 |
GNU C++ (gcc) 3.0.2 |
MipsPro7.3 C++ compiler |
VR-Forces 3.2-ngc Released November 26, 2002
No longer supported.
|
Built with: FLEXlm 6.0, VR-Link 3.7.3-ngc, Qt 3.0.5 HLA Support: MÄK RTI 1.3.7-ngc RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
SGI-MIPS |
Operating System
|
Windows 2000/XP/NT |
Red Hat Linux 7.2 |
IRIX 6.5 |
Compiler
|
MS Visual C++ 6.0 SP5 |
GNU C++ (gcc) 3.0.2 |
MipsPro7.3 C++ compiler |
VR-Forces 3.1-ngc Released October 18, 2002
No longer supported.
|
Built with: FLEXlm 6.0, VR-Link 3.7.3-ngc, Qt 3.0.5 HLA Support: MÄK RTI 1.3.7-ngc RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
SGI-MIPS |
Operating System
|
Windows 2000/XP/NT 4.0 |
Red Hat Linux 7.2 |
IRIX 6.5 |
Compiler
|
MS Visual C++ 6.0 SP5 |
GNU C++ (gcc) 3.0.2 |
MipsPro7.3 C++ compiler |
VR-Forces 3.0-ngc Released September 3, 2002
No longer supported.
|
Built with: FLEXlm 6.0, VR-Link 3.7.3-ngc HLA Support: MÄK RTI 1.3.7-ngc, DMSO RTI NG v4, v6 RPR FOM 0.5, 0.7, 0.8, 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
Operating System
|
Windows 2000/XP/NT 4.0 |
Compiler
|
MS Visual C++ 6.0 |
VR-Forces 2.1.1-ngc Released June 13, 2002
No longer supported.
|
Built with: FLEXlm 6.0, VR-Link 3.7.2-ngc HLA Support: MÄK RTI 1.3.6-ngc, DMSO RTI NG v3, v4 RPR FOM 0.5, 0.7, 0.8, 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
Operating System
|
Windows 2000/XP/NT 4.0 |
Compiler
|
MS Visual C++ 6.0 |
VR-Forces 2.1-ngc Released April 29, 2002
No longer supported.
|
Built with: FLEXlm 6.0, VR-Link 3.7.1-ngc HLA Support: MÄK RTI 1.3.6-ngc, DMSO RTI NG v1, v2, v3 RPR FOM 0.5, 0.7, 0.8, 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
Operating System
|
Windows 2000/XP/NT 4.0 |
Compiler
|
MS Visual C++ 6.0 |
VR-Forces 2.0-ngc Released November 02, 2001
No longer supported.
|
Built with: FLEXlm 6.0, VR-Link 3.7-ngc HLA Support: MÄK RTI 1.3.5-ngc, DMSO RTI NG v1, v2, v3 RPR FOM 0.5, 0.7, 0.8, 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
Operating System
|
Windows 2000/XP/NT 4.0 |
Compiler
|
MS Visual C++ 6.0 |
VR-Forces 1.3 Released October 23, 2000
No longer supported.
|
Built with: FLEXlm 6.0, VR-Link 3.6 HLA Support: MÄK RTI 1.3.3, DMSO RTI 1.3v4, 1.3v5, 1.3v6 RPR FOM 0.5, 0.7, 0.8, 1.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
Operating System
|
Windows 95/98/NT 4.0 |
Compiler
|
MS Visual C++ 6.0 |
VR-Forces 1.3-ngc No longer supported.
|
Built with: FLEXlm 6.0 (for all configurations except Linux which uses FLEXlm 6.1), VR-Link 3.6-ngc HLA Support: MÄK RTI 1.3.3-ngc, DMSO RTI NG v1, v2, v3 RPR FOM 0.5, 0.7, 0.8, 1.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
SGI-MIPS |
Operating System
|
Windows 95/98/NT 4.0 |
Red Hat Linux 6.0 (Linux 2.2.5) |
IRIX 6.5, n32 NT Visual Workstation (NT 4.0) |
Compiler
|
MS Visual C++ 6.0 |
gcc version egcs-1.1.2 |
MipsPro 7.2.1 C++, MS Visual C++ 6.0 |
VR-Forces 1.2 Released July 21, 2000
No longer supported.
|
Built with: FLEXlm 6.0, VR-Link 3.5 HLA Support: MÄK RTI 1.3.2, DMSO RTI 1.3v4, 1.3v5, 1.3v6 RPR FOM 0.5, 0.7, 0.8, 1.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
Operating System
|
Windows 95/98/NT 4.0 |
Compiler
|
MS Visual C++ 6.0 |
VR-Forces 1.2-ngc
|
Built with: FLEXlm 6.0, VR-Link 3.5-ngc HLA Support: MÄK RTI 1.3.2-ngc, DMSO RTI NG v1, v2, v3 RPR FOM 0.5, 0.7, 0.8, 1.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
Operating System
|
Windows 95/98/NT 4.0 |
Compiler
|
MS Visual C++ 6.0 |
VR-Forces 1.1 Released January 31, 2000
No longer supported.
|
Built with: FLEXlm 6.0 (for all configurations except Linux which uses FLEXlm 6.1) HLA Support: MÄK RTI 1.3.2, DMSO RTI 1.3v4, 1.3v5, 1.3v6 RPR FOM 0.5, 0.7, 0.8, 1.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
SGI-MIPS |
Operating System
|
Windows 95/98/NT 4.0 |
Red Hat Linux 6.0 (Linux 2.2.5) |
IRIX 6.2 & up n32 NT Visual Workstation (NT 4.0) |
Compiler
|
MS Visual C++ 6.0 |
gcc version egcs-1.1.2 |
MipsPro 7.1 C++, MS Visual C++ 6.0 |
VR-Forces 1.1-ngc
|
Built with: FLEXlm 6.0 (for all configurations except Linux which uses FLEXlm 6.1) HLA Support: MÄK RTI 1.3.2-ngc, DMSO RTI NG RPR FOM 0.5, 0.7, 0.8, 1.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
SGI-MIPS |
Operating System
|
Windows 95/98/NT 4.0 |
Red Hat Linux 6.0 (Linux 2.2.5) |
IRIX 6.5, n32 NT Visual Workstation (NT 4.0) |
Compiler
|
MS Visual C++ 6.0 |
gcc version egcs-1.1.2 |
MipsPro 7.2.1 C++, MS Visual C++ 6.0 |
VR-Forces 1.0 Released November 18, 1999
No longer supported.
|
Built with: FLEXlm 6.0 (for all configurations except Linux which uses FLEXlm 6.1) HLA Support: MÄK RTI 1.3.2-ngc, DMSO RTI NG RPR FOM 0.5, 0.7, 0.8, 1.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
SGI-MIPS |
Operating System
|
Windows 95/98/NT 4.0 |
Red Hat Linux 6.0 (Linux 2.2.5) |
IRIX 6.5, n32 NT Visual Workstation (NT 4.0) |
Compiler
|
MS Visual C++ 6.0 |
gcc version egcs-1.1.2 |
MipsPro 7.2.1 C++, MS Visual C++ 6.0 |
VR-Forces GUI Versions
VR‑Forces 3D Front End Versions
VR-Forces 3D Front End 2.0.0.1 for VR-Forces 3.12 Released August 20, 2009
VR-Forces 3D Front End 2.0 for VR-Forces 3.12 Released July 23, 2009
|
Built with: VR-Forces 3.12, VR-Link 3.13.2, Qt 4.5.0 HLA Support: MÄK RTI 3.3.2 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
|
Operating System
|
Windows XP/Vista (VC++ 8.0 only) |
|
Compiler
|
MS Visual C++ 7.1 and 8.0 |
|
VR-Forces 3D Front End 1.0.1 for VR-Forces 3.11 and 3.11.0.1 Released November 14, 2008 VR-Forces 3D Front End 1.0 for VR-Forces 3.11 Released March 24, 2008 Maintenance support expires July 23, 2010
|
Built with: VR-Forces 3.11, Vega Prime 2.2, VR-Link 3.11.1, Qt 4.3.3 HLA Support: MÄK RTI 3.2 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
Operating System
|
Windows XP/Vista (VC++ 8.0 only) |
Red Hat Enterprise Linux WS 4 |
Compiler
|
MS Visual C++ 7.1 and 8.0 |
default compiler |
B-Have Versions
B-HAVE Module for VR-Forces Versions
B-HAVE Module 4.1.1 for VR-Forces 4.1.1 Released April 10, 2013
|
Built with: FLEXlm 11.8, VR-Link 4.0.5, VR-Forces 4.1.1, Qt 4.7.4 HLA Support: MÄK RTI 4.1.1 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
Operating System
|
Windows XP (32 bit only)/Vista/Windows 7
|
Red Hat Enterprise Linux 5 |
Compiler
|
MS Visual C++ 8.0 MS Visual C++ 10.0 32 bit and 64 bit |
Default compiler (32 bit) |
B-HAVE Module 4.1 for VR-Forces 4.1 Released January 31, 2013
|
Built with: FLEXlm 11.8, VR-Link 4.0.5, VR-Forces 4.1, Qt 4.7.4 HLA Support: MÄK RTI 4.1.1 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
Operating System
|
Windows XP (32 bit only)/Vista/Windows 7
|
Red Hat Enterprise Linux 5 |
Compiler
|
MS Visual C++ 8.0 MS Visual C++ 10.0 64 bit |
Default compiler (32 bit) |
B-HAVE Module 2.0.4 for VR-Forces 4.0.4 Released July 2, 2012
|
Built with: FLEXlm 11.8, VR-Link 4.0.5, VR-Forces 4.0.4, Qt 4.7.4 HLA Support: MÄK RTI 4.0.4 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
Operating System
|
Windows XP(32 bit only)/Vista/Windows 7
|
Red Hat Enterprise Linux 5 |
Compiler
|
MS Visual C++ 8.0 MS Visual C++ 9.0 32 bit and 64 bit MS Visual C++ 10.0 64 bit |
Default compiler (32 bit) |
B-HAVE Module 2.0.3 for VR-Forces 4.0.3 Released February 9, 2012
|
Built with: FLEXlm 11.8, VR-Link 4.0.3, VR-Forces 4.0.3, Qt 4.7.4 HLA Support: MÄK RTI 4.0.4 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
Operating System
|
Windows XP(32 bit only)/Vista/Windows 7
|
Red Hat Enterprise Linux 5 |
Compiler
|
MS Visual C++ 8.0 MS Visual C++ 9.0 32 bit and 64 bit MS Visual C++ 10.0 64 bit |
Default compiler (32 bit) |
B-HAVE Module 2.0.2 for VR-Forces 4.0.2 Released December 12, 2011 B-HAVE Module 2.0 for VR-Forces 4.0.1 Released September 1, 2011
|
Built with: FLEXlm 11.8, VR-Link 3.13.2, VR-Forces version indicated in release title, Qt 4.6.3 HLA Support: MÄK RTI 4.0.4 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
Operating System
|
Windows XP/Vista/Windows 7
|
Red Hat Enterprise Linux 5 (B-HAVE 2.0.2 only) |
Compiler
|
MS Visual C++ 8.0 MS Visual C++ 9.0 32 bit and 64 bit |
Default compiler (32 bit) |
B-HAVE Module 1.5 for VR-Forces 4.0 Released February 3, 2011
|
Built with: FLEXlm 11.6, VR-Link 3.13.2, VR-Forces 4.0, Qt 4.6.3 HLA Support: MÄK RTI 4.0.2 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
Operating System
|
Windows XP/Vista/Windows 7 |
Compiler
|
MS Visual C++ 8.0 |
B-HAVE Module 1.4 for VR-Forces 3.12 and 3.12.0.1 Released July 23, 2009
Maintenance support expires August 3, 2012
|
Built with: FLEXlm 11.6, VR-Link 3.13.2, VR-Forces 3.12, Qt 4.5.0 HLA Support: MÄK RTI 3.3.2 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
Operating System
|
Windows XP/Vista (8.0 and 9.0) |
Red Hat Enterprise Linux WS 4, Red Hat Enterprise Linux WS 5,
|
Compiler
|
MS Visual C++ 7.1, 8.0 and 9.0 |
default compiler |
B-HAVE Module for VR-Forces 1.3 Released April 8, 2009
Maintenance support expires July 23, 2010
|
Built with: FLEXlm 11.4, VR-Link 3.11.1, VR-Forces 3.11, Qt 4.3.3 HLA Support: MÄK RTI 3.2 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
Operating System
|
Windows XP/Vista (8.0 only) |
Red Hat Enterprise Linux WS 4, Red Hat Enterprise Linux WS 5, Fedora 7 |
Compiler
|
MS Visual C++ 7.1, 8.0 |
default compiler |
B-HAVE Module for VR-Forces 1.2 Released March 24, 2008
Maintenance support expires April 8, 2010
|
Built with: FLEXlm 11.4, VR-Link 3.11.1, VR-Forces 3.11, Qt 4.3.3 HLA Support: MÄK RTI 3.2 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
PC |
Operating System
|
Windows XP/Vista (8.0 only) |
Red Hat Enterprise Linux WS 4, Red Hat Enterprise Linux WS 5, Fedora 7 |
Compiler
|
MS Visual C++ 7.1, 8.0 |
default compiler |
B-HAVE Module for VR-Forces 1.1.1 Released September 21, 2007 B-HAVE Module for VR-Forces 1.1 Released July 25, 2007
Maintenance support expires March 24, 2009
|
Built with: FLEXlm 10.8, VR-Link 3.10.1, VR-Forces 3.10.1, Qt 3.3.5 HLA Support: MÄK RTI 3.1 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
Operating System
|
Windows 2000/XP/Vista (8.0 only) |
Compiler
|
MS Visual C++ 7.1, 8.0 |
B-HAVE Module for VR-Forces 1.0.1 Released April 4, 2007 B-HAVE Module for VR-Forces 1.0 Released February 19, 2007 Maintenance support expires July 25, 2008
|
Built with: FLEXlm 10.8, VR-Link 3.10.1, VR-Forces 3.10, Qt 3.3.5 HLA Support: MÄK RTI 3.1 RPR FOM 1.0, 2.0 (Other FOMs via FOM mapper) DIS Support: Versions 4, 5, 6
|
Hardware
|
PC |
Operating System
|
Windows 2000/XP |
Compiler
|
MS Visual C++ 7.1, 8.0 |
VR-Forces Migration Support
Migration Support
VR-Forces Migration Support Policy
This migration information provides a high-level review of changes to the major classes in the GUI API. However, it is not a comprehensive guide to changes. MÄK has decided not to release a comprehensive porting guide because we believe the upgrade experience is likely to be highly specific to individual customer use cases. As such, a comprehensive porting guide would be unlikely to fully explain the process no matter how much we wrote. Instead, MÄK has pledged to work with customers on a one-on-one basis during their upgrade process. That will include help through technical support, customer specific webinars and possibly on-site support and training. Please contact us a
This e-mail address is being protected from spambots. You need JavaScript enabled to view it
or through your MÄK salesperson or reseller for help with porting to VR-Forces 4.0.
Migrating from VR-Forces 3.x to 4.x
Before migrating from VR-Forces 3.12 to 4.x, you should understand the major areas that have changed:
- The front-end was completely redesigned. In VR-Forces 3.12, the 2D and 3D interfaces were separate executables. VR-Forces 4.x has a completely integrated 2D/3D graphical user interface (GUI) based on the VR-Vantage toolkit. As a consequence, the GUI API has changed dramatically.
- The Simulation API and Remote Control API have incremental improvements to support new features, but are largely similar to previous releases.
- The Terrain API has been updated to support the terrain agility features used in VR-Vantage and to support synchronization of the front-end and back-end views of the terrain.
Click the subheading for migration details.
VR-Forces Migration Support Policy
This migration guide provides a high-level review of changes to the major classes in the GUI API. However, it is not a comprehensive guide to changes. MÄK has decided not to release a comprehensive porting guide because we believe the upgrade experience is likely to be highly specific to individual customer use cases. As such, a comprehensive porting guide would be unlikely to fully explain the process no matter how much we wrote. Instead, MÄK has pledged to work with customers on a one-on-one basis during their upgrade process. That will include help through technical support, customer specific webinars and possibly on-site support and training. Please contact us a
This e-mail address is being protected from spambots. You need JavaScript enabled to view it
or through your MÄK salesperson or reseller for help with porting to VR-Forces 4.0.
Resources
Videos
|
This video takes you quickly through the creation and running of a helicopter scenario in VR-Forces. The Scenario takes place in a terrain database served from the cloud using VR-TheWorld Server.
|
|
See how paged feature data works in VR-Forces 4.1. This applies to feature data from VR-TheWorld Server and also to local feature data.
|
 |
Learn how to quickly create realistic background traffic by using Pattern of Life with B-HAVE for VR-Forces.!
|
 |
Watch this video to see VR-Forces with B-HAVE demonstrate Pattern of Life. You will see multiple entities being created and set to paths, mimicking the environment of a real road with bursts of activity dependent on a schedule, as the work day begins and ends.
|
 |
This video demonstrates VR-Forces with B-HAVE; watch as Pattern of Life allows multiple entities to be created and set to paths, mimicking the environment of a real subway station with bursts of activity dependent on a schedule.
|
|
VR-Forces, MÄK's Computer Generated Forces solution, is terrain agile. That means that you match the style of the terrain you use to your specific simulation requirements. This video shows how easy it is to load and simulate on four different types of terrain, including Open Standards Streaming Terrain.
|
|
This video shows the creation of a "sector search" using scriptable tasks with the Lua programming language. The scenario was created with the most recent version of VR-Forces (4.1).
|
|
Force Projection is a demonstration of a global scenario using VR-Forces and VR-Vantage. It combines spot reporting, communication models, weapons models with humans, ground vehicles, ships and cruise missiles to orchestrate force projection half way across the planet.
|
|
Demonstration of a homeland security training exercise using MAK products.
|
|
VR-Forces has a great new Graphical User Interface. It combines the best of 2D Tactical displays with 3D Stealth views and exaggerated reality views to give you the best scenario creation and simulation experience. This video shows these capabilities in the context of an Instructor Operator Station (IOS).
|
|
VR-Forces, MÄK's Computer Generated Forces solution, is terrain agile. That means that you match the style of the terrain you use to your specific simulation requirements. This video shows how easy it is to load and simulate on four different types of terrain, including Open Standards Streaming Terrain.
|
Brochure

User Guide
VR-Forces 4.1.1
VR-Forces 4.1
VR-Forces 4.0.4
Bonus Materials
Marine Missile Defense Plug-in for VR-Forces 3.12
|
Marine Missile Defense is a small plug-in for VR-Forces 3.12, which adds an anti-missile missile system useful for ships. Additionally, this module adds an enhanced damage actuator that calculates cumulative damage from multiple hits, useful for any large entity types.
The package includes pre-compiled binaries for Windows VC++8, full source code, a new simulation model set, and a demonstration scenario. More detailed documentation is included with the package.
|
|
Webinar Recordings
Join Jim Kogler, Director of COTS Products, as he enumerates the many new aspects of VR-Forces 4.1. Available in January 2013, VR-Forces 4.1 will focus on better scenarios and increased usability; features will include scriptable tasks using LUA, large and streaming feature data sets, bombs, mortars, ballistic munitions model, force independent entity creation, increased entity types, MSDL laydown and support, and enhancements to 3.12 features including tactical graphics and tactical smoke and hazard cloud displays.
You know VR-Forces is flexible. You know VR-Forces is powerful. But do you know how to get the most from MÄK’s simulation toolkit? Bob Holcomb, MÄK Solution Engineer, will do what he does best - offer solutions to popular customer questions. He’ll also offer tips and tricks that can help you maximize the power behind VR-Forces.
Information is the key to winning the battle. The competitive advantage of a well-informed war fighter is the goal of network-centric warfare (NCW). This doctrine impacts everyone in the M&S and C4I worlds, whether you are working on R&D, systems engineering, or C4ISR. For a realistic battlefield simulation, you need to model communications. MÄK and Scalable Network Technologies are bringing NCW to simulation with inter-entity communications, radio and communications network infrastructure modeling, and real world communication effects, like time delays and network constraints. At this webinar Dan Brockway, MÄK's Director of Technical Marketing, will show you how to create a rich synthetic battlefield environment using VR-Forces, MÄK’s simulation toolkit. He’ll detail how to create a simulated world where sensor models perceive the events taking place, entities use radios to send spot reports, and the receiving entities change their behavior in response to the communication.
FAQs
VR-Forces provides, flexible, on-demand simulation for use as a tactical leadership trainer, threat generator, behavior model testbed, Computer Generated Forces (CGF) application, and more. This FAQ provides an in-depth overview of the product functionality and architecture.
Lua is a scripted and lightweight programming language. It is widely used in the video game industry as the preferred way to extend game engines. Its popularity stems from its light-weight fast nature and its ability to bind to C++ toolkits, such as VR-Forces.
B-HAVE (Brains for Human Activities in Virtual Environments) is a plug-in for VR-Forces. Powered by Autodesk Kynapse, B-HAVE uses advanced Artificial Intelligence (AI) technology to provide more complex and realistic behaviors and background traffic within MÄK’s VR-Forces simulation environment. Using B-HAVE, VR-Forces entities can analyze terrain topology, intelligently navigate through complex urban environments, automatically plan and follow paths through 3D building interiors, dynamically avoid collisions with obstacles or other entities, and flee from threats. B-HAVE allows VR-Forces users to create complex Pattern of Life (POL) modeling, where streams of people and vehicles follow context-sensitive patterns. These patterns add realistic background traffic, giving depth to simulations.
While many of us may look out our car window on the way to work at a crowded city street and see randomness, there is really quite a bit of order beneath the surface. It turns out people – by their very nature – are quite predictable. We take the same car at the same time, on the same road, to work everyday. Most people go to work in the morning and return in the evenings; vendors open shops, buses follow schedules, and kids go to school all in a pattern. We wear winter coats when it’s cold outside, and we wear shorts when it’s hot. No one is a robot and many individuals have some degree of variation intheir daily routines, but when taken in aggregate, we pretty much do the same thing at the same times every day. Most of us pay no attention to the pattern in the car on the road to work ‐ it all looks like noise.
Successes
|
|
 |
"The MÄK tools are easy to use and networkable, allowing us to seamlessly connect other HLA-compatible systems to provide a valuable learning experience for aircraft personnel."
|
|
|
 |
“Only a COTS solution like the one offered by MÄK could meet the budget constraints of our project. It was the perfect all-in-one solution at the right price.”
|
|
|
 |
"We chose MÄK products because of their knowledge and experience with HLA. For scenario generation, we chose their COTS product VR-Forces®. VR-Forces is flexible and can easily accommodate special requirements. MÄK seems to be serious about making their software highly customizable. We saved a lot of development hours using VR-Forces instead of making our own proprietary scenario generator."
|
|
|
 |
“We chose MÄK because of the high-quality performance, functionality, and stability of their products.”
|
|
|
 |
"MÄK’s products saved us the time of building our own custom applications without sacrificing any of our simulation requirements. It would have taken anywhere from six months to a year to develop the capability we wanted on our own. MÄK’s off the shelf products have provided a well-developed solution that still allows us the flexibility to customize it as we see fit."
|
|
|
 |
"We were looking for the best bang for our buck. That and our short time scale necessitated looking at available COTS products to use as a framework for ADGESIM. Our research led us to choose VR-Forces and VR-Link."
|
|
|
 |
"We like MÄK because we are able to put faces with products. We get great support. It’s the developers who answer our questions. We know the folks who write the code."
|
|
|
|
"We set an aggressive schedule for development and we’ve met all the milestones. VR-Forces provided us with a jump start in development which helped us meet our goals without sacrificing vital features."
|
|
|
 |
"Our tools gave the SMARTeam the ability to quickly create a simulation, from scenario development through data collection."
|
|