[WD] Reproducible bug: rewinding with different choice crashes game
Rewinding to Chapter 5 and making a different choice crashes game
note: several others have found variants of this same bug -"julchen80", "leon_xiv", "beuh_tone", "DjangoZom", "Burana", "bradtherad" (many on mac -- I'm on PC)
See further discussion at these three threads:
http://www.telltalegames.com/forums/showthread.php?t=29451
http://www.telltalegames.com/forums/showthread.php?t=29748
http://www.telltalegames.com/forums/showthread.php?t=29667
Windows 7 64bit, steam version of game
1) Need an existing save game where you gave girl in room 9 the gun, that has progressed further to a later chapter (saved at chapter 6 or later)
2) REWIND to Chapter 5 girl in room 9 (need a later save that requires rewind to reach this!)
3) on replay instead choose to not give her the gun.
4) crashes shortly thereafter. (event viewer log below)
Workaround: instead rewind further to chapter 4. Choosing to not give her the gun works fine and doesn't cause crash.
Note: I have to disable internet in order to play, unsure whether this affects this bug.
I didn't test other permutations like rewinding and making the same choice as before, it's possible this also causes crash on this scene.
I had a lot of success with rewinds on other chapters.
Ever since I found the "disable internet" workaround to getting the game working, I've had no crashes other than this one.
Faulting application name: WalkingDead101.exe, version: 2012.4.23.11289, time stamp: 0x4f95e3ff
Faulting module name: fmodex.dll, version: 0.4.38.4, time stamp: 0x4ee56056
Exception code: 0xc0000005
Fault offset: 0x000cb59c
Faulting process id: 0xf8c
Faulting application start time: 0x01cd299afe515830
Faulting application path: c:\program files (x86)\steam\steamapps\common\the walking dead\WalkingDead101.exe
Faulting module path: c:\program files (x86)\steam\steamapps\common\the walking dead\fmodex.dll
Report Id: a2857b6c-958e-11e1-b900-001a6bbbc7c7
note: several others have found variants of this same bug -"julchen80", "leon_xiv", "beuh_tone", "DjangoZom", "Burana", "bradtherad" (many on mac -- I'm on PC)
See further discussion at these three threads:
http://www.telltalegames.com/forums/showthread.php?t=29451
http://www.telltalegames.com/forums/showthread.php?t=29748
http://www.telltalegames.com/forums/showthread.php?t=29667
Windows 7 64bit, steam version of game
1) Need an existing save game where you gave girl in room 9 the gun, that has progressed further to a later chapter (saved at chapter 6 or later)
2) REWIND to Chapter 5 girl in room 9 (need a later save that requires rewind to reach this!)
3) on replay instead choose to not give her the gun.
4) crashes shortly thereafter. (event viewer log below)
Workaround: instead rewind further to chapter 4. Choosing to not give her the gun works fine and doesn't cause crash.
Note: I have to disable internet in order to play, unsure whether this affects this bug.
I didn't test other permutations like rewinding and making the same choice as before, it's possible this also causes crash on this scene.
I had a lot of success with rewinds on other chapters.
Ever since I found the "disable internet" workaround to getting the game working, I've had no crashes other than this one.
Faulting application name: WalkingDead101.exe, version: 2012.4.23.11289, time stamp: 0x4f95e3ff
Faulting module name: fmodex.dll, version: 0.4.38.4, time stamp: 0x4ee56056
Exception code: 0xc0000005
Fault offset: 0x000cb59c
Faulting process id: 0xf8c
Faulting application start time: 0x01cd299afe515830
Faulting application path: c:\program files (x86)\steam\steamapps\common\the walking dead\WalkingDead101.exe
Faulting module path: c:\program files (x86)\steam\steamapps\common\the walking dead\fmodex.dll
Report Id: a2857b6c-958e-11e1-b900-001a6bbbc7c7
This discussion has been closed.
Comments
Is it helpful or should I not bother?
I don't expect feedback on the issue but wanted confirmation that someone looks at it so I know it's not a waste to fill out more.
I've updated the original bug post above to include the fact that six others in the forum have now found and confirmed variants of this bug -- most of them on a mac (I'm on a PC)