The Bug Fixes Thread!

[Bobalude]

Description of Bug and how to replicate it: Can't build watchtowers or forts / limited movement. Don't know how to replicate, just happens on some regions.
Probable Cause: Disaster event got stuck or something so the game thinks its still active many turns later.
Suggested Fix: Wait or cause another disaster in the region that clears up correctly.

Working Fix (workaround): Edit the disasters file to force a disaster event to occur, run the saved game for a turn or two so the event happens, save, and revert the disaster file back to the original.

The file is: data\world\maps\base\descr_disasters.txt

Make a copy of the file first, then edit the original and make a copy of the first entry, for earthquake, and delete the "climate" line. Replace that line with "Position" specifying the affected region. You need to lookup the position of the city with the affected region using "show_cursorstat" in the game console with the mouse cursor over the city.

Change min/max scale to 1 to reduce the effects of the disaster, and the year/frequency from 20 to either 1 or 2. I'm playing with 2 turns/year (0.50 time scale), so if you are using the default 2 years per turn, I would try 2 instead of the 1 that I used. These numbers appear to be in years, so with a 0.50 timescale, or 2 turns per year, it takes 2 game turns for it to occur.

Save the file (its read-only so you have to undo that property). Load your game, and run a turn or two. Hopefully an earthquake will properly hit and undo the watchtower/fort bug. Save post-earthquake and then go back and restore the original descr_disasters file.

--------
Lastly, I noticed that this oddly didn't work in the odd game turns using 0.50 timescale. That is if the saved game was during a particular season or 1/2 of a year, the disaster event will never trigger for some reason. Simply go back to a saved game 1 turn earlier seems to fix it. Guessing it only counts properly either every even or odd turn number... or if the game starts at a half year, it never triggers (i.e. year 1110.5).

[Thurak]

Description of Bug and how to replicate it: Can't build watchtowers or forts / limited movement. Don't know how to replicate, just happens on some regions.
Probable Cause: Disaster event got stuck or something so the game thinks its still active many turns later.
Suggested Fix: Wait or cause another disaster in the region that clears up correctly.

Working Fix (workaround): Edit the disasters file to force a disaster event to occur, run the saved game for a turn or two so the event happens, save, and revert the disaster file back to the original.

The file is: data\world\maps\base\descr_disasters.txt

Make a copy of the file first, then edit the original and make a copy of the first entry, for earthquake, and delete the "climate" line. Replace that line with "Position" specifying the affected region. You need to lookup the position of the city with the affected region using "show_cursorstat" in the game console with the mouse cursor over the city.

Change min/max scale to 1 to reduce the effects of the disaster, and the year/frequency from 20 to either 1 or 2. I'm playing with 2 turns/year (0.50 time scale), so if you are using the default 2 years per turn, I would try 2 instead of the 1 that I used. These numbers appear to be in years, so with a 0.50 timescale, or 2 turns per year, it takes 2 game turns for it to occur.

Save the file (its read-only so you have to undo that property). Load your game, and run a turn or two. Hopefully an earthquake will properly hit and undo the watchtower/fort bug. Save post-earthquake and then go back and restore the original descr_disasters file.

--------
Lastly, I noticed that this oddly didn't work in the odd game turns using 0.50 timescale. That is if the saved game was during a particular season or 1/2 of a year, the disaster event will never trigger for some reason. Simply go back to a saved game 1 turn earlier seems to fix it. Guessing it only counts properly either every even or odd turn number... or if the game starts at a half year, it never triggers (i.e. year 1110.5).

I followed those orders some time ago and had the promised success.

But now, I did exactly what I am told to do and no disaster happens.

Does this "bugfix" still work with 1.2?!?

[Whacker]

I followed those orders some time ago and had the promised success.

But now, I did exactly what I am told to do and no disaster happens.

Does this "bugfix" still work with 1.2?!?

I don't know about his comment in for the 0.50 timescale, but it appears that the events are hard-saved into the savegames when you start a new game. I also run at the 0.50 timescale, and have found where the events are stored in the savegame. Changing descr_disasters or whatever it is and then loading up the save game does not change it in any way.

[Shahed]

So you can't get around it ?

[Thurak]

Great. I found another way to get the bug: change the ownership of the province where a disaster strikes and you have this nice low movement/no watchtowers bug.

It very much looks like it... my armies advanced towards Vienna at normal speed and everything was fine. I took the city the next turn and when I started to move around to build some watchtowers the next turn, I noticed the reduced movement. Must have missed it the round before because my army laid siege and did not move. And I got no disaster message as it was not my province at that time.

When I finally noticed the bug my autosave was one turn too new *sigh*


So how can I get rid of those s***id, f***ing, bugged disasters? There must be some way. I´ll test nearly anything, so let´s hear your brilliant ideas



@whacker: As I understand it the idea to change the descr_disasters is to cause another event in the province where the disaster bug occured. With that disaster working and especially ending normally the old, bugged disaster should be neglected. No change at the savegame needed.

[Durallan]

first post in this thread was made in 2006

[Thurak]

If you have any further, more up to date information about the bug where you can't build watchtowers in a province you are welcome.

Unfortunately not only the bug still exists, but the workaround doesn't work anymore in 1.2. *sigh*

[RickooClan]

first post in this thread was made in 2006

Omg......

If we are supposed to talk about bugs post patch 1.02 here then??

Anyway, we need a thread like this to discuss the bugs post 1.02 and try to fix them by the community since very likely 1.02 will be the last patch released by CA.

[RickooClan]

Great. I found another way to get the bug: change the ownership of the province where a disaster strikes and you have this nice low movement/no watchtowers bug.

It very much looks like it... my armies advanced towards Vienna at normal speed and everything was fine. I took the city the next turn and when I started to move around to build some watchtowers the next turn, I noticed the reduced movement. Must have missed it the round before because my army laid siege and did not move. And I got no disaster message as it was not my province at that time.

I have just started a new game with HRE and in turn 11 i realize Vienna was suffered with the flooding bug. The weird thing was i have NEVER receive any message about disaster in Vienna even it is my province right at start.

I would like to ask the modder around if we can disable/deleted the flood disaster by mod before starting a new game? Likely it is the only way to prevent the game from this very annoying bug.

p.s. If this movements points bug only cause by flood or by earthquake as well? If so we might have to disable/deleted both disaster with mod.

[RickooClan]

I followed those orders some time ago and had the promised success.

But now, I did exactly what I am told to do and no disaster happens.

Does this "bugfix" still work with 1.2?!?

I think the workaround for that disaster bug no longer works in 1.2.