The Dink Network

Ending 3 hardfreeze in FreeDink and way to avoid it

Cast Awakening Part 1: Initiation

June 28th, 05:16 AM
sob_scorpb.gif
Just in case: FreeDink version I used appears to be 109.6

After killing the Cast King, ending 3 plays, but somewhere in a middle of it hard freeze happens requiring you to kill FreeDink with task manager in Windows.

To avoid this freeze, press spacebar rapidly to skip dialog as fast as possible, and you should be able to get to the credits (and have some goodie unlocked, which is the reason you want to actually get through this cinematic) without the freeze happening.

As for the skipped dialogue, you will be able to read it by reading ending3.c (until bug is fixed that is)
June 30th, 01:23 AM
custom_robj.png
Robj
Jester Male Australia
You feed the madness, and it feeds on you. 
At what point does the cutscene freeze?
June 30th, 03:21 AM
sob_scorpb.gif
It always happens during dialogue between Elder and Acolyte (ending3.c past "// Screen 674" comment line), unless spacebar is mashed during that dialogue (you don't have to press spacebar on other screens of that long cutscene). Which lines are seen depends on whether (and how many times) player pressed spacebar.

If spacebar was not pressed at all during ENTIRE cutscene (from the very beginning, not between Elder and Acolyte), freeze happens after the second line of dialogue:
- It has, has it?

If spacebar was violently mashed throughout entire cutscene BEFORE screen changes to 674 where dialogue between Elder and Acolyte happens, but not after this part of cutscene begins, two more lines will be seen, and the game will be freezed at:
- We should have known better than to mess with the dead.

If you skip first few lines of that dialogue, but stop pressing spacebar afterwards, the freeze will still happen a few lines after.

The spacebar has to be mashed during the dialogue between Elder and Acolyte to get past the possible freeze before it has time to happen (it can only happen during that part of scene). It is as if it set to happen a fixed duration after screen change to 674 happens, so you need to hurry so that script gets killed. If you got to the credits rolling, you are safe from that point onwards, as ending3.c script gets killed and a different script is responsible for showing you credits which doesn't have this bug.

As to what causes the bug to happen, I have no idea.
June 30th, 02:19 PM
custom_robj.png
Robj
Jester Male Australia
You feed the madness, and it feeds on you. 
Thanks for that info, I've found the cause of the bug and messaged Redink1 about it, it's up to him if he wants to fix and update it.

It's nothing to do with the scripts, there's an error in the dink.ini, which causes a crash in that specific scenario due to an invalid ini line.