Good work :)

Maybe the coastline can be made thicker, or the most pointy hills shrunk down to miniature size and used as waves? You could draw your own vector symbol waves, or if you have the latest annual issue (Ellis Prybylski Watercolour) there are wave symbols in that one.

You could try a pale transparent shape over the sea to make it fractionally darker than the land, but it might look odd where this is a linework style.

The effect around the labels is a little narrow to separate them from the black detail of the map, but it might be ok if the map is much larger than here.

Hi Kit :)

The map opens with the MERGE layer active. If you pick another layer (STANDARD for example) the edit properties seems to work ok.

The MERGE layer is used by CC3 to control how effects are rendered, so probably best to leave it alone. Don't hide it though, as that can have some really strange effects.

It works in most cases where the drawing tools have been correctly setup to fall on the 'FLOORS*' sheet. The asterisk is a wildcard that allows this to happen. The only proviso is that you do need to have the chosen 'FLOORS Temple floor dirt' sheet picked as the active sheet before you start to draw.

The problem with your original file was a corrupted sheet. I also got an out of memory warning the first time I tried it. Then I discovered there was a problem with the SYMBOLS sheet and created a new one. Once I copied everything across and deleted the original SYMBOLS sheet everything worked ok.

Your system has plenty of memory and should cope ok with 40 million PPP on export. How does it do with the repaired map?

Hi Ian :)

Here's my checklist:

• First, check that you installed CD3. With multiple installers it's easy enough to forget to run one of them, so that's the easy check. Right click your Start button and pick 'installed apps' from there. If CD3 doesn't appear in the list of installed apps it's not installed.
• If CD3 is there, and while you have that list open also check that you have CC3+ installed and not just CC3.
• Run the latest CC3+ update again and see if that puts things right.

Please let us know if there's still an issue once you've done that.