Corporal Kindel
Member
I didn't see the tarawa map in the historical maps section; has it been updated or something?
They have no adressable hexes, so they don't help for the scenario 73 problem with it's beach and ocean overlays.Been working on some "filler" boards to make laying out the Action Pack boards more intuitive. Maybe they'll help for this.
https://dl.dropbox.com/u/38910931/Fillers.zip
You're right, it works.You sure about the hexes? If I wiggle a squad around I see:
* 8-3-8 AEsq moves Filler2D0/E1 -> Filler2E1 *
* 8-3-8 AEsq moves Filler2E1 -> offboard *
Seems to crop for me with parameters: board: Filler2 hex rows: A E
I was also able to add overlay G1 to hex C1 successfully.
(edit) The bounds of the overlay are limited to the size of the board, so maybe you just need a larger filler but it *seems* be generally functional.
These are wonderful.Been working on some "filler" boards to make laying out the Action Pack boards more intuitive. Maybe they'll help for this.
When setting up scenario 73 in VASL, overlays Wd5 (the island) and OC2 (on the right) work, but overlays OC4 + OC3 (on the left) are cut off at board edge.See if this one does the trick:
https://dl.dropbox.com/u/38910931/FullGeo.zip
These were my previous attemps (first with board 27, second with cropped board 27 and draggable snow overlays, third with cropped board LFT1 flipped):>> but overlays OC4 + OC3 (on the left) are cut off at board edge.
Overlays can't extend beyond the boundary of the board as a general rule.
Can you give me the coords for the overlays and I'll try it out over here and see what may need to be done to remedy.
I have had trouble with other VASL scenarios setups if an overlay spanned more than one board - it always got clipped at the board edge.May be a bug with post-setup overlays. I can reproduce with "normal" boards too (note that AFAIK, Filler0 is a normal board):
Now I've set up totally new (setting up the boards and the overlays together), and it works fine (last time I had only changed the placeholder board into filler0 and then added the overlays):May be a bug with post-setup overlays. I can reproduce with "normal" boards too (note that AFAIK, Filler0 is a normal board):
I was about to write, "why, just use Filler0 twice", but then I realized that won't work if you have overlays defined on both (but should, for instance, if you just need the overlap feature). Good catch.Maybe you should offer a second full-sized filler board to support wider beaches too ...
That was the reason.I was about to write, "why, just use Filler0 twice", but then I realized that won't work if you have overlays defined on both (but should, for instance, if you just need the overlap feature). Good catch.
Maybe instead of FillerX-Y I should go with DescriptorOfBlankX-Y, e.g. OneRow1, OneRow2, Full1, Full2, etc.
Also name them to include (H)orizontal or (V)erticalI was about to write, "why, just use Filler0 twice", but then I realized that won't work if you have overlays defined on both (but should, for instance, if you just need the overlap feature). Good catch.
Maybe instead of FillerX-Y I should go with DescriptorOfBlankX-Y, e.g. OneRow1, OneRow2, Full1, Full2, etc.
That's originally what I was making the fillers for. The T-shaped some of the other oddly placed setups were my first test cases.That was the reason.
And maybe you should provide filler boards corresponding to Fort's new a/b boards ...
Very doable.Also name them to include (H)orizontal or (V)ertical