VASL6.7.1-beta4 is released

[ibncalb]

I press the Los tool. I immediately forget where I was drawing the Los to/from.

I cancel the Los tool, I start again.

Sound familiar?

Why are my posts bold?

 

[Robin Reeve]

I press the Los tool. I immediately forget where I was drawing the Los to/from.

I cancel the Los tool, I start again.

Sound familiar?

Why are my posts bold?

My too frequent experience.
Your posts are not bold, just slightly daring.

 

[PresterJohn]

I press the Los tool. I immediately forget where I was drawing the Los to/from.

I cancel the Los tool, I start again.

Sound familiar?

This has never happened to me, I'm just supporting it "for a friend".

 

[apbills]

It happens to me all the time, but then I am trying to see an LOS that is 30+ hexes as well. I like the function very very very much.

If it was a counter, I would have already made it. Since it is code, I like when I am pleasantly surprised.

 

[ibncalb]

I just did some testing for the "transparent counters making LOS checks hard" issue.

No problem at all, the counters are very transparent, moreso than normal HIPsters.

 

[Robin Reeve]

I am also enjoying the feature, while recording a new solo playthrough video series (in French).
My failing memory is much less challenged.

 

[Will Fleming]

If the guys have to work to maintain both it could waste some of their valuable time. If it doesn't, then I think an option might be nice.

I am totally happy with whatever they do and appreciate their efforts for the benefit of us all.

 

[ScottRomanowski]

I like the opaque counters during LOS checks!

The "hide counters/overlays" button works fine during LOS stringing to hide the counters. The Ctrl-F10 alternate only works before I place the LOS though. That is, click on the LOS button and Ctrl-F10 works. But as soon as I place the string, Ctrl-F10 stops working. But the button always works.

With this new feature do we need the preference to show hindrance counters during LOS checks (shift-F10)?

 

[PresterJohn]

The LOS string works either way and for both VASL and VASSAL strings.
So far there is nothing not to like.

 

[dlazov]

I think it looks great! No pun intended (much).

 

[skippen]

"It also contains a change LOS functionality. When drawing a LOS string, counters will no longer disappear but will appear opaque; hopefully making it easier to remember and locate the firing and target hexes involved."

Great idea

Finally!

 

[Tony Gibson]

Am I the only person using this version who is having difficulty working out if a vehicle has a slow turret or a restricted slow turret on this version?
The difference in thickness on the counter seems to be marginal (I know I should look up the rule book, but I would like it to be a bit more obvious if I am using several different vehicles in a scenario).

 

[Gordon]

You are the first person to report difficulty. I will look into it further. Thanks.

 

[PresterJohn]

I felt that was always a problem, and had to check the nationality list to be sure.

 

[ScottRomanowski]

I always print the vehicle notes, including table entries, for any scenario I'm playing, so I didn't pay much attention to the new artwork.

 

[ScottRomanowski]

I developed a program to manage and launch different VASSAL configurations: combinations of VASSAL version, module, preferences, and extensions. It also lets you associate a directory with a configuration, so VASSAL launcher (VL for short) will use that configuration when you start a game file from there. It's available as a resource here on GameSquad. It is written in Python, so you need that on your system to use VL.

In relevance to this thread, VL would let you have one configuration that runs VASSAL 3.7.16 with module VASL 6.7.1-beta4 and certain preferences and extensions, another that runs VASSAL 3.7.16 with module VASL 6.6.10 and difference preferences and extensions. You can also have directories associated with configurations, so when you open a game file from games\Fred it uses one configuration, and a different configuration for game files from games\Alice.

A README.txt, instructions, and the source files are in the .zip file.

 

[ScottRomanowski]

Don't just like this; download it, test it, and tell me how to make it better. :-D

 

[PresterJohn]

I developed a program to manage and launch different VASSAL configurations: combinations of VASSAL version, module, preferences, and extensions. It also lets you associate a directory with a configuration, so VASSAL launcher (VL for short) will use that configuration when you start a game file from there. It's available as a resource here on GameSquad. It is written in Python, so you need that on your system to use VL.

In relevance to this thread, VL would let you have one configuration that runs VASSAL 3.7.16 with module VASL 6.7.1-beta4 and certain preferences and extensions, another that runs VASSAL 3.7.16 with module VASL 6.6.10 and difference preferences and extensions. You can also have directories associated with configurations, so when you open a game file from games\Fred it uses one configuration, and a different configuration for game files from games\Alice.

A README.txt, instructions, and the source files are in the .zip file.

Yeah this is definitely what people who routinely use VASL to it's fullest (pbem and live, for scenarios and campaigns, and also SASL) need to keep their sanity. I tried managing this myself for a short time using scripts and gave up. At it's simplest I will have two different setups for last stable with extensions, and current beta.

 

[PresterJohn]

I'm wondering if there is a list of counter issues that include some vehicles being slightly offset. This one is from Lend Lease Russian vehicles and there looks like a related group of Shermans. Minor, but you know how it is.

 

[Gordon]

I don't think so. This is an issue that predates the SVG conversion and I wasn't planning on dealing with it until we get to redoing the actual vehicle graphics.