Opened 9 years ago

Closed 9 years ago

Last modified 5 years ago

#5156 closed defect (fixed)

SCI: QFG2: Game can hang in desert

Reported by: SF/kuroshiro Owned by: m-kiewitz
Priority: low Component: Engine: SCI
Keywords: original script Cc:
Game: Quest for Glory 2

Description

Quest for Glory 2 (Dos/English)
ScummVM 1.2.0SVN 51733
Windows 7 x64

In the desert, when you get into a fight when riding the saurus it will run away. To get it back you have to leave and reenter the screen. The game will then automatically have you ride it again. However, if you input "Ride" again while you have time to input, the game will hang and you'll have to reload.

Ticket imported from: #3040055. Ticket imported from: bugs/5156.

Attachments (1)

qfg2.017 (36.8 KB ) - added by SF/kuroshiro 9 years ago.
walk left and quickly type "Ride"

Download all attachments as: .zip

Change History (11)

comment:1 by bluegr, 9 years ago

Please add a save game

by SF/kuroshiro, 9 years ago

Attachment: qfg2.017 added

walk left and quickly type "Ride"

comment:2 by SF/kuroshiro, 9 years ago

Added the correct saved game.

comment:3 by bluegr, 9 years ago

Seems lika a timing/script bug yet again, which shouldn't happen during "regular" gameplay, thus lowering priority

comment:4 by bluegr, 9 years ago

Priority: normallow

comment:5 by bluegr, 9 years ago

Owner: set to bluegr
Status: newclosed

comment:6 by bluegr, 9 years ago

Moving to the wiki, known SCI bugs page:
http://wiki.scummvm.org/index.php/SCI/Bugs

comment:7 by bluegr, 9 years ago

Keywords: original added

comment:8 by m-kiewitz, 5 years ago

Summary: QFG2: Game can hang in desertSCI: QFG2: Game can hang in desert

comment:9 by m-kiewitz, 5 years ago

Keywords: script added
Owner: changed from bluegr to m-kiewitz
Resolution: fixed

comment:10 by m-kiewitz, 5 years ago

script patch added in commit 53f9dac75ef0c0c22c513068eaccf8c96457a438

it is a game bug and also occurs, when using the original interpreter

command "ride" disables controls and a proximity check triggers mounting again, which disables controls a second time. Controls are only re-enabled once, which means controls stay disabled. My patch is risky and may break something, but the bug is really complicated and this was the best way I could come up with.

Note: See TracTickets for help on using tickets.