First map of the set is now in the atlas. Thanks for contributing. This is an exciting project.

I just love everything you can do with CC3+ thanks to its CAD roots. I've lost count of how many weird things I've done with it that doesn't have anything to do with mapping (Well, I guess some of them can be called mapping in a very wide definition of the term).

Multipoly combines multiple entities into one. The main advantage of multipoly is that it can be used to create holes in shapes which is needed for things like holes and some valleys.

But multipolies aren't editable, because they are a composite entity. Only way to edit it is to break the multipoly (:CC2EXPLODE:), edit the entities it is made up from ,and then reform the multipoly.

The contours follow the coloration of your FT3 world. If your contours are all in a close range, they may indeed all come out the same color since the FT3 coloring is "world scale" not "local scale".

If you set up advanced contours in the export settings, you can go in and manually assign a color to each contour level overriding the default height matching

The scaling is just the size you want that tile to show up in your map as. For example, if that tile should fit to a single 5' square (and thus repeat every 5'), you'd set the scaling to 5, if it is supposed to fit a 10' square the scaling is 10, and if it should repeat every 100', the scaling should be 100. Simple as that. It doesn't have anything to do with the pixel size of the image. (Well, it is kind of related, as a small image can't be scaled up or it would look pixelated, and should have a somewhat small scale too, but the poitn was that you cannot read the scale out from the pixel dimensions of the image)