Reply to Re: Arrrgh! Bug in tinker cut-scene
If you don't have an account, just leave the password field blank.
January 8th 2009, 03:22 PM
Kåre
A little investigation shows that the error isn't in fact in DEC-FRG.D after all.
Looking at the coredump, I found the following:
#0 0x0804fc6d in process_line (script=11,
s=0xbfe84af0 "freeze(¤t_sprite);\n", doelse=0)
at dinkc_bindings.c:728
#1 0x0804c7eb in run_script (script=11) at dinkc.c:1096
#2 0x08072ca9 in up_cycle () at freedink.c:3642
#3 0x080732a5 in updateFrame () at update_frame.c:298
#4 0x0806da65 in main (argc=2063600128, argv=0x4807460f) at freedink.c:5240
So the line that fails seems to be
freeze(¤t_sprite);
and that's from DECRETUS.D - i found the source in .chm format...
It seems current_sprite has the wrong value
Unfortunately I have no idea how to fix this!
Anyone?
I spent too much time playing the DMOD up til now, to just give up here
Looking at the coredump, I found the following:
#0 0x0804fc6d in process_line (script=11,
s=0xbfe84af0 "freeze(¤t_sprite);\n", doelse=0)
at dinkc_bindings.c:728
#1 0x0804c7eb in run_script (script=11) at dinkc.c:1096
#2 0x08072ca9 in up_cycle () at freedink.c:3642
#3 0x080732a5 in updateFrame () at update_frame.c:298
#4 0x0806da65 in main (argc=2063600128, argv=0x4807460f) at freedink.c:5240
So the line that fails seems to be
freeze(¤t_sprite);
and that's from DECRETUS.D - i found the source in .chm format...
It seems current_sprite has the wrong value
Unfortunately I have no idea how to fix this!
Anyone?
I spent too much time playing the DMOD up til now, to just give up here