New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

STARK: Blocker/Crash on “Crow Leaves” video at the start of chapter 7 #1492

MikhailAristov opened this Issue Aug 26, 2018 · 1 comment


None yet
1 participant

MikhailAristov commented Aug 26, 2018

The Longest Journey (both the unmodified GOG Version, without the police station fix, AND the unmodified Steam version, dito) crashes at the start of chapter 7, when April is on the raft and Crow flies away. The console output at that point shows repeated invocations of “WARNING: (TODO: Implement) opFullMotionVideoPlay(Crow Leaves) : (Level idx 0) (container idx 2) (FMV idx 41) - 1!”, like it’s caught in an endless loop. This video has played earlier multiple times with no trouble.

The crash occurs reliably on my installation of ResidualVM (daily build from 16 August 2018; using the default graphics renderer, no sure what it is). I have uploaded the save to my website: for the GOG version and for the Steam version. To replicate the crash, just talk to Crow and use the second dialogue option twice. The issue is a Blocker because you cannot proceed with the game until after Crow flies away, so there is no away around that cutscene crash.

I am running the game on a Win7 x64 laptop (HP Pavilion) with an i7-6700HQ, 8 GB RAM and Intel HD Graphics 530. Both game installations are on an SSD.

EDIT: Found a workaround using the Debug Mode: typing "forceScript 16" makes Crow fly away, skipping the dialogue, after which the video loads normally and the game proceeds as usual.

@bgK bgK closed this in 0f3cf3e Aug 28, 2018


This comment has been minimized.

Show comment
Hide comment

MikhailAristov Aug 31, 2018

Just confirmed that the crash no longer happens in the daily build from August 29. :-)

MikhailAristov commented Aug 31, 2018

Just confirmed that the crash no longer happens in the daily build from August 29. :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment