Opened 15 years ago

Closed 15 years ago

#4052 closed defect (fixed)

DW1: Crash after intro animation on PowerPC 64

Reported by: SF/amorya Owned by: dreammaster
Priority: normal Component: Engine: Tinsel
Version: Keywords:
Cc: Game: Discworld


Using the latest ScummVM SVN code, Discworld 1 crashes after the intro animation with:

Assertion failed: (hPath != NOPOLY), function Swalk, file engines/tinsel/tinlib.cpp, line 3057.

System details: PowerPC G5 dual core 2ghz, 5.5GB RAM MacOS X 10.5.5 Discworld 1 demo, files linked to from ScummVM forums

The same game plays fine on an Intel Core2Duo system running MacOS X 10.5.6.

Backtrace attached.

Email address:

Ticket imported from: #2462700. Ticket imported from: bugs/4052.

Attachments (1)

scummvm2.txt (22.8 KB ) - added by SF/amorya 15 years ago.

Download all attachments as: .zip

Change History (8)

by SF/amorya, 15 years ago

Attachment: scummvm2.txt added


comment:1 by fingolfin, 15 years ago

Component: Engine: Tinsel
Game: Discworld
Owner: set to dreammaster
Summary: Tinsel (DW1): Crash after intro animation on PowerPC 64DW1: Crash after intro animation on PowerPC 64

comment:2 by joostp, 15 years ago

FWIW, this used to work prior to the DW2 merge. Now I also get the same error on my MIPS based Big Endian system, so it seems like a regression. Happy to help tracking it down as time permits.

comment:3 by dreammaster, 15 years ago

I've added some FROM_LE_32 to the CommonInits method in polygons.cpp - I'm not sure if this will completely fix the problem, or not, but at least it should be a start. On a related note, the entire DW2 game need to be properly tested for endian-ness as well.

comment:4 by dreammaster, 15 years ago

This hasn't seemed to have completely fixed the problem. I'm deassigning myself from this bug, as it needs someone with a big-endian system to properly test the merged DW2 codebase for endianness correctness

comment:5 by dreammaster, 15 years ago

Owner: dreammaster removed

comment:6 by joostp, 15 years ago

Owner: set to dreammaster
Resolution: fixed
Status: newclosed

comment:7 by joostp, 15 years ago

As far as I can tell this is fixed now...

Note: See TracTickets for help on using tickets.