Your maps are now in the atlas. Thanks for the contribution Jim.

But for the future, can I ask you to be a bit more inventive with the map names. I am pretty sure the people who lives there do have names for their areas, and especially just incrementing a number really looks weird in an atlas when going between areas of different scales. People love to put names on places, I would very much like to see the regional maps named for a more interesting atlas. Be creative, that's what the people who live there is, they just pick a nice name, doesn't have to be based on the name of other things in the area. I am sure people prefer to live in the place named Grayline Hills rather than River Watch Environs 02. The map name will show up as the name of the entire area it depicts in the atlas, which is why this name is important, and not just locations inside that area that appears on the map.

If you followed my instructions above for finding the path, all you need to do is to move them so they match that path. I am guessing you just have an extra folder or missing one.

As an alternative, you can also extract the source zip again according to the instructions in the installation guide. Each of the four sets from vintiry comes with a rather detailed one.

Well, there can never be enough tutorials, but it is described in the Manual, which is a tutorial for the program. I know some people prefer videos instead of written word (that still boggles my mind, really), but videos do take time and effort to make (and are also way more difficult to keep up to date compared to written text). I do make video tutorials, but it is difficult to get to everything.

In reference to the small buttons, you know you can change their size from :TOOLSICON:?

The issue that occurs here is that because of memory constraints, CC3+ cannot compute the entire high-resolution map in memory at the same time for the export, which is why it exports in multiple passes, each pass rendering a part of the map.

Unfortunately, effects from entities outside of the current rendering part won't be considered, such as shadows from entities far away. There is a certain overlap to handle the closer but right outside things, but considering effects from everything in the map is impossible due to the aforementioned resource problem.

However, you can change the default size of these render chunks, causing CC3+ to render much more of the map in one go. This is done by typing in EXPORTSETMPPP on the CC3+ command line and hitting enter. The command line will then ask for the number of pixles, type in the value 40000000 (The current value, shown in brackets is probably 4000000, keep your zeroes straight). and hit enter. Depending on your export resolution, you will export the map in much fewer passes, perhaps even just a single pass.

Note that if this isn't enough, the other solution is to either consider using shorter shadows, avoiding the problem, or manually creating them using a partially transparent polygon.