Usually, the annuals come away the other way around. ProFantasy spots an artist already doing an interesting style (maybe as a result of a tip from the community), and then works with that artist to bring their style into CC3+ (as an annual or symbol set, assuming the artist is willing obviously). This basically means that the map types will reflect what the artist is already doing.

May it be that you are just confused by the Edit Properties box? The properties shown there ARE NOT the current properties of the entity selected, but rather the currently set properties on the status bar. It can be a bit confusing at first that it behaves that way, but it is much more friendly when you start working with multiple entities at once, and you are also much more likely to need to change properties to the current status bar settings rather than inspect existing settings.

To see what sheet an entity is actually on, use the Info -> List command on it.

This is a property of those symbols, standard behavior on the SS5 trees.

This setting is often configured for symbols that you may want to place along another entities, but should not go in the middle of the other entity, such as a alley of trees along a road (or in a dungeon, torches on a wall). It allows you to easily make sure all of the entities have the same distance from the centerline of the target entity.

The reason you don't see it every time you place a tree is that it is only triggered if you actually align the tree to something else. If it is placed in free empty space, there is nothing to align to, so this step will be skipped. To force this behaviour, when placing trees, move your cursor over a line/poly entity in your map, such as a road. You'll notice that once your cursor is over the center line of the road, the tree will rotate itself to align with the road ("aligning" for a tree may not be very obvious, but you'll see it rotate anyway), and if you click to place when it is in this state, you will get the Offset behavior.

If it just seems to happen out of the blue, for example in an empty area, there probably is a line or edge of a poly hidden on a sheet behind there somewhere. Even if you can't see it, CC3+ will detect it.

Here's the next maps from the competition integrated:

@HelenAA

@Daniel Pereda De Pablo

@Jeff B

@MakeWayForJebus

@Monsen

@Ralf

@Quenten

@Loopysue

This concludes the maps from the contest (I hope. Let me know if I forgot anything), with the exception of @Lorelei's entry. I'll process that whenever she has the parent map ready.

Thanks to everyone who participated. This put us solidly past the 1000 map milestone. Currently, there are 1033 maps in the atlas, and with all the maps that has piled up on the forum awaiting my processing, we are closing in on the 1100 mark.

Now, there's a familiar name. I've never seen her Middle Earth atlas, but I do have her Forgotten Realms atlas on my bookshelf, full of lovely hand-drawn maps.

Contrary to many of you, I had an upbringing where fantasy was simply not on the menu. I don't think my family had anything against it, it was simply not something they had heard about either. It was never a topic among the kids at school either. Tolkien was something I only learned of as an adult, after I learned about role-playing games which happened in my mid-teens. First as computer games (Eye of the Beholder anyone?), then the real deal.

I guess the closest I got to fantasy was the Narnia books, which I guess by one definition clearly fits the genre, but on the other hand doesn't really match up with the common fantasy archetypes, and I don't think there was any maps in any of the books I had.

The software is 32-bit, so it can't address more than 4GB of memory, which it should do by default.

That said, the rendering is CPU-bound, so unless you are manually forcing it to always use very high quality textures in the display speed dialog (a rather bad idea btw, since it won't affect visual quality, CC3+ automatically uses the right textures based on the current zoom level, manually overriding it just eats performance with no benefit) so the rendering speed is mainly limited by CPU-speed (Actual clock speed is the most important here, not the number of cores) .

Note that since CC3+ is a vector-based program, it will need to re-render your display every time you change view, it is not a finished bitmap just laying ready in memory as with regular image editors. The amount of work needed here depends a lot on your display size, for example a 4K display is 4 times as many pixels as as 1080p one, so it will also be 4 times as slow in that case.

This can only be changed by editing the drawing tool (Or better, make a copy, and edit the copy).

But, the best way to do it is to utilize a proper sheet naming scheme.

Almost all drawing tools look for sheets that STARTS with something in particular, for example, a drawing tool for the outside sheet will be set to draw on OUTSIDE*. That * is a wildcard, and means anything that starts with the text preceding it.

So, if the drawing tool is set to draw on OUTSIDE*, if your current sheet is called OUTSIDE VEGETATION for example, it will happily use that sheet instead of the default outside sheet. On the other hand, if your current sheet do NOT start with OUTSIDE, it will allways go to the default OUTSIDE sheet even if you have others starting with the word.

This same behavior applies to symbols as well.

Something like this?

Here's my competition map from yesterday's live stream. Obviously, as the organizer, I an not eligible for any prizes, but it is still fun to compete. You'll find a higher resolution version in my gallery.

What Wyvern states is correct. That time is to allow it to become March 1st in every time zone.