Jackson
02-15-2001, 00:13
Is this a Bug?
I’m in the final stages of a Shimazu campaign, and Uesugi is the last rival clan alive. I decided to try some subterfuge in one of his production provinces and moved about 15 shinobi into it. I saved the game, and on the next turn the province revolted, and a ronin army appeared in it. However, I could not click on the ronin unit. It was as if it wasn’t there. I saved the game again, but when I returned to the strategic map the ronin unit was gone! This happened for several turns, without the ronin unit ever fully appearing, or the province’s buildings being destroyed.
Finally, I tried continuing the game without saving, and eventually (after about three turns) the ronin army did stick. The problems with not saving a campaign between turns are numorous, not the least of which are crashes that occur after several battles have been fought, thus forcing me to fight all of them over again from the point where the game was last auto-saved.
Is this a bug? Has anyone else run into this problem? Is there a work-around? BTW, I'm playing v1.12.
I’m in the final stages of a Shimazu campaign, and Uesugi is the last rival clan alive. I decided to try some subterfuge in one of his production provinces and moved about 15 shinobi into it. I saved the game, and on the next turn the province revolted, and a ronin army appeared in it. However, I could not click on the ronin unit. It was as if it wasn’t there. I saved the game again, but when I returned to the strategic map the ronin unit was gone! This happened for several turns, without the ronin unit ever fully appearing, or the province’s buildings being destroyed.
Finally, I tried continuing the game without saving, and eventually (after about three turns) the ronin army did stick. The problems with not saving a campaign between turns are numorous, not the least of which are crashes that occur after several battles have been fought, thus forcing me to fight all of them over again from the point where the game was last auto-saved.
Is this a bug? Has anyone else run into this problem? Is there a work-around? BTW, I'm playing v1.12.