Search results

With the shift of the code to the new repo, please note that announcements and support will be done over there. If you want to ask a question or report a bug, please open a ticket.

The next release of vasl-templates is now available here. Please check the installation instructions, since there are a few considerations that may affect you. If you are running from source, or using Docker, note that the repo has moved from Github, so update your remote: git remote set-url...

Fair enough. It seems to be happening enough that it's worth doing - it'll be in the next release. Having a British PIAT label is fine, but it'd be nice to have the correct flag.

Are there scenarios where the Canadians have PIAT? The work-around is easy - just create an ad-hoc PIAT label and bung it into your scenario - but if there's a case for showing that button for the Canadians (and/or Aussies and/or Kiwis) as well, I can update it.

Are you seeing a honking big red error message when you start the program, saying that there's a problem loading the VASL module because it can't find the build file...?

It's best to not configure Java if you're on Windows, and the program will use the one that comes with VASSAL. A webdriver is optional (although you will probably want one), but it won't affect the loading of VASL.

It's in the British OB.

The third beta in the v1.10 release cycle is now available here. If you are running from source, or in Docker, there is a new branch on Github. IMPORTANT: If you are running the desktop app, the settings file is now stored in different location. While the program will automatically move your...

Thanks for send the files through. This looks like a bug - I think it's happening because you have set up your Chapter H notes, but haven't done the multi-applicable notes for the Landing Craft, and the scenario has a Landing Craft. I've sent you my Landing Craft Chapter H notes, so save those...

I meant the Chapter H data files you set up. It doesn't matter for the moment - right now, I'm thinking something's changed in the data/ sub-directory (in the installation directory). Send me a ZIP of that. But I need the vasl-templates save file (with a .json extension), not the VASSAL .vsav...

You've set up some of the Chapter H multi-applicable notes? Send me a ZIP of your directory and the vasl-templates save file (.JSON extension) you're working on. And what version of vasl-templates are you running (check the About box)?

I haven't ever seen this, or heard about someone having this problem. Open http://localhost:5010 in a browser, open the console tab in Developer Tools, and see if the problem happens there, and if anything gets logged.

The second beta in the v1.10 release cycle is available here. If you are running from source or using Docker, there is a new branch up on Github. The headline feature in this release is something that many of y'all will appreciate: a WYSIWYG editor for the HTML content. You get all the standard...

I always wondered if we could get the Phase Wheel to do this kind of thing automagically. As long as the correct player pulls the SMOKE counter, the Phase Wheel knows when it should be flipped, and then removed ...? Likewise for Prep/Defensive Fire counters, Pin/TI, etc., which would be easier...

I suggested in another post that you figure out where the hex edges are first e.g. in the diagram below, if you figure out which pixels contain a hash, then everything else must be an interior pixel: .... #......#......# ......######........# .....#......#......#...

It doesn't really matter what the terrain is. The key point is that there are some hex edges that block LOS, so if you can quickly identify hex pairs whose LOS crosses these hex edges, you don't need to check them. I reckon VASL might have this information somewhere, since it's able to do...

If you haven't read it already, check out the article "The Geometry Of ASL" (Banzai! 5.2), or search for the mathematical term "similar triangles". The angle of two LOS's must be the same if they are to align, and that will only happen if the triangles are similar. The idea is that you're...

And here's another optimization that could give big savings, depending on what's on the board. Build an index such that for any hex on the board, you can quickly get a list of every hex pair whose LOS goes through that hex. It will take some time to build, but since it's independent of the...

It's usually better to try improve the algorithm first, since the result might be Good Enough(TM), but even if you end up porting to C anyway, you're porting the improved algorithm, so it'll be that much faster again. I think there are several simple optimizations you can do that will give a...

It seems like you're thinking of how to handle LOS that spans 2 boards, but why not think of it as just one map...? Hexes would need to include the board number as part of their address, but otherwise everything stays the same. But the combinatorial explosion will kill ya. Doing 2 boards will...