A batch of great maps from @Quenten . This includes his contest entry, which means all contest maps are now in the atlas. I've also updated the contest page on the atlas site, and handed out the forum badges to the contest winners, so everything should be up to date.

As far as I know, the only thing currently in my backlog is a set of maps from @Wyvern . Everything else is either processed and added to the atlas, or I have gotten back to you requesting some kind of correction or information from you. So, if you are NOT Wyvern, but still miss me adding something you've sent me, please notify me immediately, as that means I've overlooked something. People send me maps multiple ways, as attachments to forum posts both in this common thread and in individual threads, as email and as forum PM's, so it isn't always easy keeping track of everything. I do always post in the forum when adding new maps, either in this thread, or in the WIP thread for that map, so if you haven't noticed me posting about adding your map, it might be wise to check the atlas.

Anyway, here's Quenten's new maps

Being done with the contest maps (except Quentens, if I forgot anyone else, please notify me as that is an oversight, not deliberate) it is time to move on with the rest of my queue.

So, today's map is Lorelei's excellent Timberline map. Thanks for contributing.

Feel free to post wishes. It is always nice to know what the community thinks and wants. Please do be aware that some wishes may not be feasible due to technical limitations, so popularity here doesn't necessarily mean it will be implemented, and for the same reasons, not implementing a suggestion doesn't mean you are ignored.

ProFantasy staff, including the main developer, do read these boards, so suggestions will certainly be noticed when posted here.

Because of memory restrictions, CC3+ cannot compute the entire export image in one go, but must do it in parts. This is what you see when CC3+ reports that it is on Pass X of Y in the export progress dialog. Unfortunately, this also means that it can't include effects originating from entities outside the export area of the current pass (if it could, it wouldn't be necessary to split it into passes in the first place)

However, the default setting is quite conservative to allow machines with even a very low memory to export high resolution images, and this leads to many passes, which both leads to a bigger chance of effects being cut off this way, as well as the export taking quite a bit more time.

You can change the size of each rendering pass by typing in EXPORTSETMPPP on the command line and hitting enter. CC3+ will then prompt you (on the command line) for the new setting, with the old setting being displayed in square brackets. The exact number you can use here depends a bit on your computer and the complexity of the map, but 40000000 is good settings for almost every computer. Just type in this number on the command line and hit enter to set it (Make sure to use the right number of zeros). Note that it is unlikely that you can go far beyond 40000000 on any computer, no matter the amount of memory. I've been able to use 60000000 in some cases, but not consistently.

With this setting increased, you'll find that CC3+ uses far fewer passes. A map that used 40 passes before will now use around 4 passes instead, which is both much faster, and much less likely to interfere with effects.

This setting is permanent, so you only have to set it once, and CC3+ will remember it for the future. If you have any problems, you can just run the command again and set a lower value. 4000000 is the default. Also note that this setting do require that CC3+ gets allocated a contiguous range of memory from your computer, so if CC3+ starts telling you that there are not enough memory for export while using a value for this setting that has worked in the past setting this, a simple restart of CC3+ and/or your computer will usually help. If not, try a lower number, like 20000000 which is still much higher than the default.

🎬️ Videos: Autosave

If you don't like that autosave prompt popping up all the time while you work, it may be tempting to just hit the disable autosave button. But don't do that. You can still have autosaves without the prompt. Just right click the :CC2SAVE: button and pick Autosave, and you can control the frequency of the save as well as turning off the prompt.

Keep in mind that there are only a single autosave file shared between drawings, so if you have a crash, you should immediately open the autosave file (Open Autosave Drawing from the file menu) and then use Save As to save it under a new name.