Steam crash: Couldn't load the game! [LA]
issueid=4146 12-07-2015 03:24 PM
Member
Number of reported issues by Drifted: 7
Steam crash: Couldn't load the game! [LA]
Game crashes when trying to load game
I've been getting multiple crashes where game claims they can't read file folders from tmpdat (those files with 4 numbers). It didn't really bother me as the game loaded normally after these crashes. But now after one of those crashes I get the following error "Couldn't laod the game! [LA]". So I guess I need to forsake my elven archer which was just winning the game :( I will post the file loading crash when it happens next time.

EDIT: Tried with R64 beta. Same error when loading.
Issue Details
Issue Number 4146
Issue Type Bug
Project ADOM (Ancient Domains Of Mystery)
Category Windows 7 (Steam)
Status Unconfirmed
Priority 4
Affected Version ADOM r63 (v2.0.2)
Fixed Version (none)
Milestone Potential work pipeline
Users able to reproduce bug 1
Users unable to reproduce bug 0
Attachments 3
Assigned Users adom-admin, jt
Tags (none)




12-21-2015 01:48 AM
Junior Member
Same just happened for me. ADOM crashed I was exploring R2 dungeon, when restarted - It couldn't load the save files - both .svg and .bak(if renamed to svg) can't be loaded. I have a suspicion that initial crash happened during auto-save.
About 15 hours of gameplay lost :( (and not even YASD)

Steam, Windows 10. ADOM Release 63 (2.0.2)

attaching adom.err and save files.
Reply Reply  

12-21-2015 02:06 AM
Junior Member
Also, here is an entry from Windows 'Application' Log for the crash that corrupted the save file:

Faulting application name: adom.exe, version: 0.0.0.0, time stamp: 0x564f7a9c
Faulting module name: adom.exe, version: 0.0.0.0, time stamp: 0x564f7a9c
Exception code: 0xc0000005
Fault offset: 0x00030e90
Faulting process id: 0x3cb4
Faulting application start time: 0x01d13b881cd4375d
Faulting application path: D:\Games\SteamLibrary\steamapps\common\ADOM\adom.exe
Faulting module path: D:\Games\SteamLibrary\steamapps\common\ADOM\adom.exe
Report Id: dd643475-04cb-4031-bbe4-999f5076e385
Faulting package full name:
Faulting package-relative application ID:
Reply Reply  

12-22-2016 05:15 AM
Senior Member
I've just had this same crash in r72.

very annoying
Reply Reply  

+ Reply