Open devolution79 opened 1 year ago
Update: It was a fort that completed on a previously forested taiga plot
devolution AD-1639-visibility-assert.zip
Step to reproduce:
Wait for the fort on plot (7,12) 2 plots south of Salem to complete. (Add extra pioneers from WB if impatient) and the assertion will trigger upon completion
Build 41280e1
Years ago we had a bug where storms could leave plots behind, which were no longer covered by fog of war. I fixed that and added code to recalculate the visibility cache on load as that fixed all existing savegames and would allow xml changes in existing games. Since this bug is this close to my code, I decided to self assign to this bug.
Assert Failed
File: DLLSources.\CvPlot.cpp Line: 7550 Func: CvPlot::changeVisibilityCount Expression: getVisibilityCount(eTeam) >= 0 Message:
The argument iChange was -1 so the issue is the the visibility turning negative somehow!
It appears that the completion of a build caused a feature to be cleared and the assertion to trigger. Could it be related to fort / monastery completion on a previously forested plot ? (eBuild = 29)