For this past 6 weeks I have been working part time on a personal CIV like game with all the features that I wish the latest entry had. As important as whatever I have done is what I have learned in the process, which made me appreciate even more the work the Firaxis team have put into the game. So here is a list of discoveries I have made during this process (by passing through the exact same problems):
1. The scale of the game is not really defined by the artists, but by modern hardware (and the choice of going full 3D).
Say you find things too big on the map. Maybe it would be better to scale everything by 0.5x so more stuff can fit in the map, thus making forests more realistic, reducing city sprawl (now we don't need that many hexes for cities, do we?) and at the same time making them more realistic. Well, this implies 4x the amount of objects on the scene, triangle count, GPU operations... If the game doesn't run at 240 FPS on your machine, thank the Firaxis team for not making the scale smaller. Of course ealier games (and the other new series I shall not name) don't directly have this problem because not everything in them is 3D. Just painting a texture is relatively cheap compared to have dozens of high quality trees in the same tile.
2. Having everything 3D is a necessity
This may look like it contradicts the previous paragraph. It doesn't, because CIV VI and CIV VII have a lot of camera freedom (for example, wonder animation). If you give the player this amount of camera freedom you can't foresee from where they are going to see stuff. Anything strictly 2D is going to stand out from the wrong angle and look bad.
3. Rivers in tiles are as much of a feature as a necessity
You build beatiful cities, they spraw seamlessly as an uniform unity. Every district format is hand made and every building is carefully crafted. Then you remember there are rivers passing by the edges of hexagons 😖. Now you got to handle this: maybe never put an important building / building placement close to the edge and figure out some way to connect hexes with a river in the middle and call it a day! What if rivers are realistic and don't precisely follow the edge? Now what can you guarantee exactly about where you can place buildings and what buildings can fit in dry land? Maybe for a single river you can guarantee you have some area, but what about two rivers passing by a hex and joining at some point (taking 4 of the 6 edges of a hex)? Now you can't even guarantee a wonder such as the pyramids is going to fit in the hex without making the rivers look ugly. It's better to just put the rivers in the middle of hexes and then every other land hex is guaranteed to have full land on it (as long as you make coasts not go into land tiles, which is the case). Then hexes with rivers are an edge case you can manage individually.
4. City Sprawl is here to stay, unless you don't like wonders (or graphics)
In short, due to the scale of the game as said in #1, if you want wonders appearing on the map (which has been the case since CIV IV) they will inevitably take a significant area. Having only wonders taking tiles would be super weird, as a city would be a single tile surrounded by magnificent buildings (possibly none). So having the cities sprawl is as much of a necessity as it is the only option for cities not to look odd (and given points #1 and #2).
Wait, but CIV IV was 3D, had good scale, showed wonders and didn't have city sprawl! Well, compare CIV IV graphics to CIV VII. Each object in the latest entry has far more triangles to render. So yeah, you can have all that, as long as you are accepting CIV IV graphics (it could be a bit better as hardware has evolved, actually; Also I believe this was one of the reasons for reduced map size from CIV III to IV).
5. Why don't they build the game over a globe, instead of a 2d map?
Before someone says it's impossible to tile a sphere with hexagons, one can get very very close using this:
https://en.wikipedia.org/wiki/Goldberg_polyhedron
Of course this raises a bunch of problems:
- What do we do with the pentagons? Do we have to model everything twice in case somebody builds over one of those 12 tiles?
- The tiles deform (e.g. hexagons close to pentagons have their angles very distorted)! What do we do now? Do the buildings on top deform as well and proceed to look terrible?
- Do we re-calculate shadows every single time the player moves the camera? It's going to tank performance, as those shadow maps are costly!
One could say: "just use procedural generation, bro". Well, I dare you to write an algorithm to procedurally generate cities that look good on terrain with very little guarantees below it. Good luck!
Anyway, can any of the devs confirm those claims here? I'd be very happy to know how close I got haha