Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[solved] Problem with cpoint 's throwing position
#1
this is the holding frame
[Image: scaled.php?server=594&filename=newbitmap...es=landing]
    DC-Code:
<frame> 295 backstabber
   pic: 106  state: 9  wait: 3  next: 296  dvx: 0  dvy: 0  dvz: 0  centerx: 39  centery: 79  hit_a: 0  hit_d: 0  hit_j: 0
  sound: data\014.wav 
   cpoint:
      kind: 1  x: 48  y: 35
      cover: 11 vaction: 135  throwvz: -842150451  throwinjury: -842150451 injury: 80
   cpoint_end:
   bdy:
      kind: 0  x: 19  y: 48  w: 48  h: 26
   bdy_end:
<frame_end>

and this is throwing frame
[Image: scaled.php?server=191&filename=newbitmap...es=landing]
    DC-Code:
<frame> 296 backstabber
   pic: 106  state: 9  wait: 1  next: 300  dvx: 0  dvy: 0  dvz: 0  centerx: 34  centery: 79  hit_a: 0  hit_d: 0  hit_j: 0
   cpoint:
      kind: 1  x: 48  y: 35
      cover: 11  vaction: 181  throwvx: -13  throwinjury: 30 
   cpoint_end:
   bdy:
      kind: 0  x: 19  y: 48  w: 48  h: 26
   bdy_end:
<frame_end>

The start-throwing position is far from the knees , how to make it nearer like the first pic
dctbullshit changed his name into Kuriza!
Reply
Thanks given by:
#2
Try increasing the y: value in frame 296 (by about 30 pixels, just test around to see it fit). I believe the big y position difference is due to that you use a different vaction in frame 296 than the available caught-frames, and thus the centery is a little off.

Alternatively, try to find the caught frame (somewhere around frame 140) which has the same pic as frame 181, then use that one as vaction in frame 296.
Quote of the Day f***ing Year (Click to View)
Reply
Thanks given by: dctbullshit




Users browsing this thread: 1 Guest(s)