3 ms·
I wouldn't be surprised if there's literally a variable called SAVEGAME that's a char[8192] array somewhere in the serialization path and that's what's causing
by kmeisthax 6y ago
I wouldn't be surprised if there's literally a variable called SAVEGAME that's a char[8192] array somewhere in the serialization path and that's what's causing the corruption.
- saagarjha 6y agoYou're off by ten orders of magnitude ;) char SAVEGAME[8388608];