updated 061204
Latest News
- At the time of this writing, the latest version of VASSAL is 2.8; this will
continue to evolve. However VSQL is fixed to version 1.9.9 which makes it
immune for conflicts arising with VASSAL interactions driven by requirements
of other game systems (launched via VSQL.bat)
- The latest version of VSQL is 3.1 which has the inherent version of VASSAL.
Hence run the program by either executing the vsql.bat file (Windows OS) or
the 'runvassal.jar' (other systems) which will launch VSQL within the VASSAL
1.9.9 module. The VASSAL.bat in the the VSQL files will launch VASSAL 1.9.9.
- VSQL version 3.1 has inherent new die roller code based on the mersene twister
algorithm which is identified by the yellow background.
- NOTE: Version 1.9.9 of VASSAL under which VSQL operates has several inherent
foibles. These include a non-functional Internet Die Roller and a 'memory
leak'. The latter will occur over usage time especially when you system has
many applications open.
- Additionally, on a Wintel platform, a recommended minimum RAM is 256 MB.
If your platform is sluggish, turn off the Verbose LOS in the File/Preference
settings to ease the RAM load.
- VSQL version 4.0 remains under playtest. This version runs under the current
VASSAL engine (2.8 as of this writing). Benefits are certain improvements
over VSQL3.x, new capabilities now inherent in the VASSAL, in addition to
resolving the memory leak & internet die roller issues. VSQL3 introduced
several new VASSAL capabilities requiring custom coding. On going development
of VSQL is limited as this custom code is not inherent in the latter version
of VASASL. Game files and scenario files for earlier versions will need to
be regenerated as previous counters placed with not have the VSQL4 configuration.
- The extension CodGiaV3B##.mdx is posted and expands VSQL3 for COD and GIA
play with limited availability of the host of COD and GIA vehicle/gun counters.
Placement of this extension into the appropriately named Extension folder
will load this capability when the VSQL module is launched. Due to configuration
differences in VSQL3.x and VSQL4, this extension is specific to VSQL3.x. Future
effort in this error will be put into the corresponding VSQL4 version.
- The extension PLC.mdx is posted and makes named Personal Leader Counters
available for Squad Leader Academy events which possess a parallel PLC contest.
- DO NOT OPEN VSQL USING THE LATEST VASSAL AS THIS WILL PREVENT YOUR GAME
FILE FROM BEING BACKWARD COMPATABLE.
Description
- VSQL, Virtual Squad Leader, is the SQUAD LEADER module for the VASSAL
game engine and is the standard interface for all Squad Leader Series
remote play. VSQL enables both real time internet play and stepped review
turns for PBEM play. Programmed in Sun Java, all files are computer platform
independent.
- VSQL
module 3.1 fully enables all SQUAD LEADER and CROSS OF IRON play.
VSQL screen image for
SQUAD LEADER
VSQL screen image for
CROSS OF IRON
Game File Capability:
- VSQL 3.1 has custom modifications to capture any key VASSAL features (movement
trails) not inherent to VASSAL 1.9.9 via custom code modification. Game files
generated via VSQL 2.5.8, will possess counters lacking the lasted traits.
To convert a VSQL 2.5.8 to 3.0 comparability, all counters should be deleted
and replaced from the counter menu. VSQL files capable for VSQL 3.0, will
have a '.v3scen' file extension.
- Files generated with the short lived VSQL 2.5.7 module, will only display
counters using this version. Conversion to VSQL 3.0 is highly recommended.
Version 2.5.7 is not readily available by the player pool (it is archived
below) hence games on the server will not be viewable by others.
- Files generated via VSQL 2.5.6, will be functional although the counters
will lack the latest counter traits.
- Files generated via module versions previous to 2.5.6 are not compatible
with later version.
- VSQL module 2.5.1 was compatible only through VASSAL 1,2,3. Due to changed
in counter names:; game and scenario setup files made with that or earlier
VSQL versions to 2.5.1 are not compatible with later VASSAL versions. Beginning
with VSQL 2.5.3, VASSAL versions of 1.3.2 must be used. All files are upwards
compatible from that point forward. However it is recommended to use the latest
versions of both VASSAL and VSQL for all new game starts. VASSAL is automatically
updated from the server, however VSQL must be loaded manually to effect an
update. The boards and scenario start files have been regenerated with the
latter VSQL so they remain forward compatible
Player Guides:
- For VASSAL veterans, use of VASSAL is now self evident. The inherent documentation
is written by the same folks who wrote the VASSAL code. It is of only relative
value to new players without extensive computer use background, which results
in frustration. Scott Bramley, one of the new VSQL players has drafted a VSQL
NOVICE VSQL USERS GUIDE that will undergo frequent enhancements
as weaknesses are identified by other new players.
- Similar, the Wargame Academy VASSAL team (Easton, Wise, Thomson) is rolling
out a series of VASSAL module cloned from the 'state of the art' template
(The Russian Campaign 3rd edition; 8/2005). This effort includes a VASSAL
NOVICE USERS GUIDE which similarly will be enhanced as needed.
Current Issues:
- A minimum of 64MB RAM is needed on PCs but requires Verbose LOS be turned
off. PC ram of 128+ is recommended, the more the merrier.
- VASSAL is not comparable with Macintosh OS9. Earlier now obsolete versions
did run on Mac OS 8+.
- As Macintosh OSX has its own version of java as part of the operation system
and may differ in performance for the current version of java for the PC,
Unix, and/or Linux platforms. The VASSAL programmers have no control of Macintosh
Java Resource (MRJ) or the Java Resource Environment (JRE) or other iterations
of Java. Macintosh issue of the past included reversed boards were corrupted
and board transformations resulted in undesired graphical changes (i.e. a
transformed hill changed the board to solid woods).. Most of these issues
have disappeared as the Macintosh java evolved. A ongoing issue is the selection
and movement of counters remains more 'choppy' on a Mac, and it appears counters
are being dropped at some hi eight above the board, hoping to land on the
desired location. This is hard to describe the VASSAL programmers who all
seem to use PC platforms. No resolution is anticipated through the VASSAL
team.
Other Key VSQL Assets
- Board Archive, shared with VASL These boards
are version 4.2+ which are needed for the LOS capability to function properly.
Earlier boards which were used in the VASL 3.02 application will display but
lack LOS capability which is an inherent feature in VSQL. Unzip the folder
only- DO NOT UNZIP the individual board files as VSQL uses them in the zipped
format. File size=15.7MB. Note VASL refers to Virtual Advanced Squad Leader.
- Scenario setup files archive (as
of 11/25/06; File size=0.5 MB). These standardized files display all units,
victory hex locations, startup areas, NORTH indicator will the full scenario
card posted in the INFO control window tab. Contributions for additional scenarios
are welcome if all the content is included. Individual Send setup files are
posted on Squad Leader Academy.
Independent setup files also can be found on Advancephase.com.
Jay Yanek also has a similar database. Multiple databases server to provide
redundant remote backup and independent of a server availability.
- VSQL Version history; tracing back
to version 1.0.
- Frequently Asked Questions; last updated 030826,
version 2.5.1.
- VSQL credits.
- VSQL Developmental history.
This was a length effort involving many individuals. The end product is the
benchmark for all VASSAL modules and will influence future version of VASL
as well.
VSQL SQLA Archive
VASSAL ENGINE SITE
