Opened 5 years ago

Last modified 7 weeks ago

#6722 new defect

WME: The Kite - Script runtime errors

Reported by: raziel- Owned by: somaen
Priority: normal Component: Engine: Wintermute
Keywords: Cc:
Game: Wintermute

Description

ScummVM 1.8.0git (Aug 24 2014 08:51:39)
Features compiled in: Vorbis FLAC MP3 RGB zLib MPEG2 Theora AAC FreeType2 JPEG PNG

One can force "Script runtime error"s when performing a certain action (that probably shouldn't be allowed)

Load the save and walk left until the cutscene kicks in.
Wait until the busy pointer is gone and the cutscene goes into close-up.
You can now choose items from your inventory (that should probably be omitted).
Choose the knife and wait for the cutscene to switch to Oleh facing his back at the screen.
The knife in your hands glows up meaning you can "act" with it...use the knife with Oleh and the Script runtime errors will come up.

As i said, the whole possibility to choose items in that cutscene should probably be omitted

Savegame attached

The Kite (Version 1.3.e/Windows/English)

AmigaOS4 - PPC - SDL - BE
gcc (GCC) 4.2.4 (adtools build 20090118)

Ticket imported from: bugs/6722.

Attachments (1)

save001.dsv (211.9 KB ) - added by raziel- 5 years ago.

Download all attachments as: .zip

Change History (10)

comment:1 by somaen, 5 years ago

Owner: set to somaen

comment:2 by SF/tobiatesan, 5 years ago

Uhm. AFAIK we are basically running Mnemonic's script engine, I suspect that this could be an original game bug with P >= 0.6

Will have to test it with the original interpreter sometime to make sure.

comment:3 by raziel-, 5 years ago

Original game bug.

Checked with 1.3.e on windows.

by raziel-, 5 years ago

Attachment: save001.dsv added

comment:4 by raziel-, 5 years ago

Added a save from the original engine right before.

comment:5 by SF/tobiatesan, 5 years ago

I assume we can close this, right?

comment:6 by SF/tobiatesan, 5 years ago

Double post, sorry

comment:7 by raziel-, 5 years ago

I guess it can be closed and marked as "original engine bug"?

comment:8 by SF/tobiatesan, 5 years ago

Not yet. Looks like what we do here is
1. Checking with the original developer if there is an updated version (or plans for one)
2. If not, we consider adding a workaround.

comment:9 by raziel-, 7 weeks ago

I guess five years later that the original developer isn't interested in a fix?

Note: See TracTickets for help on using tickets.