And @Lizzy_Maracuja provides her great city map to the atlas:

It really only matters if you wish to distribute your XP. The reason for sticking with the same version as CC3+ itself uses is that users are guaranteed to have the correct libraries installed. I do believe that Joe switched over to VS 2019 for newer builds anyway, and later versions of the installable runtimes actually provide support for all newer versions, making it matter even less, so you should be able to just use the 2022 toolset without issues.

That said, to install the additional toolsets, all you have to do is to go back into the visual studio installer and modifying your installation, and under the C++ desktop development you can install the MSVC 1.42 for 2019 support, and MSVC 1.41 for 2017 support. You can see these options in my screenshot above, in the list to the far right of the dialog...

I should update that article with 2022 now being the current version. There are no real differences, but it can be annoying when the steps in the article doesn't match up 100% with the actual product. Everything when it comes to the actual code in the tutorials will be 100% identical though, it's just some minor changes to the setup.

Hi @Ricko Hasche, please let me know when you are done with these, I can't start adding them to the atlas until I know you're done tinkering with them. I've added your other two threads.

I love your maps, and you've done a good job keeping things to correct scale and everything else in order making it easy for me to add them to the atlas. Not everyones maps have been this easy to add. I have two small requests for future maps though:

• Naming: Several of your maps are named something because you have a city symbol in the middle of the map bearing that name. This is a bit of a problem, because is someone is going to map that city later, their map should be named for the city name itself, the area map containing the city symbol should have a name based on the area (you've been pretty good at filling up your maps with names, so I am sure you can make up a name for the area too). An example of this is your Bughole map, but Bughole here is just a small place on the map, the map itself shouldn't be named for this. If you can't come up with a good area name, a name like Bughole environs or similar can also work. Also, it is easier for me if the filename is the proper map name, no numbering in the front, and no replacing spaces with underscores or the like
• Lots of your maps have entities sticking out beyond the screen. This looks very bad in the atlas when people see the actual fcw file, so I always fix this, but it would make things quicker for me if this was already fixed. The COLLARDEL and COLLARAUTO commands are great ways of fixing this quickly.

Finally, new Atlas contributor @Ricko Hasche has provided a large collection of maps, and is still working on more. Welcome to the atlas, and thanks for contributing.

And @Wyvern is continuing his work detailing the northwestern regions of Alarius: