[solved] bugger...stupid data

[dubbleD]

sorry i admit i shouldn't have this kind of problem with my dc at this point but i really cant be buggered finding the problem right now because im too tired...

right now, this ball (t3) is not showing the whole way and the sprite disappears from frame 9 to the last frame. but it does fly through all the frames.

heres the sprites dimensions

Code:

file(0-14): blah\X.bmp w: 256 h: 128 row: 3 col: 5

and the data

DC-Code: <frame> 0 flying pic: 1 state: 3005 wait: 1 next: 2 dvx: 22 dvy: 0 centerx: 58 centery: 117 itr: kind: 16 x: 0 y: 0 w: 256 h: 128 dvx: 5 dvy: 0 fall: 70 vrest: 100 bdefend: 16 injury: 10 zwidth: 10 itr_end: <frame_end> <frame> 1 flying pic: 0 state: 3005 wait: 1 next: 999 dvx: 22 dvy: 0 centerx: 58 centery: 117 itr: kind: 16 x: 0 y: 0 w: 256 h: 128 dvx: 5 dvy: 0 fall: 70 vrest: 100 bdefend: 16 injury: 10 zwidth: 10 itr_end: <frame_end> <frame> 2 flying pic: 2 state: 3005 wait: 1 next: 3 dvx: 22 dvy: 0 centerx: 58 centery: 117 itr: kind: 16 x: 0 y: 0 w: 256 h: 128 dvx: 5 dvy: 0 fall: 70 vrest: 100 bdefend: 16 injury: 10 zwidth: 10 itr_end: <frame_end> <frame> 3 flying pic: 3 state: 3005 wait: 1 next: 4 dvx: 22 dvy: 0 centerx: 58 centery: 117 itr: kind: 16 x: 0 y: 0 w: 256 h: 128 dvx: 5 dvy: 0 fall: 70 vrest: 100 bdefend: 16 injury: 10 zwidth: 10 itr_end: <frame_end> <frame> 4 flying pic: 4 state: 3005 wait: 1 next: 5 dvx: 22 dvy: 0 centerx: 58 centery: 117 itr: kind: 16 x: 0 y: 0 w: 256 h: 128 dvx: 5 dvy: 0 fall: 70 vrest: 100 bdefend: 16 injury: 10 zwidth: 10 itr_end: <frame_end> <frame> 5 flying pic: 5 state: 3005 wait: 1 next: 6 dvx: 22 dvy: 0 centerx: 58 centery: 117 itr: kind: 16 x: 0 y: 0 w: 256 h: 128 dvx: 5 dvy: 0 fall: 70 vrest: 100 bdefend: 16 injury: 10 zwidth: 10 itr_end: <frame_end> <frame> 6 flying pic: 6 state: 3005 wait: 1 next: 7 dvx: 22 dvy: 0 centerx: 58 centery: 117 itr: kind: 16 x: 0 y: 0 w: 256 h: 128 dvx: 5 dvy: 0 fall: 70 vrest: 100 bdefend: 16 injury: 10 zwidth: 10 itr_end: <frame_end> <frame> 7 flying pic: 7 state: 3005 wait: 1 next: 8 dvx: 22 dvy: 0 centerx: 58 centery: 117 itr: kind: 16 x: 0 y: 0 w: 256 h: 128 dvx: 5 dvy: 0 fall: 70 vrest: 100 bdefend: 16 injury: 10 zwidth: 10 itr_end: <frame_end> <frame> 8 flying pic: 8 state: 3005 wait: 1 next: 9 dvx: 22 dvy: 0 centerx: 58 centery: 117 itr: kind: 16 x: 0 y: 0 w: 256 h: 128 dvx: 5 dvy: 0 fall: 70 vrest: 100 bdefend: 16 injury: 10 zwidth: 10 itr_end: <frame_end> <frame> 9 flying pic: 9 state: 3005 wait: 1 next: 60 dvx: 22 dvy: 0 centerx: 58 centery: 117 itr: kind: 16 x: 0 y: 0 w: 256 h: 128 dvx: 5 dvy: 0 fall: 70 vrest: 100 bdefend: 16 injury: 10 zwidth: 10 itr_end: <frame_end>   <frame> 60 flying pic: 10 state: 3005 wait: 1 next: 61 dvx: 22 dvy: 0 centerx: 58 centery: 117 itr: kind: 16 x: 0 y: 0 w: 256 h: 128 dvx: 5 dvy: 0 fall: 70 vrest: 100 bdefend: 16 injury: 10 zwidth: 10 itr_end: <frame_end> <frame> 61 flying pic: 11 state: 3005 wait: 1 next: 62 dvx: 22 dvy: 0 centerx: 58 centery: 117 itr: kind: 16 x: 0 y: 0 w: 256 h: 128 dvx: 5 dvy: 0 fall: 70 vrest: 100 bdefend: 16 injury: 10 zwidth: 10 itr_end: <frame_end> <frame> 62 flying pic: 12 state: 3005 wait: 1 next: 63 dvx: 22 dvy: 0 centerx: 58 centery: 117 itr: kind: 16 x: 0 y: 0 w: 256 h: 128 dvx: 5 dvy: 0 fall: 70 vrest: 100 bdefend: 16 injury: 10 zwidth: 10 itr_end: <frame_end> <frame> 63 flying pic: 13 state: 3005 wait: 1 next: 64 dvx: 22 dvy: 0 centerx: 58 centery: 117 itr: kind: 16 x: 0 y: 0 w: 256 h: 128 dvx: 5 dvy: 0 fall: 70 vrest: 100 bdefend: 16 injury: 10 zwidth: 10 itr_end: <frame_end> <frame> 64 flying pic: 14 state: 3005 wait: 1 next: 10 dvx: 22 dvy: 0 centerx: 58 centery: 117 itr: kind: 16 x: 0 y: 0 w: 256 h: 128 dvx: 5 dvy: 0 fall: 70 vrest: 100 bdefend: 16 injury: 10 zwidth: 10 itr_end: <frame_end>[/spoiler]

anyone tell me whats making the sprite disappear please
your help will be greatly appreciated

[Alblaka]

I think, yout pic is may 1-3 px to small, therefore the last row of sprites (the last 5, aka; all sprites from frame 60-64) won't be displayed.
Just check whether your pic has really the neccessary dimension:
128*3+2=368 pxl

[dubbleD]

actually, 9 doesnt show either

ive checked the image and the dimensions for the entire grid is fine. all rectangles are identicle
what are you talking about with the 128*3+2=368??

[Alblaka]

Oh, hmm...
May you also have 1-3 px to less in the W, so pic 9 and 4 are not properly displayed? XD

Dunno, can't find any other error...

PS: Why there is a next:10 in frame 64? There is no frame 10?

[vandesdelca]

if its not the pic's dimension, then it must be the row-col or.... well, i don't see another possibilities other than that.

[Lauli]

You can split the sprite sheet up in two parts.
See if it works.

[forgetlatios]

Oh, hmm...
May you also have 1-3 px to less in the W, so pic 9 and 4 are not properly displayed? XD

Dunno, can't find any other error...

PS: Why there is a next:10 in frame 64? There is no frame 10?

he wants to destroy it after frame 64, and can we see the sheet?

[vandesdelca]

Oh, hmm...
May you also have 1-3 px to less in the W, so pic 9 and 4 are not properly displayed? XD

Dunno, can't find any other error...

PS: Why there is a next:10 in frame 64? There is no frame 10?

he wants to destroy it after frame 64, and can we see the sheet?

you're wrong, if he really want to destroy it, he should put frame 10 between frame 9 and 60, or just use next: 1000....
and yes, may we see the sheet?

[dubbleD]

never mind the next 10
its a ball. i just assumed everyone knew that in balls, from 10 was the hitting (or was it hit?) frames where most balls just die.
next 10 is for dying though i dunno why i didnt just put 1000....i should go and do that

as for the sheet
im currently using something from 'this' thread.
its this:

Apocalipsis made it into a gif:

sheet (Click to View)

of course credits will be needed because it was mentioned in the post but right now, thats not my concern.

[forgetlatios]

never mind the next 10
its a ball. i just assumed everyone knew that in balls, from 10 was the hitting (or was it hit?) frames where most balls just die.
next 10 is for dying though i dunno why i didnt just put 1000....

because 1000 doesn't give the dying frames?