Single Player bugs and crashes - After the 16th of May

Just wanted to mention again about the listings of double units when a finished unit is over and then asking for another unit to be built, sometimes lists as much as 3-4 times for certain of SAME unit??????

Also building are doing the same when BUILT??? (In same town:crazyeye:) see attached??
 
Also building are doing the same when BUILT??? (In same town:crazyeye:) see attached??

Is the number of entries in the log the same as the number of threads for city production in the XML by chance? (I think you asked where the number of threads can be increased?)
 
Just wanted to mention again about the listings of double units when a finished unit is over and then asking for another unit to be built, sometimes lists as much as 3-4 times for certain of SAME unit??????

Also building are doing the same when BUILT??? (In same town:crazyeye:) see attached??

Did it actually build several things in a multi-production turn and just log the first one each time?
 
Is the number of entries in the log the same as the number of threads for city production in the XML by chance? (I think you asked where the number of threads can be increased?)

Nope i changed it back to 2 because of all the problems C2C is presently having:sad:

Did it actually build several things in a multi-production turn and just log the first one each time?

Dont know, i didnt look at the buildings being built, i just go by what it says.
 
I missed that sorry, here goes:

OK in the far left top city of mine, the one with a rebellion, i open the city (double clicking on it) i want to test if the turn times change, so i click on the city governor, then i TRY to click on the production ALSO (so both would be ON., but a CTD happens right away. I hope this explains it better.

Can't reproduce this - selecting them both causes no problems when I try
 
Setting odds on the hunt automation does not always insure that all attacks will be at those odds or better.

I have the odds set at 80%. Click on the Cree Tracker, tell him to hunt, and he will attack the axeman even though the odds of that attack are 52%.

I'm sure I've asked you this before (sorry - I ask so many people that I don't always remember the answers), but V30 or SVN? For me he doesn't attack the axeman when I load your game and set the odds threshold to 80%, but I can readily believe he did with V30 (I fixed some odds calculation bugs a couple of weeks ago).

HOWEVER, he does with the odds set to 75%, and digging in I found a rather dubious calculation within the AI odds calculator, which I have adjusted to hopefully be more accurate (it was incorrectly assessing the odds at 78%, which changes to 55% after the adjustment I made [it still suffers a slight rounding error which is why its a few points higher than it probably should be]).

Fix for this will be on the SVN later today.
 
I just build my second city. Now when I click on the Go to City button, I have a CTD, every time.
V30 no SVN.

I tried this on the current build and it reproduces. I now understand it (it's a bug in the goto city code itself) - a fix will be on the SVN later today.
 
The one listed back here: It was a great game. . . SO

http://forums.civfanatics.com/showpost.php?p=12491757&postcount=218

Also on the Polynesian one, did you try the Revolting city ONLY, cause the others work ok.

Yes, the revolting city in the far north was the one I tried.

Edit - just tried the other CTD (Cherokee save). Loaded and immediately pressed end turn. Turn completed fine (latest SVN, both DLL an assets) - is there something else I should be trying?

It did reproduce the repeated build logs though, so I'll use it to look into that...
 
Yes, the revolting city in the far north was the one I tried.

Edit - just tried the other CTD (Cherokee save). Loaded and immediately pressed end turn. Turn completed fine (latest SVN, both DLL an assets) - is there something else I should be trying?

It did reproduce the repeated build logs though, so I'll use it to look into that...

I have ALL the logs zipped if you need them from me, they are five savedgames full. HUH, i think then maybe, and to come to think of it, might be in moving the Pipeline from 2 to 6?? I just tried the one and the Governor works now at 2??

http://www.gamefront.com/files/23378235/Logs.zip
 
I very, very much doubt the governor thing is anything to do with the threading, given when the CTD occurs.

Anyway, I've fixed your repeated production of the same building issue (pushing to SVN now). In the course of another related test I just managed to reproduce the governor crash also (on one of DH's saves as it happens, not yours). I'm about to go out, so it won't be until tomorrow afternoon that I get to look into that, but at least I have a case that reproduces it now, so I'm sure it won't be hard to find.
 
I'm sure I've asked you this before (sorry - I ask so many people that I don't always remember the answers), but V30 or SVN? For me he doesn't attack the axeman when I load your game and set the odds threshold to 80%, but I can readily believe he did with V30 (I fixed some odds calculation bugs a couple of weeks ago).

HOWEVER, he does with the odds set to 75%, and digging in I found a rather dubious calculation within the AI odds calculator, which I have adjusted to hopefully be more accurate (it was incorrectly assessing the odds at 78%, which changes to 55% after the adjustment I made [it still suffers a slight rounding error which is why its a few points higher than it probably should be]).

Fix for this will be on the SVN later today.

This is V30 no SVN. The only time I check it is when a unit dies attacking something, I look at the combat results. Sometimes the odds are correct, 80%+ but some have been as low as 19%. There are check boxes for allow unit suicide, but that is clear. Can there be added another check box for attack Animal Class only? That will clear this up, as it is only when attacking 2 legged barbs that the odds drop.
 
In the course of another related test I just managed to reproduce the governor crash also (on one of DH's saves as it happens, not yours). I'm about to go out, so it won't be until tomorrow afternoon that I get to look into that, but at least I have a case that reproduces it now, so I'm sure it won't be hard to find.

:whew: Starting to sound like my ADHD was acting up again.:crazyeye:
 
This is V30 no SVN. The only time I check it is when a unit dies attacking something, I look at the combat results. Sometimes the odds are correct, 80%+ but some have been as low as 19%. There are check boxes for allow unit suicide, but that is clear. Can there be added another check box for attack Animal Class only? That will clear this up, as it is only when attacking 2 legged barbs that the odds drop.

Wel, I think I've fixed it now, so it shouldn't really need a workaround option, though I do agree with you that (independently of any misinterpretation of odds) an option to restrict hunting to animals wold be useful.
 
urgent! i found a problem, when i put a city to generate gold or knowledge, the city are doubling the bonus. The showed value is right, but when pass the turn i got double gold or double knowledge.
 
I have found out where the "<\link>" bits in the BUG pages are coming from. They are there to make the pedia work well. So that when you look at what a unit can do you can click on them and open the relevant improvement in the pedia. This is a very good use for them. What needs to happen is that the "link" and "end link" need to be stripped out of those texts when it is being used in BUG.

The reason it was so difficult to find was because in BUG it is displayed as </link> whereas in the text files it is [\LINK].
 
urgent! i found a problem, when i put a city to generate gold or knowledge, the city are doubling the bonus. The showed value is right, but when pass the turn i got double gold or double knowledge.

It might be that the boni the city shows to provide are different to the actual benefits in the end because of non-city-specific general civic boni which are adding up after the results of the cities have been summed up.
 
Back
Top Bottom