[solved] A weird opoint problem

[A-Man]

I needed to split up my sprites because they are big, after doing this I encountered an opoint problem:
I have some opoints that stopped working after they where actually working before splitting.
Why did this happen?



note: it's activated by a next frame.
please help.

[Azriel]

check the bmp part of the data for the object that is opointed. the file: lines of the split spritesheets have to replace the original ones (and make sure the row: and col: values are correct)



Azriel~

the width and height must be correct as well ~ Marshall

[A-Man]

check the bmp part of the data for the object that is opointed. the file: lines of the split spritesheets have to replace the original ones (and make sure the row: and col: values are correct)



Azriel~

the width and height must be correct as well ~ Marshall

No, there is no problem with the height ,width ,col and row.
I checked many times for that.
I tried the dimensions with your frame maker and it showed correctly.
I even tried to replace the centerx and centery, or find any dc mistake but couldn't.
I am sure that I spelled the picture name correctly.
I think that is the weirdest problem that happened to me ever.Thanks after all.

[empirefantasy]

Post the dat file here and we can see which is the problem.Maybe you have put the number of pic wrong,or the action wrong in opoint tag.

First see,what opoint tag have (oid: and action: ).Then see if frames are correctly in the dat file which is opointed.Then see if pics are correctly in these frames.Do so for all.

[A-Man]

Post the dat file here and we can see which is the problem.Maybe you have put the number of pic wrong,or the action wrong in opoint tag.

First see,what opoint tag have (oid: and action: ).Then see if frames are correctly in the dat file which is opointed.Then see if pics are correctly in these frames.Do so for all.

Thats the move,

DC-Code: <frame> 255 finger_shot pic: 72 state: 3 wait: 2 next: 256 dvx: 0 dvy: 0 centerx: 37 centery: 158 hit_a: 0 hit_d: 0 hit_j: 0 mp: 90 bdy: kind: 0 x: 21 y: 18 w: 43 h: 62 bdy_end: bdy: kind: 0 x: 15 y: 65 w: 39 h: 93 bdy_end: <frame_end> <frame> 256 finger_shot pic: 73 state: 3 wait: 2 next: 251 dvx: 0 dvy: 0 centerx: 37 centery: 158 hit_a: 0 hit_d: 0 hit_j: 0 bdy: kind: 0 x: 21 y: 18 w: 43 h: 62 bdy_end: bdy: kind: 0 x: 15 y: 65 w: 39 h: 93 bdy_end: <frame_end> <frame> 251 finger_shot pic: 74 state: 3 wait: 2 next: 252 dvx: 0 dvy: 0 centerx: 37 centery: 158 hit_a: 0 hit_d: 0 hit_j: 0 bdy: kind: 0 x: 21 y: 18 w: 43 h: 62 bdy_end: bdy: kind: 0 x: 15 y: 65 w: 39 h: 93 bdy_end: <frame_end> <frame> 252 finger_shot pic: 75 state: 3 wait: 2 next: 253 dvx: 0 dvy: 0 centerx: 37 centery: 158 hit_a: 0 hit_d: 0 hit_j: 0 bdy: kind: 0 x: 21 y: 18 w: 43 h: 62 bdy_end: bdy: kind: 0 x: 15 y: 65 w: 39 h: 93 bdy_end: opoint: kind: 1 x: 38 y: 80 action: 12 oid: 233 facing: 1 opoint_end: Problem is here <frame_end> <frame> 253 finger_shot pic: 76 state: 3 wait: 2 next: 254 dvx: 0 dvy: 0 centerx: 37 centery: 158 hit_a: 0 hit_d: 0 hit_j: 0 bdy: kind: 0 x: 21 y: 18 w: 43 h: 62 bdy_end: bdy: kind: 0 x: 15 y: 65 w: 39 h: 93 bdy_end: <frame_end> <frame> 254 finger_shot pic: 77 state: 3 wait: 20 next: 999 dvx: 0 dvy: 0 centerx: 37 centery: 158 hit_a: 0 hit_d: 0 hit_j: 0 bdy: kind: 0 x: 21 y: 18 w: 43 h: 62 bdy_end: bdy: kind: 0 x: 15 y: 65 w: 39 h: 93 bdy_end: opoint: kind: 1 x: 43 y: 77 action: 0 dvx: 0 dvy: 0 oid: 221 facing: 0 opoint_end: <frame_end>

that is the opointed object:

DC-Code: <bmp_begin> file(0-29): sprite\sys\kuam4.bmp w: 158 h: 159 row: 10 col: 3 <bmp_end>         <frame> 12 flying pic: 21 state: 3005 wait: 1 next: 12 dvx: 0 dvy: 0 dvz: 0 centerx: 24 centery: 141 hit_a: 0 hit_d: 0 hit_j: 0 <frame_end> <frame> 13 flying pic: 22 state: 3005 wait: 1 next: 14 dvx: 0 dvy: 0 dvz: 0 centerx: 24 centery: 141 hit_a: 0 hit_d: 0 hit_j: 0 <frame_end> <frame> 14 flying pic: 23 state: 3005 wait: 21 next: 1000 dvx: 0 dvy: 0 dvz: 0 centerx: 24 centery: 141 hit_a: 0 hit_d: 0 hit_j: 0 <frame_end>

and here is the sprite



hope U can help.

[empirefantasy]

that is the opointed object:

DC-Code: <bmp_begin> file(0-29): sprite\sys\kuam4.bmp w: 158 h: 159 row: 10 col: 3 <bmp_end>         <frame> 12 flying pic: 21 state: 3005 wait: 1 next: 12 dvx: 0 dvy: 0 dvz: 0 centerx: 24 centery: 141 hit_a: 0 hit_d: 0 hit_j: 0 <frame_end> <frame> 13 flying pic: 22 state: 3005 wait: 1 next: 14 dvx: 0 dvy: 0 dvz: 0 centerx: 24 centery: 141 hit_a: 0 hit_d: 0 hit_j: 0 <frame_end> <frame> 14 flying pic: 23 state: 3005 wait: 21 next: 1000 dvx: 0 dvy: 0 dvz: 0 centerx: 24 centery: 141 hit_a: 0 hit_d: 0 hit_j: 0 <frame_end>

and here is the sprite

Here is not any sprite.


Are these 3 frames after each-other?
Maybe the problem is that you have let next: 12 in frame 12.While next in frame 12 should be 13.

Maybe the correct

DC-Code: <frame> 12 flying pic: 21 state: 3005 wait: 1 next: 13 (not 12) dvx: 0 dvy: 0 dvz: 0 centerx: 24 centery: 141 hit_a: 0 hit_d: 0 hit_j: 0 <frame_end> <frame> 13 flying pic: 22 state: 3005 wait: 1 next: 14 dvx: 0 dvy: 0 dvz: 0 centerx: 24 centery: 141 hit_a: 0 hit_d: 0 hit_j: 0 <frame_end>

[A-Man]

that is the opointed object:

DC-Code: <bmp_begin> file(0-29): sprite\sys\kuam4.bmp w: 158 h: 159 row: 10 col: 3 <bmp_end>         <frame> 12 flying pic: 21 state: 3005 wait: 1 next: 12 dvx: 0 dvy: 0 dvz: 0 centerx: 24 centery: 141 hit_a: 0 hit_d: 0 hit_j: 0 <frame_end> <frame> 13 flying pic: 22 state: 3005 wait: 1 next: 14 dvx: 0 dvy: 0 dvz: 0 centerx: 24 centery: 141 hit_a: 0 hit_d: 0 hit_j: 0 <frame_end> <frame> 14 flying pic: 23 state: 3005 wait: 21 next: 1000 dvx: 0 dvy: 0 dvz: 0 centerx: 24 centery: 141 hit_a: 0 hit_d: 0 hit_j: 0 <frame_end>

and here is the sprite

Here is not any sprite.


Are these 3 frames after each-other?
Maybe the problem is that you have let next: 12 in frame 12.While next in frame 12 should be 13.

Maybe the correct

DC-Code: <frame> 12 flying pic: 21 state: 3005 wait: 1 next: 13 (not 12) dvx: 0 dvy: 0 dvz: 0 centerx: 24 centery: 141 hit_a: 0 hit_d: 0 hit_j: 0 <frame_end> <frame> 13 flying pic: 22 state: 3005 wait: 1 next: 14 dvx: 0 dvy: 0 dvz: 0 centerx: 24 centery: 141 hit_a: 0 hit_d: 0 hit_j: 0 <frame_end>

Sorry for the late reply,
I don't think that is the problem or it would at least show pic: 12.
and here is the sprite:

[Marshall]

h: 159
that's wrong

the image's height is 478, which can't even be divided by 3 (col: 3), obviously the sprite won't show

>No, there is no problem with the height ,width ,col and row.
I checked many times for that.
check carefully and you'll only need to do it once

[Silverthorn]

w: 158 h: 159 row: 10 col: 3

So estimated dimensions of the image would be:

Width: (158+1) * 10 = 1590px
Height: (159+1) * 3 = 480px

Always remember the extra-pixel-row/column that is reserved for separating sprites. That is also the reason why the neon-green lines in Template's spritesheet don't show up in-game. So yeh, guess that'll fix it

[A-Man]

GOD, DAMN IT!!!!!
IT WORKED!
How in blazes can this simple thing cause the problem,I have been trying to fix it for hours and hours.
Thanx to U guys, you are awesome!!!

off topic: why can't I give a reputation.

Marshall edited this post 07-12-2011 11:55 AM because:

you're welcome. And the rep system has been removed