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
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:
Click the subheading for migration details.
- 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.