Closed DizzyEggg closed 7 months ago
It's too bad they didn't have a single point of reference for gWindows
, it'd be nice to do this kind of check there (because I wouldn't be surprised if there are some other places this is happening quietly). But by my count there's 23 functions that access gWindows
with an arbitrary window id, so this is definitely the less intrusive fix.
Followup to #1976
We found the cause of the glitching map graphics. It was
GetMapNamePopUpWindowId
passing 0xFF as valid windowId, which in turn modifies the data directly belowgWindows
, which happened to begHeap
on some compiler/linker versions. In vanilla this goes unnoticed.