|
We use Roll20 for our world map. We have one large-scale map, and have also broken it up into a dozen or so 'detail' maps for each region. I've played with both Maptool and Roll20, and understand the pros and cons of each. From what you've said, I doubt you'd have a better experience in roll20. In general, MapTool is more technically impressive but has a steep learning curve, while Roll20 is less fancy but 'just works' without a steep learning curve.
It sounds like your problem is trying to generate overly-detailed maps. A large map optimized to look gorgeous will be anti-optimized to load quickly, and vice versa. For example, having a detailed texture on your 'forests' and 'oceans' requires a lot of bits, each of which must transfer across the network and be loaded into your VTT. E.G. Try making your forest 'green' and your ocean 'blue', without lot of detailed texture. Such maps will load a lot faster.
The solution you seek isn't using different software. The solution is learning to make leaner maps. Start with a black-and-white line-drawing big map. Verify that works well. Then add a splash of color and a bit more detail, and see if that slows things down. Find the 'sweet spot' where you get a nice-looking map that also loads quickly.
Carefully watch the 'file size' of the maps you generate. It's perfectly possible to create a large-size map that looks pleasing to the eye, but does not occupy lots of file size. This is an art, and requires practice. File format may also make a difference, as different image formats(e.g. PNG, JPEG, GIF)are optimized for different purposes.
I would get a roll20 account to see if they run any better. I would also try jpeg vs png. If that does not work try breaking the map up into 4 sections. I know you want a world map but 20 MB is big.
|
|
Either use something besides hexographer, else explore ways to have that software generate reasonable-sized files. The software you use to generate your maps seems to not be intended for making lightweight maps. I don't know Hexographer. Unless it has some way to control this sort of detail, it's the wrong software to use.
As a general rule, you want to keep all map files under 1 MB, preferably less than 100KB. That will make things feel responsive and snappy for your players. Sometimes we allow our big maps to reach 5 MB, but that's about where things start slowing down.
Note that various (free!) Image Editing software programs have the ability to edit things like detail-level and image size. Definitely don't spend $$$ on this, as the free tools are also the best tools.
You either need to find a different way to make your big maps, else you need to do some post-processing (in other software) to make your maps reasonable sized. There are dozens of tips and tricks to do this.
The problem you are bumping into is the EXACT SAME problem that every graphical web designer faces: how to generate a pleasing visual image within reasonable bandwidth constraints. Again, this is an art, and requires practice. Understanding image file formats will help a lot: you need to choose the right format, as Wraithstrike mentions above. PNG is probably (but not certainly) your best option.
roll20 can have the background size change + you can use hex grids, but it screws up distance calculation.
Roll20 automatically breaks maps up into sections to reduce the processing load on your computer. This is a behind the scenes element to how Roll20 works and will not affect how you use your maps.
If you use a 5MB map (maximum size limit for free users) it should not slow things down provided it is not PNG. If you can, avoid PNG images for maps because PNG maps may slow down people's processing time (PNG is a resource hog).
With that said, my suggestion is taking your mega-map and breaking it up into sections using an image program such as Gimp.
Also, there is a practical size limit for hex maps in Roll20. If you find you need more than 500x500 hexes (just a ballpark estimate) you may want to consider breaking the map up in separate pages.
If you decide to use Roll20 and you need further help feel free to ask. You can find me on the Roll20 boards. :)
I've been using Fantasy Grounds for a long time now and have shared maps that are zoomable and very large/detailed with zero lag or slow down.
Well currently I don't have one huge map. Since a world map would need about 1250x625 hexes, I only make maps at 240x120. Problem is each hex is already small at 30x26. Currently, the world map is about a dozen of these 240x120 chunks, and each once is about 20 MB, so it's loading literally 200+ MB.
I'll try checking out Roll20 and/or Fantasy Grounds for this and see if it meets my needs. Unfortunately, making a world map in 12-mile hexes seems like it might be difficult regardless of the platform.
Also, I do use transparency. You can't make a square image out of hexes and overlay them without transparency.
okay, yeah, WAY too big. also, if you cook the hex grid onto the other image you won't need transparency. Transparency is REALLY a hog on your GPU.
DreamGoddessLindsey, what is the DPI of your images? If you can bring the DPI down to about 75 it should reduce the file size considerably.
If you would like I can help you get set up (I am a Moderator on Roll20).
|
|
I use MapTool and have the Inner Sea World Map as a hex map. No problems.
Are you using the MapTool grid overlay?
I use the Inner Sea World map and overlay the hex grid to map scale, with each hex being 12 miles. I use a single token to represent the party. Set the vision to 0 or 5' and then they can only see the hex they are in or the surrounding hexes and the areas of the map already revealed. You should be able to do something similar.
As long as you can get your image to less than 5 MB, you shouldn't have any problems. Gimp (free) can help with that or Photoshop if you have it.
|
|
Okay, tried shrinking the maps, but the loss of quality makes them unplayable. I tried going to 1726x1000 at 25dpi and the map was still over 10 MB. I'm fairly proficient in this software, so I'm not sure what's causing this.
The problem here is that you're trying to use the software for something it was never intended for. It was intended to print large paper maps. It was not intended for use with a Virtual Table Top, so it doesn't generate the right style of images.
Part of the problem, though, is certainly trying to make a true WORLD map that has the entire world in 12-mile hexes.
Agreed. 12 mile hexes is way too much detail for a world map. 100 mile hexes is more like what you want.
Can't use Fantasy Grounds because it costs way too much money for me. Roll20 doesn't work because it goes in squares and not hexes.
Incorrect. Roll20 does both grids and hexes. We use hexes for our Roll20 World Map.
Actually, I might be able to fix it by reducing the size Hexographer exports to so that the resolution has a natural resize. Then I'll take those, shrunk to 10x12 hexes, combine them into a single map to be loaded instead of multiple objects. Our computers can certainly handle the load.
Your best bet is to abandon hexographer, or to use its output as input to another graphics software. E.g. free GIMP or expensive Photoshop. Hexographer is the wrong too for the job you are applying it to.
DreamGoddessLindsey, after reducing the DPI to about 75 or 100 try splitting the map into pieces using GIMP or Photoshop.
Example:
If you have a 100 DPI map and it is coming in at 40 MB split it into 9 pieces and they should each come in under 5 MB.
I can help you get set up in Roll20 if you would like. Private message me a join link (note: I am a Moderator on Roll20).