New program to help set up VASL scenarios

[Pacman Ghost]

Will that work for chapter H notes?

No, since there's no real way for your friend's VASSAL to talk to your vasl-templates, which is where the Chapter H data lives.

If you've done your Chapter H notes as images, you could put them up online somewhere, then include them in your scenarios using a normal <img src="http://..."> HTML tag, but it's copyrighted material, so it's not something one should be really doing.

If you've done them as HTML, it will work (although that's a big job), but you still have the problem of including images in those notes (typically a picture of the counter, but there are sometimes other images e.g. SPW 251/16).

The only other way to get it to work is to have your friend also run vasl-templates, and have the same Chapter H data.

 

[JohanVrijdaghs]

Hi,

when I start up VASL Templates and I click the 'Search for scenarios' button I get the message which you see on the added picture,
do you know the reason?

Johan.

 

[Pacman Ghost]

when I start up VASL Templates and I click the 'Search for scenarios' button I get the message which you see on the added picture,

This is being caused by the same thing that Doug Leslie reported recently. Run Windows Update, if you're running Chrome, make sure that it's at the latest version - this should fix it.

Scenario search should still work (as long as you haven't just started using vasl-templates), you just won't have the latest data from the ASL Scenario Archive.

 

[Stewart]

Any thoughts of adding a CHAP B for terrain "cards"
This would be VERY useful for those odd terrain features...
I wouldn't include the standards to start...just the odd ones... Slopes, PTO, SSR types like Ground snow etc.
MUD

 

[Pacman Ghost]

Any thoughts of adding a CHAP B for terrain "cards"

You can add this kind of thing via your own "Scenario notes" labels.

 

[Pacman Ghost]

Version v1.8 of vasl-templates has been released here.

The only change since v1.8.beta1 is the addition of support for VASSAL 3.5.8 and VASL 6.6.3.

 

[Paul_RS]

Any thoughts of adding a CHAP B for terrain "cards"
This would be VERY useful for those odd terrain features...
I wouldn't include the standards to start...just the odd ones... Slopes, PTO, SSR types like Ground snow etc.
MUD

Bear in mind that unless you store the images online, you will be the only one who can see them in any template you create.

 

[Neal]

Would it be possible to add an option that allows players to merge multiple log files? It looks like VASL Templates knows how to parse a .vlog and .vsav files.

How hard would it be to have an option to "Merge vlog Files" where a user just drags a set of .vlog files into a window (like you can do to analyze dice stats), order them correctly, then hit a "Merge" button and have it create one .vlog file?

 

[Cpl Wright]

I'm getting this error when I try to analyze multiple log files from a PBEM game I have going. Some older files were created in VASL 6.6.2 and the more recent in 6.6.3. This isn't an issue with other PBEM games. I know the 6.6.2 versions of the log files had an OBA module included with it for some reason, which I later found out when I was encountering issues with upgrading this game to 6.6.3, but I'm not sure if that has anything to do with this issue.

 

[Pacman Ghost]

It looks like VASL Templates knows how to parse a .vlog and .vsav files.

Actually, it doesn't. It runs VASSAL+VASL and that loads the vlog/vsav files.

How hard would it be to have an option to "Merge vlog Files" where a user just drags a set of .vlog files into a window (like you can do to analyze dice stats), order them correctly, then hit a "Merge" button and have it create one .vlog file?

This is a non-trivial task, and getting a bit out-of-scope for vasl-templates. However, someone has already written a program to stitch log files together, but IIRC, abandoned it when VASSAL started obfuscating the save files. But since de-obfuscating them is trivial, it should be easy to get it going again.

 

[Pacman Ghost]

I'm getting this error when I try to analyze multiple log files from a PBEM game I have going.

This error code (almost certainly) means that VASSAL crashed.

Make sure that vasl-templates has a recent version of VASSAL and VASL configured.

Try loading the files one at a time, to see if you can isolate which one is causing the problem, and if it happens every time. If you can do this, PM me the file, and I'll take a look at it.

 

[Pacman Ghost]

I know the 6.6.2 versions of the log files had an OBA module included with it for some reason, which I later found out when I was encountering issues with upgrading this game to 6.6.3

Did you upgrade the log file, as well? If you haven't, and vasl-templates is configured to use VASL 6.6.3, then yes, VASSAL will probably crash. You can configure vasl-templates to use VASL 6.6.2.

 

[Cpl Wright]

Did you upgrade the log file, as well? If you haven't, and vasl-templates is configured to use VASL 6.6.3, then yes, VASSAL will probably crash. You can configure vasl-templates to use VASL 6.6.2.

I have confirmed that the problem is related to VASL 6.6.3, because when I run the analyzer with 6.6.2 referenced in the settings it works just fine. For some reason the file we used to set up our game had an OBA module included with it. Games with OBA modules were identified very early on with the release of 6.6.3 to case issues. This also seems to be the case with running the log file analyzer in VASL Templates. I'll just keep 6.6.2 and run it with that, no biggie!

 

[hongkongwargamer]

I have confirmed that the problem is related to VASL 6.6.3, because when I run the analyzer with 6.6.2 referenced in the settings it works just fine. For some reason the file we used to set up our game had an OBA module included with it. Games with OBA modules were identified very early on with the release of 6.6.3 to case issues. This also seems to be the case with running the log file analyzer in VASL Templates. I'll just keep 6.6.2 and run it with that, no biggie!

This 6.6.4-beta fixes the OBA issue http://www.gamesquad.com/forums/index.php?threads/vasl6-6-3-official-release.164998/post-2073373

 

[Cpl Wright]

In the next update would it be possible to allow changing of colors to RGB values in the log file analyzer?

 

[Pacman Ghost]

In the next update would it be possible to allow changing of colors to RGB values in the log file analyzer?

I'm not sure why someone would need such precise control over the exact colors used, but you can set them directly in C:\Users\YOUR-NAME\vasl-templates.ini.

 

[Cpl Wright]

I'm not sure why someone would need such precise control over the exact colors used, but you can set them directly in C:\Users\YOUR-NAME\vasl-templates.ini.

I would be nice to change them, so you could have the colors correspond to the nationality colors. There is a table posted on the Texas ASL website.
I'm sure you could do it in the .ini file; however, being able to do it "on the fly" in the program would be much simpler, especially for those of us more programming challenged. It's a really great tool, and I think this would be a nice addition. Thanks for considering!

 

[Pacman Ghost]

I would be nice to change them, so you could have the colors correspond to the nationality colors.

That's not a bad suggestion. Leave it with me, I have an idea...

 

[Neal]

I'm not sure why someone would need such precise control over the exact colors used, but you can set them directly in C:\Users\YOUR-NAME\vasl-templates.ini.

I would use the built in RBG functionality as well, as I put dice stats in all our AAR videos and try to match the chart colors to nationality colors.

The .ini has 5 colors listed: lfa.player-colors=#fd4c4c, #7f7931, #ded63c, #c6b949, #5fd760

Which are the colors for the players on the dice stats chart? Thanks!

 

[Pacman Ghost]

Which are the colors for the players on the dice stats chart?

All of them IIRC, the first one is for the "expected result" line, the remainder are for the players. At some point, you've loaded a log file that had 4 players. Have a play with the values, and it should become clear.