But instead of different named men you can simply have a number of how advanced and how civilized they are:

Your civ is 5 points advanced and 3 points civilized
the local tribe is maybe 1 point advanced and 5 points civilized. The difference from each number is calculated to measure not only how good/bad conscripts they will be but also how your different people will feel for each other. In this case the difference is (3-1)+(5-3)=2+2=4.

How's life, the universe, and everything.

I agree about the Unit Workshop, what was the point in leaving that out Firaxis!

However, perhaps in your city view you would have Youngsons manager screens with which you would sort a group of, say 200,000 men into an Infantry corps, or army, or division, although something that large would normally be an army group. It was the size of the German 6th Army which got trapped at Stalingrad.

MD's unit workshop components need fleshing out (to put it mildly, it's still in a pretty primitive state), and it looks like you've done some very impressive work here.

Of course, you designed this for Civ, which MD is not. As such, some of the concepts don't work under our system. But a lot of them will. And it would need to be expanded in directions you don't have to accomodate our different combat systems. But that could all be handled in due course.

I only have looked over it very briefly. If you have objections to me looking at it, I won't touch it again. But if you do not, I'd like to examine it in a more detailed fasion, with an eye to adapting it for our needs.

Let me know if it's okay with you. Since they aren't going to use it for CivIII, it'd be a shame for all this work to go to waste, heh.

quote: Let me know if it's okay with you.

It's alright Ron. no objection. Good luck.

If we end up using significant parts of it, I will, of course, give credit where it is due on the credits screen.

quote: Originally posted by Urban Ranger on 02-24-2001 07:51 AM By the way, what is MD?

D'oh! Doesn't everyone know this by now?

MD is "Manifest Destiny - The Race for World Domination".

It's a game in the same genre of Civ, though it's not a clone (and therefore has some very basic differences). The major changes from civ are:

A) It takes place on a true spherical world.
B) It has a unit workshop
C) The combat system is much more extensive than Civ (ie it's not just two units bumping into each other and one unit survives).

There are a bunch of other differences, but those are the big ones, I suppose. You can get more information by going to the Alt-Civ section here at Apolyton, or by checking my web page (address in my profile).

The game has been in development for about three years now, and is getting relatively close to being done. We currently have a playable Alpha release in public circulation right now, as long as you are willing to accept a lot of prototype graphics, and no combat system (yet). Oh, and multiplayer only. The computer player AI isn't working yet, so you really can't play by yourself at this point.

We spent the better part of nine or ten months just working on the spherical world (how to represent it in memory, how to display it, how to allow the player to manipulate the maps, etc.). I tried various methods for tiling a sphere, and getting it to display properly, and (most difficultly) getting it to scroll without visible distortions showing up on the playfield.

We finally ended up using Direct3D to display the sphere, which is nothing more than a ball shaped skeleton, and then pasted the terrain texture over the top of it. The tricky bit with the terrain texture is that textures need to be represented in memory as rectangular. But, as you know, you can't wrap a sphere with a rectangle without distorting it. It turns out that when you do such a wrap, you get the exact opposite distortions that a mercator projection causes. Those bits near the top and bottom of the rectangle shrink horizontally when applied to the sphere. Our first attempts at this wrap didn't look very good, because it appeared that land masses compressed as they moved south to north, or north to south. The solution, which took some time to program, was to deliberately distort the rectangular texture picture so that the land masses expanded horizontally as they moved toward a pole (just like a mercator projection does). Then, when wrapped back onto a sphere, they would distort back to the original shape, and look alright on the globe.

Another thing that causes me lots of headaches is path finding. Of course, the textures representations are rectangular, and it is natural to look at them when trying to find the best path. The problem is that when you draw a straight line on a rectangular texture (from point A to point B), and then translate that to a sphere, it curves. Player stacks will spiral toward the poles rather than move straight to them. In order to get a straight line on the sphere, you have to first translate the coordinates of your points into a polar coordinate system and examine all your terrains from there. We still have problems with that phenomonon, though they are not as bad as they used to be.

The game would have been a lot easier to work with and have been done a lot sooner if we had stuck with a regular flat map, and I can certainly understand why game designers don't want to mess with spherical ones. But I decided we had to have a spherical world, and I can be stubborn once I've decided something is needed