Opened 13 years ago

Closed 13 years ago

#2745 closed defect (fixed)

PSP: 0.9.1svn text is illegible during MI2 dream sequence

Reported by: SF/patters98 Owned by: joostp
Priority: normal Component: Engine: SCUMM
Keywords: Cc:
Game: Monkey Island 2

Description

Using the PC VGA version of Monkey Island 2 patched to
remove codewheel check, using the 0.9.1svn (Jul 8 2006
14:57:12) on PSP firmware 1.5.

Using the attached save file, if you "walk to oar" to
start the dream sequence, the speech text is the wrong
colour and cannot be read.

The 0.9.0 release version does not exhibit this
problem.
The older 0.9.0svn bug finding release (via forums)
however exhibited more serious bugs here and did not
display the song text beyond the first verse and the
cutscene had to be manually skipped.

Ticket imported from: #1525218. Ticket imported from: bugs/2745.

Attachments (1)

monkey2.s07 (14.6 KB) - added by SF/patters98 13 years ago.
save state for MI2 dream sequence

Download all attachments as: .zip

Change History (7)

Changed 13 years ago by SF/patters98

Attachment: monkey2.s07 added

save state for MI2 dream sequence

comment:1 Changed 13 years ago by SF/patters98

Summary: PSP: 0.9.1svn text is illegible during dream sequencePSP: 0.9.1svn text is illegible during MI2 dream sequence

comment:2 Changed 13 years ago by fingolfin

Owner: set to joostp

comment:3 Changed 13 years ago by joostp

Which text exactly is illegible? I just loaded this
savegame in the "0.9.1svn test build", clicked "use oar" and
all seems fine in the dream sequence here.

comment:4 Changed 13 years ago by joostp

Actually, scratch that. I was accidentally running a
different build. I can indeed reproduce the bug with
0.9.1svn and this save.

comment:5 Changed 13 years ago by joostp

Resolution: fixed
Status: newclosed

comment:6 Changed 13 years ago by joostp

This is now fixed in SVN / the latest build.

I don't know what caused (or fixed) it, but my guess was it
was a temporary regression in SVN just at the time I built
the test version in question.

Thanks for reporting though :)

Note: See TracTickets for help on using tickets.