Anonymous | Login | 2024-11-22 01:33 UTC |
My View | View Issues | Change Log | Roadmap |
View Revisions: Issue #1259 | [ Back to Issue ] | ||
Summary | 0001259: AI crashes when trying to find visitable offset | ||
Revision | 2013-04-24 05:31 by Warmonger | ||
Description | After recent changes which removed other bugs, now I get only one bug during long AI runs. Debugger claims access violation in this function: int3 CGObjectInstance::getVisitableOffset() const { for(int y = 0; y < 6; y++) for (int x = 0; x < 8; x++) if((defInfo->visitMap[5-y] >> x) & 1) return int3(x,y,0); logGlobal->warnStream() << "Warning: getVisitableOffset called on non-visitable obj!"; return int3(-1,-1,-1); } Looks like visitMap size is innapriopriate. It happens on any of random tests maps I used so far, so no new objects (towns, dwellings) are present. |
||
Revision | 2013-04-24 05:43 by Warmonger | ||
Description | After recent changes which removed other bugs, now I get only one bug during long AI runs. Debugger claims access violation in this function: int3 CGObjectInstance::getVisitableOffset() const { for(int y = 0; y < 6; y++) for (int x = 0; x < 8; x++) if((defInfo->visitMap[5-y] >> x) & 1) return int3(x,y,0); logGlobal->warnStream() << "Warning: getVisitableOffset called on non-visitable obj!"; return int3(-1,-1,-1); } Looks like visitMap size is innapriopriate. It happens on any of random tests maps I used so far, so no new objects (towns, dwellings) should be present. |
Copyright © 2000 - 2024 MantisBT Team |