Anyone else have problems with the game turn not ending in the 1800's? This is two people at the moment. I've played and passed the 1800's so it's not a universal thing.
I'm going to compare the two saves see if I can find anything. If anyone else experienced this a save will help (even better a save the turn before it happened then the earliest auto before that).
Thanks, hopefully this will be fixed for my patch
Back home
Was able to reload my game, and I deleted all privateers (I think 3 of them were on the board) -- was able to get past the game stall and on to the next turn.
Here are the save files:
View attachment 194217
View attachment 194218
(and yes, I know, I am getting my rear kicked here...not one of my best games)
I will likely continue on this afternoon -- but interesting that removing privateers unlocks the freeze.
Also, here is the earliest autosave (about 10 turns before the freeze up)
View attachment 194219
g
Thank you that will help a lot!
So the problem seems to be linked to the hidden nationality units. I changed Tesla's Ray to work completely different in the next patch so if it was that then that shouldn't be a problem with the patch. Besides that I'm not sure. I didn't change that unit at all. Tesla's Ray was the only thing that could affect it (if there was something which I'm still not sure there was between its effect and hidden nationality).
I'll study these new saves and get back to everyone.
In the meantime I would suggest people go into the UnitInfos XML, change the privateer cost to -1, and then reload the mod. This will disable privateers for the moment (you'll need to delete the ones in play off the worldbuilder) so you can continue playing - also see if the error comes up again. Hopefully I'll have this fixed.
I'll do that and continue my game to see what happens. A lot of privateers are being built at present.....about to continue my game.
g
Okay, using the upcoming patch I was able to get into the future era and finish a game yesterday without a single CTD, python exception, or stall.
This doesn't mean that everything is fixed of course, since I still can't identify the exact cause of the stall in the first place. I implanted in the code however checks for every idea we came up with on the forums and stuff I noticed while playing.
I want to do another game and check the saves that were sent to me today, and if both of those go well I'll put the patch up, say by Monday, so other people can test it besides me.
I read about this mod, downloaded it a week ago and am trying to get it started, but I have a weird error : never had this before (see bmp)!!
I have no probelm playing RoM, HiTM, Overlord2, etc by the way
Do I need a new BTS version (I play 3.17 now)
Please help me![]()
I noticed another problem this evening, although this one may be due to my system specs:
Casimir (Poland) and Hitler (Germany) have blank Civilopedia entries (the entry is selectable, but it's just empty text boxes), the game locks up if they are selected in 'Play Now,' they have blank descriptions if selected in 'Custom Game' as the player's side, and the game locks up going to the diplomacy screen if they appear as opponents.
There are minor visual glitches with other leader portraits - Gustavus Adolphus (Sweden) is transparent save for his teeth, eyes and clothes, for example - but only Casimir and Hitler seem to affect gameplay.
It's strange that you experience that error only for my mod but RoM, etc all work fine as the error is referring to something not related specifically to my mod. I can only guess the fact that I'm using some colonization assets could perhaps be the cause. You can try deleting the Custom UI I use (delete the Resource folder in Thomas' War/ and the artdefines_misc XML file in Thomas' War/Assets/XML/Art/ ) Additionally, researching your problem on the forums it seems some people have experienced this for unmodded BTS and playing on a different screen resolution setting allowed it to start. Again, it's weird that this type of problem is only affecting your loading of my mod and not all of BTS for you. I'll see what else I can find out...