C3C Patch 1.20 Bug Thread

[Jerh9e1k5]

Hello, The last patch I have installed was the BETA one. (I can't recall the number right now)

If I want to install this new patch must I uninstall the BETA one first? If so, how would I do that?

I have heard many complaints and problems so far in this thread. I realise that with 1.22 if fixes some of these but there still seem to be problems. Would it be wise not to install either of these two patches?

Thank you for your replies, Jerh9e1k5

[player1]

1.22 runs fine for me.

[vmxa1]

122 needs 120, but I don't think it needs any others. This should mean that any patches prior to 120 should be fine.

[jshelr]

We just arrived in the industrial era about 20 turns ago and all of a sudden my friend Joan has more than 11,000 gold.

I don't like the look of it. This was 1.20 version.

[vmxa1]

Was she able to account for this via trades and income or is it a glitch?

[jshelr]

I never call something a glitch because Alexman then posts on why it's my dumb mistake but it looks like a glitch to me. If anyone else runs into this wierd gold buildup, then we will suspect the return of something like the former gold bug.

[alexman]

Yes, don't you dare call something a glitch without my conscent!



Seriously, how can it be the old gpt bug, if Joan got 11,000 'all of a sudden'? I don't suppose you have a save from the turn before she got rich, do you?

[LordEd]

seed-1984, large/huge, 80% water, pangaea bug

I have noticed a strange possible coding bug with the map generation system.

I have only found it with one particular seed, but it may represent a flaw of some sort in the algorithm used to code the coastline.

Generating a map with the following parameters gives rise to the peculiarity:
80% Ocean
Pangaea
Huge/Large
seed 1984

The map generated is clearly not a pangaea, instead appearing to be more like an archipeligo. The remaining parameters (age/climate/temperature) have no effect on the coastline and resulting land-shape.

I would have discarded this as an random occurance at the 1984 seed, however i noticed something else that was peculiar. When I generated a map with the same parameters (80% Ocean/Pangaea) on a tiny, small, or standard sized map, an acceptable pangaea map was generated. So far for every other seed (and i have checked hundreds of seeds) the basic coastline was the same for every size of the map (assuming the ocean coverage and land form were held constant). A hypothetical crescent-shaped pangaea on tiny would remain a crescent-shaped pangaea on huge, albeit a much more detailed crescent-shaped pangaea.

Here the coastline is vastly different for the tiny/small/standard vs the large/huge maps. I present this information out of a hope that it might help firaxis with improving map generation (since i obviously have no access to the source code I cannot check to see if there is a 1984 seed flaw in the map generation algorithm).

[DrGerry]

Sorry, but I'm not so good in eglish and it was an effort to me to read all the posts in this thread.

The questions are: can we use the 1.22 patch without trouble or is better to wait a little?

What about the 1.25 patch? Is real?

Thanks

[Wittlich]

I haven't heard of a v1.25 patch...

[vmxa1]

It seems no nasty stuff is flying around with 1.22, but you will no be able to load previous saves.

It is believed that 1.25 or some such is planned.

[Wittlich]

Ah... Thanks for the clearification vmxa.

[player1]

I think that some of the posters accidentaly said number 1.25 in order to represent next full patch and then rumors started to fly (since noone officialy ever sad anything similar).

Fact:
-there is no such thing as 1.25
-but there is full version of 1.22 now

[Alex]

it seems that there will be a new patch (a *final* one, not a beta), but it has been delayed for quite some time yet, as is stated in the official civ3 site.

[jshelr]

"Seriously, how can it be the old gpt bug, if Joan got 11,000 'all of a sudden'? I don't suppose you have a save from the turn before she got rich, do you?"

No saves. This was a game started on 1.15 and moved to 1.20. Hopefully, it just turns out to be a freak.