Opened 4 years ago
Last modified 6 months ago
#11529 new defect
CRUISE: Cut-scenes happen too quickly and dialogue cannot be read
Reported by: | JohnnyWalkerDesign | Owned by: | |
---|---|---|---|
Priority: | normal | Component: | Engine: Cruise |
Version: | Keywords: | ||
Cc: | Game: | Cruise for a Corpse |
Description (last modified by )
MacOS 10.14.6 / ScummVM 2.1.2
Specific cut-scenes happen too quickly for dialogue to be read. For example: Julio talking about the Pocket-Watch and recounting Fabiani's Poker game with Niklos. Or when Rebecca attempts to shoot Dick.
This is the correct speed of the cut-scene for reference:
https://youtu.be/VAlVDtThgW0?t=3914
Attachments (2)
Change History (10)
by , 4 years ago
Attachment: | cruise.s27 added |
---|
comment:1 by , 4 years ago
Description: | modified (diff) |
---|
comment:2 by , 4 years ago
Summary: | Cut-scenes happen too quickly and dialogue cannot be read → CRUISE: Cut-scenes happen too quickly and dialogue cannot be read |
---|
comment:3 by , 4 years ago
Priority: | normal → high |
---|
comment:4 by , 4 years ago
I did my best to try and understand the logic of the scripts, but since I'm not the original engine author, I couldn't locate anything in the script interpreter related to delays. So there must be something in the engine itself.. maybe the cutscene script is "yielding" execution for a time, but if that's the case, I can't locate where it's doing so
comment:5 by , 3 years ago
Still a problem on version 2.3.0git22086-g49a5fd6ebe, the only "workaround" is to pause the game (p key)
comment:7 by , 22 months ago
Priority: | high → normal |
---|
comment:8 by , 6 months ago
I have experienced the same problem.
The game has... oh I can't remember the term... "no CPU timer?", which means it runs faster on a 286 with 16 mHz than on one with 8 mHz.
I tried it with DOSBox Staging, as 386_slow with 2470 cycles, which corresponds to a 286 with ~11,5 mHz.
[cpu]
cputype = 386_slow
cycles = 2470
The game should run in such a way that the texts are easily readable even by not so fast readers. From today's perspective, the display looks very jerky, but that was the case back then.
Go to BAR to see cut-scene