We are already a good bit into the new year and January, but we still like to take a quick look back at the some of the beautiful maps created by our user community in December.
André Franke created this fantastic map of a hypothetical Antarctica (without the ice) with the help of Fractal Terrain 3, Wilbur and the November Annual issue.
Continue reading »
Colors are important for any CC3+ map. Now, you can make beautiful Black & White maps too, but it would be a bit boring if that was the only option available.
Colors in CC3+ comes in two main flavors. CC3+ has it’s own color palette from which you can pick colors and use for entities you create in CC3+. And then you have the colors used in raster symbols and fills, which are part of the image these are based upon, and which are not changeable inside CC3+ (with the exception of varicolor symbols, but that is a separate topic).
The CC3+ color palette will be the focus of today’s article.
One of the limiting factors with the palette is that it only supports 256 colors, which means that it might not contain the exact colors we want for our map. Fortunately, it is easy to edit the palette. You can bring up the dialog at any time by clicking the color indicator on the status bar, pick one of the existing colors, and hit the Define Color button. This lets us define it as any color in the standard 24-bit color spectrum (over 16 million different colors available). Just remember that if you edit a color, it will affect existing entities in the map, you cannot get around the 256 color limit by first using a color and then changing it. Now, changing the colors are easy, but let us look a bit more a palette-wide options. Continue reading »
In FT3 you can simply change your colour scheme by loading a new one. With some minor limitation this is now also possible for your topographical maps in CC3+. Here are some supporting files:
Exporting coloured topographical maps from FT3 to CC3+
Fractal Terrains 3 (FT3) is a great tool to create new worlds or to visualize our own – earth. Here I will focus on how you can export a topographical map to Campaign Cartographer 3+ (CC3+) and change its style easily.
When you export contour maps from FT3 and CC3+ you usually get the expected results – as long as you use the predefined colours from the built in palette or standard colouring schemes that follow with FT3.
As soon as you start to use non predefined colours in your map the export from FT3 to CC3+ will give unexpected results.
The built-in colour palette in FT3 matches the default palette used in CC3+. As long as you only use the predefined colours when you design your own style for topographical maps, the colours in both FT3 and CC3+ will match. As soon as you start to use your own or blended colours, the result in CC3+ will look different and usually not match your style anymore.
How to use other colour styles
With the November 2019 issue of the Cartographer’s Annual come several very useful and inspiring colour schemes by the artist Sue Daniel. These where actually made for use with Wilbur (another very handy application by Joe Slayton, the creator of Fractal Terrains). She also gives an example of a colour palette for CC3+ that can be used to colourize your imported height contours from FT3. But you have to do it the manual way – one by one.
While you can change the look of your maps completely in FT3 only by loading another colour scheme, you have to colorize each contour again from scratch in CC3+. You also have to adjust the 256-colour palette when you not find your favourite colours that match your style.
This had me thinking about a workaround. There must be a way to skip the manual work of colouring contours and there should be also a possibility to make it much easier to change the
style of your map – just only by changing the colour palette in CC3+ which has become much easier since Profantasy introduced the new command PALLOAD.
Sue used 10 colours for different sea depths and 25 for altitudes. She replaced “unusual” colours in the 256 colour palette of CC3+. Why not expanding those colours ranges was one of my first thoughts. Why shouldn’t I force FT3 to use a certain colour instead of leaving it up to the program itself (trying to find a matching colour)? And how could several colour styles be used without having to export a map several times from FT3?
I decided to use 32 colours for altitudes and 16 for the sea. If you always use colour no. 223 for the lowest land level and no. 192 for the highest one then you make use of exactly 32 colours for altitudes. The same applies when you always use colour number 224 for the sallowest sea and no. 239 for the deepest. This way you use 16 colours for the sea. (Note that I changed the order of colours for altitudes over land compared with Sue’s approach).
If your world is between -32.000 ft and 32.000 ft – what are the needed depths and altitudes to be exported from FT3? If you want to have equidistant high levels then we have 32.000 ft / 32 colours = 1.000 ft / colour (and for the sea 2.000 ft, because we have only 16 colours here).
So in this case you have to set up a Campaign Cartographer Export in FT3 that exports 32 altitude levels from 0 ft to 31.000 ft (32 levels, the last one reaches up to 32.000 ft).
You force FT3 to use colour no. 223 for the first level – 0 ft. For the second level 1.000 ft use no. 222, for the third one no. 221 and so on. Concentrate on the numbers and do not get disturbed by the pink/purple or nearly black colours that you select when setting up the template. Then you generate 16 levels of depth from -32.000 ft to -2.000 ft and force the level -2.000 ft to choose colour no. 224, the next lower level uses no. 225 and so on. This is the most time consuming part of this procedure.
If your world expands from let’s say -4.800 m to 4.800 m you have to define another Export template with 150 m steps for altitudes and 300 m steps for the sea. Unfortunately you cannot change the height levels afterwards. You have to delete existing ones and have to add new ones when you have copied an existing template. Basically you can set up your heights and depths as you wish – as long as you follow the procedure above with exactly 32 levels for the altitude and 16 for the sea.
You may object that setting up an individual export is as time consuming as having to colourize each contour separately. You are right as long as you only want to create a single map and do not want to change the style of it afterwards. Until now there are only quite a few colour palettes available for CC3+ and almost all existing colour schemes in FT3 do not match the above approach with 48 colours.
So my personnel challenge was to create colour palettes that fulfill my requirements and the matching colour palettes for CC3+. With a little programming my PC did this job. And now you can take a look at your exported map. When you still have the default palette loaded it will look like the one on the right! This is not quite the look we wanted – but it is the style we defined in our FT3 to CC3+ export template!
And now to the fun part: Start loading the new specialized colour palettes and see what happens. Download some example color schemes for FT and CC3+ here.
We start by typing PALLOAD into the command line and press enter. We press enter once again – no entry given for the palette name. A file selection dialog opens and you can pick the colour palette of your choice – here I use the one with the same name that I used for my FT3 visualisation. It’s the Wilbur Old Map style – based on an idea by Sue. (Eventually you have to press enter two times again before the effect takes place).
Compared to the original map (generated in FT3) this one exactly matches our style in CC3+. Finally, you can change the style easily only by loading another colour palette – and there are quite a lot to choose from. Your map gets a totally different look in no time…
Here are a couple examples in the Dark Parchment and Arctic styles.
About André alias WeathermanSweden
André has been working as a forecaster southwest of Sweden’s Capital Stockholm for many years. While weather maps were his daily duty he always had a big favour for astronomical and topographical maps as well. He is fascinated by fantasy worlds and loves all the incredible maps presented by the community. Since he has been back to his roots in northern Germany he runs a little campsite together with his parents south of Lübeck. Despite the weather and the stars he is also interested in 3D rendering, photography and nature, where he spends a lot of time with his dog.
This is the third article in my series about XP development. To understand this article properly, you should be familiar with the contents of the previous articles.
When writing commands for CC3+, we frequently need to communicate with the user. This is often in the form of requesting some data from the user, such as where to place a node or which color to use, or we want to provide information to the user, such as instructions on the command line or the information the user requested. In this article, I’ll talk about the Text Formatting & Output Service (FormSt) used to prepare data to display to the user, and the data request format (ReqData). We have been touching both of these briefly in the two prior articles, but it is time to discuss these a bit more in depth.
Update 22 for CC3+ was just released, and in addition to fixing a couple of issues, it also includes some improved commands, as well as a few brand new ones. Let us have a look at these and how you can use them.
A new command for tracing the outline of images (and other CC3+ entities) and turning them into CC3+ entities have been added. This new command, simply called Trace is an easier to use variant of the Contours command from Update 16, and it also support colors.
There are two new commands here, TRACED and TRACE. The former allows you to select entities for tracing, and then it will pop up a dialog where you can set various parameters, while the latter is the silent version which just executes the trace using the current parameters (either set by using the dialog version, otherwise it uses default ones). The options in the dialog are as follows: Continue reading »
Rationale
The method below is to accurately display your FT3 map at any projection as a CC3+ map, with all the climate zones, altitudes and major rivers in their correct places no matter what the projection, and also to allow fine tuning the map in a way designed to add extra detail without changing the original FT3 map to any great degree.
The method requires as much detail in creating the FT3 map as possible – see articles on designing FT3 maps. Especially, this requires attention to altitude, climate zones, islands and rivers.
Prior to export
The most popular projections are:
• Equirectangular – increasingly inaccurate as you travel away from the equator
• Hammer – distorted increasingly as you travel to the east and west borders
• Sinusoidal – accurate and not so distorted, but discontinuous. Can be used to make an actual globe, especially the 18-way Stereographic Gores.
• Orthographic – allows you to centre on the landmass in question and see it most accurately of all in a continuous fashion. Used also to make maps centred on the North or South poles.
• AE Hemispheres – presents the map as 2 hemispheres (E and W). For best results, make your original draft map in FT3 as an AE Hemisphere projection, and then refine it at the equirectangular projection. This enables you to make sure there is not too much land overlapping each hemisphere – see below for preferred (left) and not preferred arrangements (right).
Continue reading »
What is a symbol really?One common way to look at symbols is to separate them into raster and vector symbols, where a raster symbol is a png image file on disk, while a vector symbol is built from regular CC3+ shapes. While there is truth in this, it is also an oversimplification.
If we look at things from the perspective of CC3+, there is no difference between these, it is just a symbol either way, and is treated exactly the same. And all of this becomes evident when we look at what a symbol really is.
If we go back in time, Campaign Cartographer didn’t have symbols at all (at least not as we know them today), it had parts. Put simply, a part is a CC drawing, which you can insert into another drawing. Being an actual drawing, it could contain everything a regular drawing could. It is from this concept of insertable parts that symbols arose. Just as with parts, a symbol is just an ordinary CC drawing that can contain (almost) all the features of a normal drawing. One of the main differences between symbols and parts is that one file can contain many symbols, allowing for the symbol catalogs we use today, while parts must be one file per part. (Also note that a symbol catalog file is just a standard map file with a different file extension, there is no difference in the file format at all.) You know the symbols that show up in the symbol catalog window if you click the Symbols in Map button? Those are the same symbols which would be available to other drawings if you loaded the current map up in the symbol catalog window while working on another map). Another big difference between symbols and parts is that when you use symbols, the symbol definition is stored exactly once in the drawing, and each placement of the symbol in the map just reference that definition, while when you insert a part, the entities in the part are simply being inserted into the drawing each time.
So, where am I going with this? Well, as you probably already know, in CC3+ you can use Draw –> Insert File to insert different things into your drawing, one of the possibilities being an image file in png format. Doing this simply inserts a picture entity into the drawing. A picture entity is one of the standard entities in CC3+, just like a line, a polygon or so on, the difference is obviously that it references an external image on disk. And this is exactly what a raster symbol is, it is a standard symbol that happen to include a picture entity. One interesting fact about how this is done is that you could insert images into your maps all the way back in CC2, so technically you could have raster symbols in CC2, even if it wasn’t officially added until CC3 (CC3 improved the functionality a lot though, such as support for transparency, the png format, variable resolution, varicolor and much more) Continue reading »
Dear map aficionados, it’s time again for our Maps of the Month series, where we highlight just a few of the many contributions to the online CC3+ community. Enjoy!
Christina Trani (Lorelei) posted pictures of her 3D ship plan in action on Facebook and the forum. Isn’t the combination of a flat floorplan with a 3D arrangement just wonderful?
Continue reading »
This is the second article in my series about XP development. To understand this article properly, you should be familiar with the contents of the previous articles.
In this article, we’ll talk about how we can manipulate our drawing. In CC3+, a drawing is really a series of entities, so we are going to have a closer look at what an entity really is, how to create new entities in the map, and how to access and manipulate existing entities.
Everything in a CC3+ map is an entity; a symbol, a line, a landmass and so on. This term should be well known to all CC3+ mappers, as it is the term used in official documentation. However, it isn’t just these visible things that are entities, almost everything stored in a CC3+ drawing is an entity, such as a map note or an effect. We can view an entity as a data container for one specific thing or aspect of our map.
When working on an XP, you are almost always going to be handling entities. After all, manipulating entities is needed no matter what you want to do with the drawing, including extracting information from it, so understanding how to work with these is very important.
Whenever you add a new effect to a map in Campaign Cartographer, you are presented with a small choice about which effect units to use. In these article, I’d like to talk a little bit about these choices, what they really mean, and which setting to pick in each situation.
In general, the effects units affect how you specify effect sizes, such as the width of an edge fade, the length of a shadow and so on. It does not affect the strength of the effect (although changing the size of an effect, such as a glow, will indirectly make it feel stronger as well).
The three available settings are
So, let us look into what the different settings are most appropriate for, along with some examples.
