When you need to to a precise export, make sure that you only export the map itself, and not any border/screen, as this will mess up your calculation. This is typically what causes the drifting you describe since then borders steal some of the pixels you calculated for the grid cells, they suddenly aren't 50 pixels anymore. Use the save as rectangular section to accomplish saving just the map. Make sure that the export size is calculated correctly, for example, a 11 by 12 squares map sghould be exported as 550 by 600 pixels to fit with 50px/square

Also note that 50 px/square does not give you a very high quality result if you like to zoom in as in your image above. I recommend at least 100px/square, MapTools handles that fine (Of course, that also means that the players get sent a bigger file, so you need to weight quality against bandwidth/transfer times here)

Generally, I also prefer to leave the grid off from my CC3+ export, as it generally isn't needed. That also minimizes the effect of drift a bit, but again, drift won't be an issue if the export size is correct.

Maybe my blog article here can also help you a bit:

Second edition is the best :)

(Currently playing 2nd ed this weekend with my friends actually)

These maps are great as player handouts. I love how they describe the route and let the players know what to look for and what to expect without giving them a complete detailed regional map.

I currently have my players following a river with such a map in hand.

The new maps from Quenten is now in the atlas. Thanks for the contribution.

You'll need to contact support by email, and they'll help you out.

The issue that occurs here is that because of memory constraints, CC3+ cannot compute the entire high-resolution map in memory at the same time for the export, which is why it exports in multiple passes, each pass rendering a part of the map.

Unfortunately, effects from entities outside of the current rendering part won't be considered, such as shadows from entities far away. There is a certain overlap to handle the closer but right outside things, but considering effects from everything in the map is impossible due to the aforementioned resource problem.

However, you can change the default size of these render chunks, causing CC3+ to render much more of the map in one go. This is done by typing in EXPORTSETMPPP on the CC3+ command line and hitting enter. The command line will then ask for the number of pixles, type in the value 40000000 (The current value, shown in brackets is probably 4000000, keep your zeroes straight). and hit enter. Depending on your export resolution, you will export the map in much fewer passes, perhaps even just a single pass.

Note that if this isn't enough, the other solution is to either consider using shorter shadows, avoiding the problem, or manually creating them using a partially transparent polygon.

Well, there can never be enough tutorials, but it is described in the Manual, which is a tutorial for the program. I know some people prefer videos instead of written word (that still boggles my mind, really), but videos do take time and effort to make (and are also way more difficult to keep up to date compared to written text). I do make video tutorials, but it is difficult to get to everything.

Being druids, they have access to the control weather spell. Maybe they keep each of the four villages is like that year round? ;-)

The druids have now found their home in the atlas. Thanks Quenten.

Well, that's the problem then. Just move the COASTLINE sheet upwards to right between RIVERS and ROADS, which is where it is supposed to be.

What probably happened here is that the COASTLINE sheet was missing from the template you used, which caused CC3+ to automatically created it when it was needed for that outline. But CC3+ don't know where in the order to put such a automatically created sheet, so it just puts it on top of everything.

Edit: And a fast Lorelei sneaks in......