Opened 5 weeks ago
Last modified 2 weeks ago
#15388 new defect
TWINE: LBA: Bulldozer driven by Twinsen can get stuck behind truck (soft lock)
Reported by: | antoniou79 | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | Engine: TwinE |
Version: | Keywords: | collision-detection | |
Cc: | Game: | Little Big Adventure |
Description
Happens in Windows 10, ScummVM 2.9.0git built from recent master HEAD.
There's a scene from the construction area where Twinsen gets the keys to drive a bulldozer. After entering the bulldozer the game removes control from the player and the bulldozer moves automatically along some pre-existing tire tracks.
The issue comes from another NPC truck moving along those tracks as well. And that truck also stops in some pre-defined spots, at least one of which is in the path of the auto-driven bulldozer.
I've had the bulldozer stuck behind the truck twice in a row in my recent playthrough. And unfortunately this seems to mess up the truck's "patrol" sequence too, because the truck wouldn't start again to move along the tracks. Both vehicles remained there and I could only force quit the game.
Both times the bulldozer was stuck in the location indicated by the attached screenshot.
I am also attaching a saved game from the location. To reproduce you have to make it to the NPC elephant near the bulldozer that will give you the keys when you talk to him, and then go up to the bulldozer (might need to press Space on it on Normal mode).
The way I got past this was that I kept my eye on where the NPC truck was, to make sure it was far enough from the "softlock corner", and then get in the bulldozer.
Attachments (2)
Change History (5)
by , 5 weeks ago
Attachment: | lba-win-1.002 added |
---|
by , 5 weeks ago
Attachment: | scummvm-lba-win-1-00069Cricl.png added |
---|
comment:1 by , 4 weeks ago
Keywords: | collision-detection added |
---|
comment:2 by , 3 weeks ago
comment:3 by , 2 weeks ago
Not yet fixed - could still reproduce it with revision b81a05b9463ee36ffbfed4a407d1941f007bcdb4
Not yet verified - but it is very likely to be related to the commit 4ad6a6961cff13bc421e0ce19c5ed1c225b4e9a6 - and thus maybe fixed, too