Yes, all three members of this family have been updated. From developer's point of view the main feature of this update is changes in the JSON format, which is used to exchange data between the generators and the viewer. But it doesn't affect most of the users, so I'll comment on it in the end of this post. What else is changed?
- On the image above you may notice that buildings on the outskirts of the city look differently from the buildings in the central parts. For their placement within a block I use a new algorithm similar to the one in Village Generator. The con is that they are placed more sparsely, which is probably OK for semi-rural areas. The pro is that they all are proper rectangles. We'll see how it works.
- A separate colour can be used now for roads. In all the built-in palettes a "paper" colour is used as a road colour, but in a custom palette you can specify a different value. On the image above roads (along with bridges and squares) are lighter than the background (link to the palette).
- District names are now editable right in the legend box. So if you use the legend, there is no need now to disable it, edit names and enable again.
- City Viewer now supports a number of small features of MFCG which weren't supported before: piers, small bridges, monuments, water gates. You won't see them in the sample cities since the sample files don't contain required data (I'll update those samples later).
- Some elements have been fixed/improved - roads, squares, coastal castles etc.
- Square towers are added as an option. Tower shape is one of the "environmental" parameters, so, for example, "midlands" towers (5) are always round and "desert" towers (6) are always square.
- Random setting (Shift+0) are improved but still mostly ugly.
Apart from really small layout improvements the only change is the addition of basic JSON export, so it's now possible to view a generated village in 3D. The main problem with it is that there is literally nothing beyond the map borders and in 3D it doesn't look good - roads, waterbodies end right where the original map ends. In the future I hope to find a way to extend them visually without additional generation.
Another shortcoming of the current JSON export is that height-maps are not exported. Of course, it's not hard to export them, but they are not yet supported in City Viewer. When they are implemented, they should greatly improve the quality of the final image.
Changes in JSON
If you don't load exported settlements in your own applications, this shouldn't affect you and you can safely skip the next paragraph.
I finally decided to move away from the strict GeoJSON format. I mentioned before that I found it too rigid, too limiting and overall awkward. For now the changes are minimal: there are still the same object types, points are still two-element arrays etc. I'm not going to list what exactly has changed, you'll see it yourself. In the future I'm going to change many things and I hope in the end it will be more comfortable to use not only for me.
The next generator to update is ⚔️One Page Dungeon Generator!