ArmA II and its effect on the future of VBS

Many people out there using VBS2 at this point would be largely aware of one key fact, behind the simulation is a game franchise. A franchise which is looking to take another step with a new iteration. The one the community is calling "the real sequel" to Operation Flashpoint. Armed Assault 2. To get an idea of what's on the way, there's this short summary of features from 505games.

SINGLE PLAYER MODE with emphasis on resource management and RPG elements, the player commands a squad through a story full of twists and surprises
Cooperative MULTIPLAYER and team-based large scale multiplayer over entire map for 50 live players
Built-in MISSION EDITOR allowing player to expand the game beyond original content
Complex weapons SIMULATION based on technologies used in military training and real-world data: ballistics, deflection, material penetration, glowing tracer rounds
AUTONOMOUS AI providing them ability to react dynamically depending on player's action: AI-controlled soldiers and vehicles maneuver, flank, take cover and surprise player in many ways.
AI where squads navigate in REALISTIC FASHION, soldiers can find proper cover with millimeter precision, lean from cover and return fire.
Advanced dynamic CONVERSATION system, integrating preset conversations and dynamic queries about the game environment.
GESTURES and combat communication of units: Soldiers shout and use same communication means as in real combat situations
Comprehensive library of over 60 fully simulated modern FIREARMS
Over 60 playable VEHICLES

Does this mean we can expect a new engine backing the VBS product line very soon? not necessarily. Unfortunately the major limiting factor here is the PC specifications most of the large customers are using. They're either out of date or likely to come up short, they may be able to run standard ArmA II for the most part, however one must consider the scope of VBS2, the addition of addons, numbering approximately 1000. The size of the average VBS2 terrain is also in some cases double the size of Sahrani. And the final factor in play is the expected number of participants in a scenario.

The issue here is we can't expect the current fleet of PCs to carry the weight of ArmA II, with VBS2 content, given the above additions and other planned features. The massive push with customer funded content is fast approaching its limit of exploitation on the current PC spec as it is, with each new minor version and even build we're seeing exponential leaps in capability. The changelog for 1.22 printed straight from notepad was 9 pages, and this was for a point version hop of 1. The next expected release of VBS2 which is scheduled for May/June is 1.3 (Although some elements of the US Army have 1.23).

In addition to the BIA created content, content creators who happen to be external like myself and possibly the major audience of this blog are likely to receive more as well in the tools. The 1.22 tools which we're still waiting on appear to be coming with an Enterprise licensed copy of GlobalMapper, and the long awaited FSM editor. And why are the tools being expanded? quite possibly because the applications of VBS2 are that far ranging, the demands of the end user so great and the control of information so tight, that it takes someone internal to the organisation to develop some things. Although this is a double edged sword as developing internally can edge the organisation closer to its own limit of exploitation with regards to the PC spec.

However with an intelligent approach this should not stop any organisation from taking up the challenge, particularly if the end-user requests a small feature, perhaps alteration to a terrain, creation of a basic model, scripted functionality, etc. Thanks to the tools such things are possible, particularly if the staff are aware of how the system works, or able to access someone who is. The ArmA community being a perfect example, where individuals in their own spare time armed with similar tools and a knowledge of the system have gone out on a mission to alter the functionality inline with their own objective.

Will the same expansion be seen in VBS2? well it's already underway, there is a massive desire among the user organisations to carry out their own improvement tasks, refining the utility of the simulation to match the local user requirements. Everything from controlled IED lanes through to massive combat team scenarios. Regardless of the uses, one thing is quite clear through all this, and that is with the current package and the current engine, VBS2 isn't likely to be going anywhere. As every day passes, every success in VBS2 is only another reason to persist with it and refine it, tirelessly pursuing perfection.