The map exported from FT3 should be in the correct scale already.

The scale bar may be wrong, that's a known bug. Try to measure the actual distance with the Info -> Distance tool.

Also note that map projection can also affect scale. FT3 exports the map using the current map projection. Depending on the projection, areas nearer to the poles may be distorted/enlarged (like Greenland in the real world). If this is the issue, try using another projection in FT3 when you export.

A nice map, but here are some thoughts:

• Too much variation in font size. Makes it look messy.
• A few more vegetation symbols would be nice, especially on the islands that have none.

To elaborate a bit on Sue's answer. RAM is used for bitmap caching in the program, and is also important in determining the maximum export size of the map since that requires space in RAM for the work.

As Sue points out, it uses 4GB at maximum, but it is always a good idea to have that 4GB available to the program, which means that if your computer only have 8GB's of RAM you might need to be careful about what you run at the same time, while if you have 16 or more, it is generally not an issue. The ram allocation needs to be contiguous, so for a lower memory machine, it may need to be rebooted more often as well, especially if you find that CC3+ complains it doesn't have enough memory to complete an export.

You'll easily see if you have DD3 installed by creating a new map in the dungeon type, and see if you have the DD3 dungeon available (as opposed to just CC3 Dungeon).

If you don't have that template, it means you have forgotten to download and install the DD3 setup. It is a separate installer from the main CC3 one. It was included in the Humble Bundle (if you got the top tier), so you should own it.

I assume you scaled it up to that each minor flagstone became a grid square? That might be more than that texture can do. A texture have a limited resolution after all, it can't be scaled indefinitely.

However, it might just be CC3+ displaying the wrong resolution version of the image, that can also happen if you scale it by too much. Try going into :CC2RESMODE: and set the display to manual -> Very High and see if that fixes the issue.