Opened 14 years ago

Closed 14 years ago

#4752 closed defect

COMI: cutscene falls to internal debugger

Reported by: SF/h00ligan Owned by: sev-
Priority: high Component: Engine: SCUMM
Version: Keywords:
Cc: Game: Monkey Island 3


ScummVM 1.0.0 (Nov 8 2009 11:04:03) load attached save state

try exit to left part of screen following cutscene will fall to debugger with " (70:127:0x4F): Unknown Chunk found at 95687e: ...., -622395868" message

you may also try following sequence instead of loading save state: load game with -b 630 params use stan card with locked door open bed use all nails with bed use crawbar with hole use crawbar with bed take ring

Ticket imported from: #2933042. Ticket imported from: bugs/4752.

Attachments (1)

comi.s03 (79.9 KB ) - added by SF/h00ligan 14 years ago.

Download all attachments as: .zip

Change History (9)

by SF/h00ligan, 14 years ago

Attachment: comi.s03 added

comment:1 by eriktorbjorn, 14 years ago

I can't reproduce this on my Linux box with the English version of the game, neither with 1.0.0 nor the trunk. Valgrind reports no errors with the trunk either. The "Unknown Chunk" error comes, not surprisingly, from the SMUSH cutscene player. It expects to find an AHDR or FRME chunk, but in your case it found something else. This is what that part of moreslaw.san looks like in my version:

0956860: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 0956870: 0000 0000 0000 4652 4d45 0000 2efa 464f ......FRME....FO 0956880: 424a 0000 2ef2 2f00 0000 0000 8002 e001 BJ..../.........

The offset (95687e in hexadecimal) points to right after the chunk type (FRME) and chunk size (2efa in hexadecimal, or 12026 in decimal).

Could your moreslaw.san have become corrupted somehow?

comment:2 by fingolfin, 14 years ago

Summary: cutscene falls to internal debuggerCOMI: cutscene falls to internal debugger

comment:3 by sev-, 14 years ago

This bug is nice to get fixed before the release. Raising priority for keeping the track.

comment:4 by sev-, 14 years ago

Priority: normalhigh

comment:5 by fingolfin, 14 years ago

Status: newpending

comment:6 by fingolfin, 14 years ago

This tracker item is pending response by the submitter; we cannot continue processing it before that happens. As a consequence, its status has been set to "Pending". It will automatically revert to "Open" once a new comment is made to this item. If no response is made within 14 days, it will automatically be closed.

Thank you.

comment:7 by SF/sf-robot, 14 years ago

Status: pendingclosed

comment:8 by SF/sf-robot, 14 years ago

This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker).

Note: See TracTickets for help on using tickets.