init(); bug
Many of you are propably familiar with the bug that sometimes occurs with inited weapons like bows and swords... Some frames (usually the last one) don't point in the same direction as the others, and it doesn't look very nice.
So what's with this bug and how can it be fixed?
So what's with this bug and how can it be fixed?
I get this problem a lot too
it seems to be fixed when you use the original dink.ini IIRC...
I know the bug you are referring to. Are you experiencing it with 1.08? I thought I managed to fix it.
Yeah, that seems to fix it. The reason may be here:
//this is here for reasons to complex to explain. j/k! This sequence
//is one that is going to be replaced, so I'm loading the one with the most
//frames first, because max frame count is initted only the first time we
//load into a certain seq #.
load_sequence_now graphics\dink\sword\hit\d-sa2- 102 75 52 92 -23 -12 24 11
load_sequence_now graphics\dink\sword\hit\d-sa4- 104 75 74 90 -23 -13 23 14
load_sequence_now graphics\dink\sword\hit\d-sa6- 106 75 33 92 -18 -14 18 10
load_sequence_now graphics\dink\sword\hit\d-sa8- 108 75 46 109 -17 -16 17 10
//this is here for reasons to complex to explain. j/k! This sequence
//is one that is going to be replaced, so I'm loading the one with the most
//frames first, because max frame count is initted only the first time we
//load into a certain seq #.
load_sequence_now graphics\dink\sword\hit\d-sa2- 102 75 52 92 -23 -12 24 11
load_sequence_now graphics\dink\sword\hit\d-sa4- 104 75 74 90 -23 -13 23 14
load_sequence_now graphics\dink\sword\hit\d-sa6- 106 75 33 92 -18 -14 18 10
load_sequence_now graphics\dink\sword\hit\d-sa8- 108 75 46 109 -17 -16 17 10











