Need Hex Maps Advice

Greetings, all. I'm trying to set up a hex-based map for a friend's campaign and I'm not having any luck. The map-making software I have (Worldographer) doesn't line up with Roll20 -- apparently 70px means something completely different to the two programs (somehow). Does anyone know of any hex map software or tools that do  align properly with Roll20? Thanks in advance for any help.

Maybe you can set it up just by using the number of hexes?  Also roll20 can use vertical or horizontal hexes.  If you set your page to the wrong one, it wont line up no matter what you do. If all else fails, I make all my maps with Inkarnate and have no issues with roll20 grid.  I just set the page to the same number of squares or hexes as the map I create, and use the "Resize Fit" option on the right click menu.

If you are using Hex (H), someone came up with something that worked for them. From  this thread : "If you are using Hex (H), and a square map, set the page height to to the number of hexes, vertically. Set the width to that number multiplied by 1.0082976746938481461036010506722. Set the cell height multiplier to 0.87841715270730512222684903731446."

David M. said: If you are using Hex (H), someone came up with something that worked for them. From  this thread : "If you are using Hex (H), and a square map, set the page height to to the number of hexes, vertically. Set the width to that number multiplied by 1.0082976746938481461036010506722. Set the cell height multiplier to 0.87841715270730512222684903731446." There's "very" accurate, and then there's "you-made-my-calculator-commit-suicide-out-of-shame" accurate.

For hex maps you can use roll20 with hex art assets. In the following post a api script is described that will autosize all hex images when you drop them on the map. <a href="https://app.roll20.net/forum/post/9707488/script-artresizer-solution-to-automatically-resize-art-when-dropped-on-the-map/?pageforid=9707488#post-9707488" rel="nofollow">https://app.roll20.net/forum/post/9707488/script-artresizer-solution-to-automatically-resize-art-when-dropped-on-the-map/?pageforid=9707488#post-9707488</a>

Oosh said: There's "very" accurate, and then there's "you-made-my-calculator-commit-suicide-out-of-shame" accurate. Well, I suppose you *could* round it to an even 30 decimal points... if you wanted your map to look like crap ;)

David M. said: Oosh said: There's "very" accurate, and then there's "you-made-my-calculator-commit-suicide-out-of-shame" accurate. Well, I suppose you *could* round it to an even 30 decimal points... if you wanted your map to look like crap ;) Good Lord. You almost made me have to go wash breakfast smoothie off my keyboard.

Ryan E. Let me know if that works for you, or what solution you come up with. I do considerable freelance work for Worldographer, and I know the dev would appreciate feedback like this. (He might even be interested in hard coding a solution).

David M. said: If you are using Hex (H), someone came up with something that worked for them. From&nbsp; this thread : "If you are using Hex (H), and a square map, set the page height to to the number of hexes, vertically. Set the width to that number multiplied by&nbsp;1.0082976746938481461036010506722. Set the cell height multiplier to 0.87841715270730512222684903731446." Here's the problem with that. Worldographer seems to really, really &nbsp;dislike using decimals in hex measurements -- it leads to the hex images getting stretched out into adjacent hexes and strange gray artifacting filling in the gaps. That's why I'm looking for other software that's hex-compatible with Roll20. Honestly, I'm a bit surprised that hex proportions don't have a universal standard or anything...

Ryan E. said: It looks like your map is set to Hex (V) but your page is set to Hex (H). But that image is a little odd looking in general -- like there are hex images being forced into vertical columns, instead of a true hex layout. But I'm not a graphic designer and I know nothing about Worldographer so hopefully Keith can help you!

That does appear to be part of the case. Those are Row Hexes in a Column Hex layout. (every iso terrain hex has a row and a column version—it has to be because they are raster images, not vector) It also appears that the original is still in isometric perspective, which would keep the export from fitting a Roll20 grid.

Note: The settings recommended above were for the Roll20 Hex grid settings, not the source software/image output. That being said, that screenshot looks pretty jacked up.

David M. said: Note: The settings recommended above were for the Roll20 Hex grid settings, not the source software/image output. That being said, that screenshot looks pretty jacked up. Correct. The screen shot indicates that the settings were not correct in Worldographer to begin with. Ryan needs to go back to Worldographer and correct the hex orientation there before outputting anything.

Hey Folks, Worldographer/Hexographer developer here.&nbsp; It does look like the sample map snippet by Jarren uses what we call "isometric rows" hex images in a map intended for "columns".&nbsp; You'd want to replace that terrain with "Isom. Cols" terrain--at the top of the Terrain drawer is a drop-down where you can filter the terrain.&nbsp; Also, the perspective (hex width vs. height) could be tweaked a bit to help with the isometric style--you'd want to make the hexes 75 pixels wide and 56.25 high. (This makes the hexes look squished, but that's what we're going for to play a trick on the eyes.&nbsp; You can leave it if you prefer.&nbsp; You can also use our "classic" icon set which is better designed for true hexes.) You can change to an isometric perspective in an existing map by changing the values under the "mini-map" in the upper right of the program.&nbsp; Make sure you uncheck "Preserve Aspect Ratio" near those settings so it doesn't auto-change the other as you change one.&nbsp; Or if starting a new map look for the pixel settings on the create new world/kingdom dialog.&nbsp; That dialog has other info for typical pixels sizes/ratios for other perspectives. I'm a Roll20 novice, so I'm going to play with it a little and see if I can come up with some ideas to make importing the maps easier.&nbsp; Based on my initial experience, because Roll20 is using a square grid behind the scenes, some trial and error may be necessary. The snapping to the square grid (even if showing a hex grid) also causes the map to jump from where you want it, so I recommend holding down "alt" while you move it so it doesn't snap. (Thanks Keith!) You also probably want to only resize one dimension (width or height) at a time so changing one doesn't mess up the other. But I'll see what else I can come up with.

And if you make the roll20 grid transparent after resizing, it hardly shows if the resize is one or two pixels off.

I summarized what I did to get a Worldographer map (although the same would apply to its predecessor Hexographer) into Roll 20 on this page .&nbsp; Again, I'm a Roll20 novice, so if anyone has constructive criticism please let me know.

Just an FYI, my thread no longer applies, they changed how calculations are done I guess... The changed "Cell Height" to "Cell Width" some reason, and I forget the math I used to get my numbers, so I gotta figure out what width to use. Love breaking changes to their already broken hex system. At least I think that's what happened because I can't get my maps perfect anymore :( Edit: nvm I think I just exported my images incorrectly.