Opened 15 years ago
Closed 3 years ago
#4424 closed defect (fixed)
SCUMM: COMI - Guybrush walks in place when examing certain objects
| Reported by: | SF/buffmcmanly | Owned by: | athrxx |
|---|---|---|---|
| Priority: | normal | Component: | Engine: SCUMM |
| Version: | Keywords: | ||
| Cc: | Game: | Monkey Island 3 |
Description
* ScummVM version: 0.13.0. * Language of game: English. * Version of game: Regular CD-ROM, purchased in Europe, all required contents from the CD copied onto harddrive like the instructions in the readme said. * Platform and Compiler: Win32, normal version from the Downloads-page.
Examing a few objects with the E -keyboard hotkey while walking causes Guybrush not to stop; instead he keeps walking in place while talking and keeps walking in place after he's done talking. This only happens with the keyboard hotkey, using the "Action Coin" does not cause this bug. Objects which cause this bug are:
-The clock tower on Puerto Pollo at the main square and at the Field of Honor (where the caber toss and dueling banjos take place) -The "diastant beach" at the Field of Honor. -The "Tiki lanterns" outside the Goodsoup Hotel on Blood Island.
Ticket imported from: #2823309. Ticket imported from: bugs/4424.
Attachments (1)
Change History (8)
by , 15 years ago
comment:1 by , 15 years ago
The problem is the examine command seems to be processed too quickly, before Guybrush walks to his destination.
In the original game, Guybrush would completely walk to his destination, before examining the item.
comment:3 by , 4 years ago
| Summary: | COMI: Guybrush walks in place when examing certain objects → SCUMM: COMI - Guybrush walks in place when examing certain objects |
|---|
comment:4 by , 3 years ago
| Owner: | set to |
|---|---|
| Resolution: | → pending |
| Status: | new → pending |
Does this still happen?
comment:5 by , 3 years ago
I can't find my own patch on sourceforge, but another patch was submitted and rejected:
https://bugs.scummvm.org/ticket/9170
comment:6 by , 3 years ago
So the answer to the question would be: it still happens, right?
The only thing I am currently doing here is to evaluate whether the ticket can be closed or not.
EDIT: I've checked myself. It still happens...
comment:7 by , 3 years ago
| Resolution: | pending → fixed |
|---|---|
| Status: | pending → closed |
I have made a fix for this. I have tested the clock tower situation only, but it should be the same cause for the other cases mentioned in the ticket description (script reporting wrong movement data due to bugged movement code).
Closing this. Feel free to reopen if any of the issues in the ticket description remain...
Save game where these bugs can be seen.