The Dink Network

Crash during cutscene

Pilgrim's Quest

October 9th 2015, 07:38 PM
I experience a crash during the cutscene after handing the tinkerer the basilisk scale. to be precise on the screen where the badguy looks at the obelisk-like monument.....

From some research i guess it is a buffer overflow in the game,
experienced in earlier versions by some linux users. as the Linux kernel is generally stricter players probably didn't experience it until now. PQ attempted to freeze sprite #1000 while the maximum sprite number is 300. '1000' is a special sprite in the game
which means 'not attached to the current screen' and is much used in
cut scene, but as you can imagine this is error-prone for the engine

can someone help fix it?

October 11th 2015, 04:45 AM
Peasant Male France

Can you try if this development version fixes the problem?

If not, can you send me a saved game, with instructions on how to reproduce the crash?
October 11th 2015, 05:36 PM
thanks for the really fast answer, considering i didnt expect anyone to still be here ....
(i played the original dink way back, and just recentlygot hookedon the new HD and all the dmods)

in my initial rage i forgot to properly post and to mention that i was using win 7 and dinkHD.

i downloaded freedink, copied a savegame and it worked without a problem. I transfered the savegame after the cutscene "back" and i seem to have therefore worked around but not cleared the problem. So if you are interested in fixing i can get you that savegame if you like :

thanks again


October 11th 2015, 07:43 PM
Peasant Male Equatorial Guinea xbox steam duck bloop
can't flim flam the glim glam 
thanks for the really fast answer, considering i didnt expect anyone to still be here ....

Hey, we're still here. And by we, I mean me.
October 12th 2015, 03:53 AM
I am also still here.
November 9th 2015, 12:50 PM
Peasant Netherlands
Never be afraid to ask, but don't demand an answer 
So if you are interested in fixing

I don't think anyone is maintaining any engine other than Freedink. The usual reason GNU/Linux users don't experience the bugs is that they have been fixed in Freedink, and the other engines don't run on their system.