Hex Grid: Map Layer: Assets scale in unexpected ways on hex maps.

It's not possible to drop images that will align cleanly with the built in hex grid. They are always scaled smaller or larger than the grid. Steps to reproduce: 1. Create a new game with a new page. 2. Grid enabled. Type Hex (h). Size: Any 3. Upload a picture of a hexagon cropped to the edges. 4. Switch to the map layer. 5. Drag the hexagon to the map. 6. Attempt to resize it to fit the grid EXPECTED RESULT: You should be able to get your hexagon to almost exactly match the Roll20 map. ACTUAL RESULT: The image is resized a bit smaller at first (Image left) . The first available "snap" size up is too big (image right). Notes: Consider a set of hex tiles that are meant to mix and match with the borders touching (or almost at least). You can, with a lot of fiddling with the ALT key get the size just right. However if you have a lot of hexes to add to the map, this is not a very good solution.

I'll give a shot at answering, giving methods to try, and leave thread open for other responses to your bug report of this. Background info to help understand what's going on there: The Roll20 hex grid has an underlying square grid. Snapping actually snaps to the invisible square grid, which corresponds to the visible Hex grid that you have set. Try setting your hex token dimensions to 103x103 and test it. Either remake your token at 103x103 in graphics editor, or Advanced &gt; Set Dimensions in Roll20. That might make it fit just about perfectly (according to some experimenting and discussion in another thread which I'll link, below). With a Pro subscription of Roll20 you can get access to the community-created API scripts. With the API you can set-up a macro button or chat command that scales or sets a token to a specific size (Token-Mod API or ScaleOnAdd API can do this nicely and quickly). If you have a lot of hexes to add to the map, getting a Pro subscription for a month in order to quickly resize your hex tokens could be worth it for the time savings. Threads, Wiki, and related Marketplace pages to read for related info: <a href="https://wiki.roll20.net/Aligning_Maps#Hex_map" rel="nofollow">https://wiki.roll20.net/Aligning_Maps#Hex_map</a> <a href="https://app.roll20.net/forum/post/3903750/slug%7D" rel="nofollow">https://app.roll20.net/forum/post/3903750/slug%7D</a> <a href="https://marketplace.roll20.net/browse/set/1128/hex" rel="nofollow">https://marketplace.roll20.net/browse/set/1128/hex</a>... <a href="https://marketplace.roll20.net/browse/set/1233/hex" rel="nofollow">https://marketplace.roll20.net/browse/set/1233/hex</a>...

Thanks for the reply. I scaled my hex to 103x103 and tried again with the same results. So I may not be understanding your suggestions. Here are the results of my experiments. On the left my "successful" image. It's 140x140 (or a multiple). The background would be transparent, but I marked it in red for clarity. a 90x90 hex image is centered in the box. When dropped on the map and scaled down one automatic step, the visible hexagonal area fills the grid correctly. The drawback is that tiles will be overlapping quite a lot. In the center my experiments with 103x103 sized images. #1 The UI applied resizing and shrunk the hex part too small. #2 I set the size to 90x90 in the advanced menu. #3 I set the size to 103x103 in the advanced menu as you seemed to suggest. On the right you can see why images need a buffer to work. The hidden square grid keeps the tiles touching but not overlapping. Ideally it would scale them to the width of the hex IMO. (or height if the hexes are turned 90 deg.)

What if you create 90x90 hex tokens, or size them to that dimensions setting? That size looks nice in your experiment sample. The 103x103 also looks nice if you plan the hex-style in which each hex token has a border of its own built in, so that the overlapping pixels will be mutual borders of matching color such as black. That was found to be the suggested solution for the Fantasylands hex art pack from a Marketplace link in my previous post. Note: If you hold ALT when you originally drop the token onto the tabletop, or if you drop the token originally onto a Page that has no grid applied, in those 2 cases it should drop onto tabletop at the token's native graphic size. (Avoiding UI resizing)

90x90 tokens were auto-sized to 70x70 to fit the square grid, which is secretly 70x77 and offset by -35 Y in every other cell. You can make out the hidden grid in the right hand side of my last example The only one that "works" is 140x140 transparent with the hex part being 90x78 in the center. Even that one is auto-sized to 280x280, but at least it snaps to the correct size easily. I assert that auto-sizing to the hidden square grid on a hexagonal grid is counter-intuitive. Ideally assets (at least on the map layer) would automatically size to the longest dimension of the hex. In the default case that would be 90x90. (This would break some existing hex sets, so it would be nice to be able to choose in settings or mitigate that problem somehow.) I don't wish to buy some hex sets to see how they currently work, but I suspect one or more of them may not be working as intended since the 103x103 advice was correct. Edit: ALT-Dragging 90x90 hexes works. That's the best solution currently.

Dustin A. said: Edit: ALT-Dragging 90x90 hexes works. That's the best solution currently. Super. Good finding. Auto-sizing is not perfect, but fortunately it is optional and can be avoided at token-sizes, with that method.&nbsp;