You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I verified my game files creating a clean environment.
I ported a TASK from HospitalLower to AndroidLab. The game crashed upon loading into the AndroidLab each time.
I thought it was the porting process being experimental or some other issue, but then I tried the debug menu and
I got it load the map without the crash.
I made a mistake and needed to start over again. And then the game crashed loading into M7 each time.
I'd forgot about the sequence I had followed earlier that made it work. Then I realized that verifying the game
removed the patching on the AI.EXE for the file CRC checks. So the game was closing because of that.
I verified OpenCAGE and tried the debug menu this fixed it and it no longer crashes.
Can you add some sort of check that the patching is in place perhaps following porting or maybe any
resource edit that triggers the CRC checks. How about a message to indicate whether it's patched or not at start up?
The text was updated successfully, but these errors were encountered:
I verified my game files creating a clean environment.
I ported a TASK from HospitalLower to AndroidLab. The game crashed upon loading into the AndroidLab each time.
I thought it was the porting process being experimental or some other issue, but then I tried the debug menu and
I got it load the map without the crash.
I made a mistake and needed to start over again. And then the game crashed loading into M7 each time.
I'd forgot about the sequence I had followed earlier that made it work. Then I realized that verifying the game
removed the patching on the AI.EXE for the file CRC checks. So the game was closing because of that.
I verified OpenCAGE and tried the debug menu this fixed it and it no longer crashes.
Can you add some sort of check that the patching is in place perhaps following porting or maybe any
resource edit that triggers the CRC checks. How about a message to indicate whether it's patched or not at start up?
The text was updated successfully, but these errors were encountered: