These aren't values stored in the map that can be simply accessed.

The Drawing area size is found by calculating the extents of the current drawing. CC3+ drawing doesn't actually have a fixed size (as you may have noticed, you can easily draw far outside the map border with the basic tools. So the size you see in this dialog is just the current extents of the entities in your map. Finding the extents is basically just walk the list of entities and grab all the coordinates there and just pick out the biggest and smallest ones, these will describe your extent.

As for the pixel size, CC3+ doesn't care about pixels at all. The value you refer to is just whatever value you happened to put into the export dialog the last time you used it, but it has nothing at all to do with the current map. And any CC3+ map can be exported to any pixel size, so to calculate in relation to the export size you must know what resolution the user intends to export in. Now, usually, when you export battle maps for VTT use, you would use whatever number of pixels per map square as that particular VTT system prefer. I don't know what foundry want, and it probably can use different values, but that is the value you want, not whatever is stored in the CC3+ dialog. And there is really no way for CC3+ to tell you this since it doesn't work in pixel space. But you could assume some standard pixels/square, for example if you plan on exporting the map as 100 pixels per 5' square, that relates to 20 pixels per map unit.

What Julian says is correct, but just to add one thing; just ignore that number entirely. It doesn't have anything to do with the quality of the image. Or put differently, there are two ways to know the quality, either you know the resolution in pixels, or you know the dpi AND the display size (inches). While sometimes used to make sure things is right sized for a computer screen, the dpi is really a value only appreciated by people who does professional printing and print layout.

Another set with maps integrated into the atlas. Thanks for the contribution Ricko.

Part of your problem at least is all those contours.

The Mike Schley style isn't a style that relies on height contours, it uses symbols. So there wouldn't be appropriate fills for those contours which probably leads to all those solid filled areas.

I've attached my Mike Schley export settings to this post. I don't remember if I have modified it or not, but it seems to export an appropriate result for the Schley style anyway. Just unzip the archive and put the file inside in C:\ProgramData\Profantasy\FT35\Export overwriting the one there already

Well, except from the obvious lack of cats, they are awesome.....

I find the divisions of the bottom scale bar slightly hard to make sense of though.

Thanks, that completes this set.

According to the count, there are now 1099 maps in the atlas. No need to go out and hurry to make the 1100th one though, I still have maps in queue for processing.

I think you used the wrong button. In the video, Ralf used Change Properties, but you write Edit Properties in your post, and that prompt is indeed the expected one if you use Edit Properties.

The change Properties and Edit Properties button do look a bit similar, so they are easy to confuse.

It is the same command which is triggered no matter if you use Ctrl+C, pick from the menu, or the button right click. All of that are just simple shortcuts to the same command.

But for copy, it is important do follow the advice from @Wyvern about waiting till the command actually finishes and the selection indicators disappear, only then is the command done and the contents on the clipboard. And equally important is it to actually finish the command, a lot of people forget to pick the requested origin point after hitting Do it, but if you leave out that part, the command isn't done, and nothing will be copied to the clipboard. (Always pay attention to the command line)

A good way to notice things like that is if you look at the command line while executing the macro. A macro that successfully and completely executes should return to the Command [LASTCOMMANDNAME]: prompt.

In your case, you could see that it was instead asking for a filter, with a word prefilled.

You don't need to install on c:\

What happens when you install CC3+ is that a very tiny portion of the program is always installed on C no matter what you pick in the installer. The bulk of the program is installed to wherever you pick in the installer, and it is fine to put that on any drive (Should be a local drive though, not external drive or network drive)

If you have parts that seems to be installed outside the data directory, it might be that you have performed an artwork-only install on those components. This type of install is intended for people not using CC3+, but just want the artwork for use in other software. The files in these directories are NOT the complete set of files CC3+ needs, so they should not be manually copied into your CC3+ data directory. I think just re-running the installer for those "missing" products should help. The separate art file directories are just a bunch of image files, and can be safely deleted manually.