USER GUIDE

Troubleshooting

500

VBS3Fires v3.6.3 User Guide

should close down the other application which is conflicting with VBS3Fires and run

VBS3Fires again.

5. If you have IPv6 installed on your system, ensure that IPv4 is also installed and that you are

running VBS3Fires with the -Djava.net.preferIPv4Stack=true before the -jar flag in the

command line.

28.1.1.4 I get a disconnection message

VBS3Fires will display a disconnection message whenever it loses a connection to VBS3. This could

be because:

a. VBS3 has closed down.

b. The network connection between VBS3 and VBS3Fires has been broken

c. A timeout has occurred due to VBS3 excessive processing. If this occurs repeatedly, please

contact the VBS3 support department.

28.1.1.5 I get unexpected behavior when I try and run two Stand-Alone VB2Fires

systems or two Instructor VBS3Fires systems in the same VBS3 scenario.

Currently, VBS3Fires does not support having multiple Stand-Alone VBS3Fires systems running in the

same scenario. The scenario will start; however, any attempt to control the same Batteries from

the two systems will result in unexpected behaviour. Similarly, VBS3Fires does not currently support

multiple VBS3Fires instances running in Instructor mode connected to the same scenario.

28.1.1.6 “SEVERE: Cannot load map UTM origin coordinate. Aborting initialization.”

In the case when the VBS3Fires timers are not running in the Simulation Status panel and the

VBS3Fires scenario has already started, and when you access the VBS3Fires log (Menubar  Help 

View Log), the above message is displayed. The reason is that the FO unit’s location is invalid. To

further confirm that the terrain that the scenario was created has origin issues, type “getOrigin” in

the Developer Console of VBS3 and it will return [-1,-1,-1,"N"].

28.1.1.7 Connecting VBS3Fires to a VBS3 scenario in progress

If for any reason, VBS3 and VBS3Fires loose connectivity during a simulation scenario, it is possible to

force VBS3 to connect to VBS3Fires during the scenario.