VASL 6.7.2 officially released

[PresterJohn]

There is a problem with old acquisition counters being moved off the map. They were not counting range correctly on some maps in 6.7.1 and LOS and range calculations have been corrected in 6.7.2, but old Acq counters need to be replaced.

 

[Michael R]

I tried reproducing the error with the same software and data files, but on a different computer. I was not successful.

 

[Michael R]

I saw this post from Doug on Discord.

DougRim67 — 2026-04-14, 10:45 AM
Test results this morning: 1. Veh/Gun + Acq linked (CTRL-ALT-L) in offboard position: bug notification. 2. Veh/Gun+Acq linked in onboard position: no bug. 3. Veh/Gun+Acq linked in onboard position then unit and/or Acq dragged offboard: bug notification. 4. Veh/Gun+Acq linked in game using boards which don't support LOS Checking (HASLs and special TPP boards): no bug. 5. Veh/Gun+Acq linked in game using boards which normally support LOS Checking but for some reason LOS Checking is disabled on the map: bug notification.

My advice: In 672, ONLY use counter linking (CTRL-ALT-L) with units on the boards (NOT in an offboard position). If you get a bug notification, save the game and restart VASSAL and VASL. If you need to remove an acq from the map: (1) delete it; (2) HIP it for later use; (3) unlink it (CTRL-ALT-U) and then drag it off the board. Finally, I will work more on the bug; it is clearly tied to the range display functionality. Should be fixed in an early 673 beta.

 

[ThidalASLSK]

Hi! I've had a problem since the update: some AFV acquisitions cause a bug when moved outside the map (I just realized that others had already pointed out the problem, sorry)... Also, I can no longer see the units transparently when checking a Line of Sight (that was really useful).

 

[PresterJohn]

The transparency was good.

 

[ThidalASLSK]

The transparency was good.

Do I need to activate or modify an option? Because for me, the transparency disappeared as soon as I installed the new version.

 

[PresterJohn]

I noticed that too. I expect it will be reinstated.

 

[Michael R]

I was able to reproduce the error now that I read more about how to trigger it. Just in case it is useful, the error log is attached.

The key part is;

2026-04-16 19:01:45,827 [18779-AWT-EventQueue-0] INFO VASL.build.module.ASLMap -
java.lang.NullPointerException: Cannot invoke "VASL.LOS.Map.Map.resetHexTerrain(double)" because "this.VASLMap" is null
at VASL.build.module.ASLMap.addBoardsToMap(ASLMap.java:502)
at VASL.build.module.ASLMap.buildVASLMap(ASLMap.java:471)
at VASL.build.module.ASLMap.setBoards(ASLMap.java:248)
at VASSAL.build.module.map.BoardPicker.setup(BoardPicker.java:491)
at VASL.build.module.map.ASLBoardPicker.setup(ASLBoardPicker.java:229)
at VASSAL.build.module.GameState.setup(GameState.java:543)
at VASSAL.build.module.GameState$SetupCommand.executeCommand(GameState.java:1249)
at VASSAL.command.Command.execute(Command.java:61)
at VASSAL.command.Command.execute(Command.java:73)
at VASSAL.chat.CommandDecoder.lambda$propertyChange$0(CommandDecoder.java:40)
at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:323)
at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:723)
at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:702)
at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:203)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:124)
at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:113)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:109)
at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:90)
2026-04-16 19:03:45,833 [18779-write game.vassalengine.org/172.237.96.19] WARN VASSAL.tools.logging.LoggedOutputStream - Sent keep-alive

 

[Tony Gibson]

Thanks for the work on the new version.
What version of VASSAL is required for 6.7.2 to work please?

Please ignore me, I've just seen the notes on the upgrade page.

 

[Robin Reeve]

Also, I can no longer see the units transparently when checking a Line of Sight (that was really useful).

I have a partial fix to the problem.

• Opening VASSAL, right click on the VASL module and choose Edit module.
  It opens the module with a window for modifications.
• Then, in the window for modifications, go to the "Main Map [Map Window]" menu and double-click on "LOS" or "los".
  

• There, uncheck "Hide pieces when drawing", near the bottom of the options.
  
  
  
  
  
• Then save the file (ignore the warning message) - there is a minidisk icon next to "File"...

Now, when drawing the LOS thread, the units remain fully visible - not transparent (I don't really care about that difference).

 

[ThidalASLSK]

Merci Robin !

 

[uckelman]

We've seen quite a few bug reports for 6.7.2 in the Vassal tracker. Are you planning to release 6.7.3 soon to correct them?

 

[DougRim]

We've seen quite a few bug reports for 6.7.2 in the Vassal tracker. Are you planning to release 6.7.3 soon to correct them?

There are two bugs being reported, multiple times for each which I know is generating a lot of work for you and I apologize for that.

The first bug deals with use of counter linking (usually a gun/veh and an acq). I have posted about this in GS/FB/Discord with advice about work arounds. I have a fix but can’t release a week or so.

The second bug relates to the use of an outdated extension: Scenario Setup File 670.vmdx. Again I have posted about this on GS/FB/Discord. Users should delete the outdated extension. That is the only way to solve the problem. There is no other fix possible.

Please minimize the work you do on handling these bug reports.

 

[Tycho]

I will check out your error log. Thanks for sending.

I have opened 672 and all of its betas hundreds of times. If a new instance, it tiles the images then proceeds to open. Your problem may be a bug but it certainly wasn't a known one.

Just redid it on my system. Tiled the images and opened!

Taking a quick look at your error log. You seem to have a directory called VASL Stuff which has (1) the 672 .vmod and your \VASSAL3720 folder. Try putting the vmod somewhere else. Just a guess at this stage.

Sorry for the delayed response. I moved the files and no longer get an error. Weird as that's always where I store the vmod files (usually going back a few releases) but I'm just going to quietly walk away and call it good. Thank you!

 

[PresterJohn]

Just noting what was said on the last MMP podcast. The use of VASL makes playable and easy to manage all the scenarios and CG's that are almost impossible on the tabletop because of the issues of managing hidden units and fortifications.

 

[tommyl]

I may be doing something wrong, but for SASL the Suspect counters in version 6.7.1 would flag possible activation for all relevant ranges. The new version 6.7.2 only flags up when a friendly unit is adjacent.
I am using the latest version (V4.1) of the SASL campaign roster.

I'm having the same issue with the Suspect counters only flagging when adjacent. Any ideas for me to try?
So far I have replaced the suspect counters with new ones and also the British (Friendly) counters with new ones.
Using VASL 6.7.2/VASSAL 3.7.21 on a Mac running Sequoia 15..7.5

Thanks

 

[haggis]

I found that

I'm having the same issue with the Suspect counters only flagging when adjacent. Any ideas for me to try?
So far I have replaced the suspect counters with new ones and also the British (Friendly) counters with new ones.
Using VASL 6.7.2/VASSAL 3.7.21 on a Mac running Sequoia 15..7.5

Thanks

My issue was that VASL 6.7.2 was looking to a different extensions path than my set up prior to upgrade.
Therefore, I wasn't actually loading the latest SASL campaign roster 4.1.
Once I had sorted that out, it functioned correctly.

You could try that.

 

[tommyl]

I found that


My issue was that VASL 6.7.2 was looking to a different extensions path than my set up prior to upgrade.
Therefore, I wasn't actually loading the latest SASL campaign roster 4.1.
Once I had sorted that out, it functioned correctly.

You could try that.

Unfortunately, no joy. I deleted the SASL campaign roster and downloaded the a new copy from vasl.info. Restarted VASSAL and VASL and still only activate when adjacent. I've tried all 3 ways listed in the help note and none will activate at other than adjacent.

 

[Gordon]

Unfortunately, no joy. I deleted the SASL campaign roster and downloaded the a new copy from vasl.info. Restarted VASSAL and VASL and still only activate when adjacent. I've tried all 3 ways listed in the help note and none will activate at other than adjacent.

If you can DM a log of the issue I can take a look.

 

[tommyl]

If you can DM a log of the issue I can take a look.

Thanks - Solved it. Helps to read the entire instructions! Had an NVR set on the Scenario Aid Card. Don't remember using this card so didn't think to check it. All works great now, Super helpful to play.