Menu
News
All News
Dungeons & Dragons
Level Up: Advanced 5th Edition
Pathfinder
Starfinder
Warhammer
2d20 System
Year Zero Engine
Industry News
Reviews
Dragon Reflections
White Dwarf Reflections
Columns
Weekly Digests
Weekly News Digest
Freebies, Sales & Bundles
RPG Print News
RPG Crowdfunding News
Game Content
ENterplanetary DimENsions
Mythological Figures
Opinion
Worlds of Design
Peregrine's Nest
RPG Evolution
Other Columns
From the Freelancing Frontline
Monster ENcyclopedia
WotC/TSR Alumni Look Back
4 Hours w/RSD (Ryan Dancey)
The Road to 3E (Jonathan Tweet)
Greenwood's Realms (Ed Greenwood)
Drawmij's TSR (Jim Ward)
Community
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Resources
Wiki
Pages
Latest activity
Media
New media
New comments
Search media
Downloads
Latest reviews
Search resources
EN Publishing
Store
EN5ider
Adventures in ZEITGEIST
Awfully Cheerful Engine
What's OLD is NEW
Judge Dredd & The Worlds Of 2000AD
War of the Burning Sky
Level Up: Advanced 5E
Events & Releases
Upcoming Events
Private Events
Featured Events
Socials!
EN Publishing
Twitter
BlueSky
Facebook
Instagram
EN World
BlueSky
YouTube
Facebook
Twitter
Twitch
Podcast
Features
Top 5 RPGs Compiled Charts 2004-Present
Adventure Game Industry Market Research Summary (RPGs) V1.0
Ryan Dancey: Acquiring TSR
Q&A With Gary Gygax
D&D Rules FAQs
TSR, WotC, & Paizo: A Comparative History
D&D Pronunciation Guide
Million Dollar TTRPG Kickstarters
Tabletop RPG Podcast Hall of Fame
Eric Noah's Unofficial D&D 3rd Edition News
D&D in the Mainstream
D&D & RPG History
About Morrus
Log in
Register
What's new
Search
Search
Search titles only
By:
Forums & Topics
Forum List
Latest Posts
Forum list
*Dungeons & Dragons
Level Up: Advanced 5th Edition
D&D Older Editions, OSR, & D&D Variants
*TTRPGs General
*Pathfinder & Starfinder
EN Publishing
*Geek Talk & Media
Search forums
Chat/Discord
Menu
Log in
Register
Install the app
Install
Upgrade your account to a Community Supporter account and remove most of the site ads.
Community
General Tabletop Discussion
EN Publishing
One Inch Battlemaps
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="EugeneZ" data-source="post: 5241572" data-attributes="member: 83605"><p>Those maps weren't normalized properly, is my guess. I didn't normalize most of the maps from the first module. I really should do that. Since I'm short on time these days and converting Tears is my priority at the moment, I'll try to briefly explain the normalization process.</p><p></p><p>Step 1) Use any software with a ruler to measure an arbitrary number of squares in either direction. The more the better, but they must be full squares. So, for example, measure the exact number of pixels from the bottom of the lowest possible square to the top of the highest possible square. Ignore squares that are cut off. Only count pixels in one dimension, either x or y.</p><p></p><p>Step 2) Count the number of physical squares that you just measured the length of. At this point, you should have something like this: 943 pixels = 35 squares. This number gives you the current "zoom level" of the map. Divide the number of pixels by the number of squares to give you the zoom level: 943/35 ~= 26.943. The more decimal places you keep, the more accurate the final result is, so don't just round to the nearest integer.</p><p></p><p>Step 3) Using the same dimension you used for the length count, get the image's TOTAL length in that dimension. In the example above, I measured the y (top-to-bottom) dimension of most of the squares on the map, but I didn't count a few obscured squares at the top because I couldn't tell where one square ended and the next began. The bottom-most square was also not counted because it was cut off. So the height of this image was 1200.</p><p></p><p>Step 4) Divide the total height by the zoom level you obtained earlier. This gives you the total number of squares the image REALLY has. In my example, I would do: 1200/26.943 = 44.538. My image has 44 and a half real squares.</p><p></p><p>Step 5) Decide what zoom level you want to normalize the map to. I always use 50px. Multiply the result of Step 4 by this number. So 44.538 x 50 = 2226.9235.</p><p></p><p>Step 6) Resize the image. Make sure your editor's "Maintain aspect ratio" option is enabled. Change the value of whatever dimension you were using to the result of step 5. I was using y, so I'm changing the height of the image to 2227. This time you have to round to the nearest integer. Hit OK, and the software will resize the image. Every square will be exactly 50px, or close enough that maptools won't be able to tell the difference.</p></blockquote><p></p>
[QUOTE="EugeneZ, post: 5241572, member: 83605"] Those maps weren't normalized properly, is my guess. I didn't normalize most of the maps from the first module. I really should do that. Since I'm short on time these days and converting Tears is my priority at the moment, I'll try to briefly explain the normalization process. Step 1) Use any software with a ruler to measure an arbitrary number of squares in either direction. The more the better, but they must be full squares. So, for example, measure the exact number of pixels from the bottom of the lowest possible square to the top of the highest possible square. Ignore squares that are cut off. Only count pixels in one dimension, either x or y. Step 2) Count the number of physical squares that you just measured the length of. At this point, you should have something like this: 943 pixels = 35 squares. This number gives you the current "zoom level" of the map. Divide the number of pixels by the number of squares to give you the zoom level: 943/35 ~= 26.943. The more decimal places you keep, the more accurate the final result is, so don't just round to the nearest integer. Step 3) Using the same dimension you used for the length count, get the image's TOTAL length in that dimension. In the example above, I measured the y (top-to-bottom) dimension of most of the squares on the map, but I didn't count a few obscured squares at the top because I couldn't tell where one square ended and the next began. The bottom-most square was also not counted because it was cut off. So the height of this image was 1200. Step 4) Divide the total height by the zoom level you obtained earlier. This gives you the total number of squares the image REALLY has. In my example, I would do: 1200/26.943 = 44.538. My image has 44 and a half real squares. Step 5) Decide what zoom level you want to normalize the map to. I always use 50px. Multiply the result of Step 4 by this number. So 44.538 x 50 = 2226.9235. Step 6) Resize the image. Make sure your editor's "Maintain aspect ratio" option is enabled. Change the value of whatever dimension you were using to the result of step 5. I was using y, so I'm changing the height of the image to 2227. This time you have to round to the nearest integer. Hit OK, and the software will resize the image. Every square will be exactly 50px, or close enough that maptools won't be able to tell the difference. [/QUOTE]
Insert quotes…
Verification
Post reply
Community
General Tabletop Discussion
EN Publishing
One Inch Battlemaps
Top