Upgrade your account to a Community Supporter account and remove most of the site ads.

Reply to thread

Message: <blockquote data-quote="pming" data-source="post: 7344465" data-attributes="member: 45197">Hiya!As [MENTION=29314]Del[/MENTION]richo said, don't sweat it. A "thing" in a hex usually represents the most prominant thing...not necissarily the most pelentiful, and with regards to settlements a settlement could be virtually anywhere in that 'hex' (right at a corner, smack dab in the middle, or anywhere else).My suggestion is: Don't use a hex or grid. Decide how big you want to print it (in inches). Make the resolution at least half of what your printer will print at (typically its 300 - 600 pixels per inch...so your map should have at least 150px per inch). I have a map of "Darkurthe" (yes, from the RPG Darkurthe Legends) that I made myself. IIRC, it's at 150dpi and printed out (at a photo place) the size was 28" x 32". It still wasn't quite big enough to easily read the city/town names...I need to double it.Anyway, the non-grid map thing. Draw your own scale on your map AFTER you do a rough outline of your continent. Decide how big you want it to be...that will give you your "Scale: 1 inch = 120 miles" or whatever. I suggest choosing a distance that is easily dividable by 2, so 32, 24, 12 etc...it makes it easier to eye-ball distances and figure out time to travel, imho.Once you have your grand "continent" map, save it. Any smaller kingdom maps you want all you have to do is copy the layer with your Scale on it, select an area to Crop To..., crop it, then past your Scale layer into this new "Kingdom" map. Save this immediately as a new file! Don't accidentally over-write your Continent map file!This makes it easy to 'zoom into' or out of any map. The key is to have your own "Scale" layer that will be consistent across all your other campaign overland maps. If you must have a grid, you can make a grid based on the size of your scale distance. But, if you have a 'regular' visual Scale...you won't need it.^_^Paul L. Ming</blockquote>

Verification