Which installer did you use when installing this? I noticed yesterday night that I had the same issues as you on my main computer where I had only ran the individual issue installers as they arrived, but the complete 2020 installer set up the template properly on both my regular system and my test system when I installed that.

Best way to transfer effects and sheets over is to save the preset from a working map. Load up the @annual\Issue165 Smaple cliff.fcw file, go to the effects dialog, and save the current setup as a preset. Now, in your own map, load the preset. Do notice that new sheets added WILL be added to the bottom of the list, you must rearrange them yourself.

Looks like the installer may not be replacing the template properly. Do a Draw -> Insert file, pick the @Annual\Issue 165 - City Cliffs\CA165 Cliff Import.FCW file, and hit ok. Once the dialog closes and CC3+ want you to place the inserted file, hit Esc.

As for the fcw32.mac issue when re-running update 25, it is safe to simply hit ignore on it. Only thing that will happen is that you won't get a backup copy of the file if you had manually customized it (which most people never do anyway).

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.