Get it at https://vasl.info/download.htm.
VASL6.6.7 now available
- Thread starter DougRim
- Start date
- Joined
- Feb 4, 2003
- Messages
- 4,996
- Reaction score
- 4,792
- Location
- La Belle Province
- First name
- Michael
- Country
-
For the people who might miss reading this: it requires VASSAL 3.7.5
PresterJohn
Elder Member
And manually unzip and move the .vmod file to your VASSAL modules directory.
Then double click to add it to VASSAL.
Then double click to add it to VASSAL.
The VASSAL version will not load for me. This is a first. I always get the, "this is not a Google Play app" warning, but can just dance around it. This time, I get the VASSAL icon to download, but when I try to run it, nothing happens. I have the latest JAVA downloaded, but the VASSAL refuses to open up, which is an issue I have never had. No new security added to the system either.
PresterJohn
Elder Member
Are you downloading from https://forum.vassalengine.org/t/vassal-3-7-5-released/78165 and selecting the correct file for your hardware and OS. What type of PC are you using?
A Dell PC. As I say, this is the exact same download I always get for this PC. Nothing has changed. This problem on the other hand, IS a first. Tried the link you provided. Exact same one as I used, exact same result, which is to say, failure. Downloading the 64 bitX86 option.
PresterJohn
Elder Member
Sorry, I'm completely thrown by the "this is not a Google Play app" warning.
You do not need Java installed for the Windows or Mac versions of Vassal. They come bundled with their own Java. They will not use the Java you have installed. Vassal has been this way since 3.3.0 in 2020.
Please tell us:
- the URL of the file you're downloading
- the name and size (in bytes) of the file you download
- the hash of the file you downloaded (you can compute that here)
- the full path to which you've downloaded the file
- how exactly you are trying to run the file
EDIT: Carl, the following may not apply to your circumstance as you seem able to download but cannot get the download to run. I am hearing from others having problem actually getting VASSAL to download and the following may be of use to them.
In my experience this a Win11/Chrome thing. I never had an issue until a got a new computer with Win11 last month. I get the problem most times I download a VASSAL version, sometimes with VASL, and randomly with other stuff.
What I do is this: click on the download symbol in my browser bar, which gives me a pop up with a list of recent downloads. Some will show blocked and will have a button named Delete. I click the dropdown arrow on that button and get an option to continue download. Selecting that allows the download to work.
Of course your results may vary but this is working for me.
In my experience this a Win11/Chrome thing. I never had an issue until a got a new computer with Win11 last month. I get the problem most times I download a VASSAL version, sometimes with VASL, and randomly with other stuff.
What I do is this: click on the download symbol in my browser bar, which gives me a pop up with a list of recent downloads. Some will show blocked and will have a button named Delete. I click the dropdown arrow on that button and get an option to continue download. Selecting that allows the download to work.
Of course your results may vary but this is working for me.
Last edited:
Larry
Elder Member
I get an unsafe warning. I click on more information. That allows me to click on run anyway. Then it installs. Win10, 64 bit.
Yes, this is what used to happen to me on win10 as well. Carl, sometimes the unsafe warning window can get hidden behind other windows. Try closing out any other open window before trying to get the VASSAL download to install and get LOS to as much of your desktop as possible. Especially if you are a two-monitor kind of guy - the unsafe warning window may be open on the other monitor, behind another app. Sad to say, that happened to me. Duh!
apbills
Elder Member
I have attempted to use the new convert function and can report the following.
I used a very large campaign game file (over 500 counters of various types) saved under VASSAL 3.6.19/VASL 6.6.6. I also have multiple extensions including one I am making that was updated and built under VASSAL 3.7.5/VASL 6.6.7_AmmoFix (which is the VASL 6.6.7 version with fixes to the dmMTR/GUN counters towork with the VASSAL 3.7.5 fix to the "Replace with Other" text label bug. Doug has indicated that he will incorporate into VASL 6.6.8 once he is done with his WELL DESERVED break after the massive undertaking to create the game converter function).
For the core game counters everything updated, including the new dmMTR counters that now keep the special ammo status between dismantled/assembled counters. The one thing that did not update were any linked acquisition counters. I am not sure if that functionality was part of this first cut of the tool. It was no real problem as we label all our tanks/guns anyway so the acquisition counters had the labels on them and it was easy to relink them.
For the new campaign extension the counters were updated, however, for some of them the correct layer was not updated, just the counter itself. This left all of the control type counters on their initial layer (in most cases this was a German control indicator). I went through them all and corrected them. I did not know what would happen with this anyway since the extension is not even released to Doug, but it was interesting in that the converter clearly updated the vehicle counters with some of their special layers (like an Assault Boat indicator on SPW 251/7 engineer halftracks and a "Driver" indicator on the SPW 251/2 halftracks which had their MTR removed and left them with just a driver). All of these vehicles and the control counters were in the previous version of the extension built under VASSAL 3.6.19/VASL 6.6.6 so it is not clear why one set was converted with the layer information and the other set/type was not.
Again, Doug set my expectations in his release notes and met them with my test. The conversion execution went flawlessly with the steps given. The only issue I found was the linkage one. My extension update was not supposed to be part of the conversion tool anyway, so I was pleased that the tool clearly updated the counters and the issues with the control layers is something for future reference and once I am happy with the final extension version it will go to Doug for his review and posting to the VASL.info site. That will probably help with the conversion bugs as I think he adds some code to those to support conversion.
Well Done my friend, Well Done!
I used a very large campaign game file (over 500 counters of various types) saved under VASSAL 3.6.19/VASL 6.6.6. I also have multiple extensions including one I am making that was updated and built under VASSAL 3.7.5/VASL 6.6.7_AmmoFix (which is the VASL 6.6.7 version with fixes to the dmMTR/GUN counters towork with the VASSAL 3.7.5 fix to the "Replace with Other" text label bug. Doug has indicated that he will incorporate into VASL 6.6.8 once he is done with his WELL DESERVED break after the massive undertaking to create the game converter function).
For the core game counters everything updated, including the new dmMTR counters that now keep the special ammo status between dismantled/assembled counters. The one thing that did not update were any linked acquisition counters. I am not sure if that functionality was part of this first cut of the tool. It was no real problem as we label all our tanks/guns anyway so the acquisition counters had the labels on them and it was easy to relink them.
For the new campaign extension the counters were updated, however, for some of them the correct layer was not updated, just the counter itself. This left all of the control type counters on their initial layer (in most cases this was a German control indicator). I went through them all and corrected them. I did not know what would happen with this anyway since the extension is not even released to Doug, but it was interesting in that the converter clearly updated the vehicle counters with some of their special layers (like an Assault Boat indicator on SPW 251/7 engineer halftracks and a "Driver" indicator on the SPW 251/2 halftracks which had their MTR removed and left them with just a driver). All of these vehicles and the control counters were in the previous version of the extension built under VASSAL 3.6.19/VASL 6.6.6 so it is not clear why one set was converted with the layer information and the other set/type was not.
Again, Doug set my expectations in his release notes and met them with my test. The conversion execution went flawlessly with the steps given. The only issue I found was the linkage one. My extension update was not supposed to be part of the conversion tool anyway, so I was pleased that the tool clearly updated the counters and the issues with the control layers is something for future reference and once I am happy with the final extension version it will go to Doug for his review and posting to the VASL.info site. That will probably help with the conversion bugs as I think he adds some code to those to support conversion.
Well Done my friend, Well Done!
EJ1
Member
Dear Doug,
What a great update. And thanks for including the rowhouse overlay bar! I’m getting choked up.
Cheers,
What a great update. And thanks for including the rowhouse overlay bar! I’m getting choked up.
Cheers,
- Joined
- Jul 26, 2003
- Messages
- 20,128
- Reaction score
- 6,312
- Location
- St-Légier
- First name
- Robin
- Country
-
All works fine for me.
Thank you for the good job !
The "marked units moved" had to be toggled on in the Preferences, but the function works.
Thank you for the good job !
The "marked units moved" had to be toggled on in the Preferences, but the function works.
I got this same popup again, but, had additional steps I could take this time which got me around it. Not sure why they were not there the first time, but 3.7.5 is up and gunning now. I assume there will be no issue with 6.6.7, so I think all is happy and well now. Thanks and sorry for the band width.
PresterJohn
Elder Member
I'm going to go with Doug saying it might be a Chrome thing. I'm a Mozilla heretic at home and just get the usual warnings from Windows (both 10 and 11).
GeorgeBates
Elder Member
Still playing with v6.6.4. Eager to hear to word on the street about this latest.
Quite honestly, this never occurred to me. And is the reason why I am rolling this out in stages - there is always something(s) you don't think about. This kind of testing is how we find them. First addition to the list of improvements!
VASL counters make extensive use of layers so this is another important find. We will need to do some further testing to determine why some updated and not others.
Thanks for this. I appreciate the appreciation!
Pay attention to VASL spaces this fall. Before Christmas I will be announcing and pushing updates to many, many boards to enable a Wooden Building to Huts transformation that will be los enabled. So when using PTO, such terrain will become LOSH rather than obstacles. In the image below, red=clear; cyan=LOSH, blue=blocked.
NOTE: Games using these updated boards will continue to work in 6.6.4 and below however the VASL los function will be disabled. You may wish to update to a version beyond 6.6.4.