#6979 closed defect (fixed)
Broken Sword 2.5 Crashes when the time-bomb on train should go off
| Reported by: | SF/albadross | Owned by: | sev- |
|---|---|---|---|
| Priority: | high | Component: | Engine: Sword25 |
| Version: | Keywords: | ||
| Cc: | Game: | Broken Sword 2.5 |
Description
ScummVM Version : 1.8.0 git5172-g7820bd5 (Dec 7 2015 04:25:06)
Problem : The game crashes at the end of the train scene when you click the whistle on the dog to activate the time-bomb - Lua error occurred. Code 2.
I attach a series of saves of the game on the train but unfortunately due to bug #6977 I cannot get them to re-load. The last save sword25.016 is when the whistle has to be clicked on the dog. The last save I can load is the first one attached to bug #6977
Language : English Windows 7 Ultimate 64-bit
Ticket imported from: bugs/6979.
Attachments (6)
Change History (12)
by , 9 years ago
| Attachment: | sword25.013 added |
|---|
comment:1 by , 9 years ago
| Priority: | normal → high |
|---|
comment:2 by , 9 years ago
by , 9 years ago
| Attachment: | sword25.007 added |
|---|
comment:3 by , 9 years ago
Now that bug #6977 has been fixed, I have a savegame at the problem point that will reload. To demonstrate the problem, click the whistle on the dog.
comment:4 by , 9 years ago
We seem to hide the actual script error message, but it appears to be this:
rooms/uba/scripts/default.lua:1073: The renderobject with the handle 13031 does no longer exist.
comment:5 by , 9 years ago
...and this appears to be the same bug in the original: http://forum.baphometsfluch25.de/viewtopic.php?f=52&t=2718
comment:6 by , 9 years ago
My current guess is that this is what's happening.
The background animations in this room (uba), such as DoLamp, update regularly until CurrentRoom changes, at which point they exit.
The room changing code first unloads/deregisters bitmaps/animations, and only then calls OnLeave. The explosion movie is started in the OnLeave script of the uba room.
While the movie is running, the background animations update because CurrentRoom is still valid, and dereference invalid handles.
comment:7 by , 9 years ago
I noticed you mentioned you did finish the game. Does that mean that this bug can be avoided, or only happens sometimes for you?
comment:8 by , 9 years ago
It was a freak occurrence (say, 1 in a 100) that I got past that scene and I doubt that I could do it again.
I tried combinations of all of the following many times :
- Waiting to see if the time-bomb would go off by itself
- Exhausting conversation with everyone on the train
- Examining everything I could even if it wasn't needed for the story
- Waiting for a time doing nothing (to see if the program would sort itself out)
Eventually I got lucky - once!
comment:9 by , 9 years ago
| Owner: | set to |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
comment:10 by , 9 years ago
This was fixed by commit 12fadf7 which restored original engine Lua error processor.
It would be nice to fix it before the release of 1.8.0. Raising priority.