Ball direction (up/down) (dvz)

[Gad]

Ok.
The problem is:
I wanna make my character opoint a ball that may be going down, up, or normally depends on what player presses. Simple - like davis makes his balls, he can decide where do they go.

I dunno how to make it work. My character creates a ball, but I can't control it in dvz moving.

BALL (Click to View)

DC-Code: <frame> 5 flying pic: 36 state: 3005 wait: 1 next: 6 dvx: 20 dvy: 0 dvz: 15 centerx: 30 centery: 24 hit_a: 0 hit_d: 0 hit_j: 0 itr: kind: 0 x: 26 y: 0 w: 20 h: 10 dvx: 7 fall: 20 arest: 6 bdefend: 10 injury: 30 itr_end: bdy: kind: 0 x: 26 y: 0 w: 20 h: 24 bdy_end: <frame_end>   <frame> 6 flying pic: 37 state: 3005 wait: 1 next: 7 dvx: 20 dvy: 0 dvz: 15 centerx: 30 centery: 24 hit_a: 0 hit_d: 0 hit_j: 0 itr: kind: 0 x: 26 y: 20 w: 20 h: 10 dvx: 7 fall: 20 arest: 6 bdefend: 10 injury: 30 itr_end: bdy: kind: 0 x: 26 y: 12 w: 20 h: 24 bdy_end: <frame_end>   <frame> 7 flying pic: 38 state: 3005 wait: 1 next: 5 dvx: 20 dvy: 0 dvz: 15 centerx: 30 centery: 24 hit_a: 0 hit_d: 0 hit_j: 0 itr: kind: 0 x: 26 y: 20 w: 20 h: 10 dvx: 7 fall: 20 arest: 6 bdefend: 10 injury: 30 itr_end: bdy: kind: 0 x: 26 y: 12 w: 20 h: 24 bdy_end: <frame_end>

opoint frame (Click to View)

DC-Code: <frame> 284 BALL pic: 94 state: 3 wait: 1 next: 285 dvx: 3 dvy: 0 dvz: 0 centerx: 44 centery: 78 hit_a: 0 hit_d: 0 hit_j: 0 bdy: kind: 0 x: 26 y: 12 w: 27 h: 68 bdy_end: opoint: kind: 1 x: 75 y: 78 action: 5 dvx: 0 dvy: 0 dvz: 15 oid: 10012 facing: 0 opoint_end: itr: kind: 0 x: 17 y: 35 w: 50 h: 13 dvx: 7 dvy: -7 fall: 70 vrest: 7 bdefend: 50 injury: 30 itr_end: sound: data\020.wav <frame_end>

[Rhino.Freak]

i have the similar problem.. btw the dvz value in ball frames are too high.. try using 5 or so?

[mfc]

Can't u figure it out by checking the balls from original LF2?

But as i remember you could only apply the z-direction control by starting the ball frame from frame 0.

[TheFreeze]

You have to add a certain number in the hit_j: tags of the ball. 1-49 will make it go up and 51 to 99 (if I remember correctly) will make it go down. 0 and 50 will have no effect. I hope I could help.

[A-Man]

You have to add a certain number in the hit_j: tags of the ball. 1-49 will make it go up and 51 to 99 (if I remember correctly) will make it go down. 0 and 50 will have no effect. I hope I could help.

He didn't mean that. He meant if U pressed up when conducting the ball, the ball will move up(to the left of the player), and if U pressed down when conducting the ball, the ball will move down(to the right of the player).

Can't u figure it out by checking the balls from original LF2?

But as i remember you could only apply the z-direction control by starting the ball frame from frame 0.

No, I am very sure that it can be used in any frame. Every thing in his frames is right. I really wonder what the problem is.
@Gad, try using a different EXE, or maybe changing the ball id.
Plus, whats the ball type????

[bashscrazy]

IIRC state 3005 balls can't be moved in that fashion.
You can always add a chase effect to it? I think? IDK

[mfc]

If its because of state; start the ball with state 3006 then let it continue with 3005.

[Gad]

If its because of state; start the ball with state 3006 then let it continue with 3005.

Changed state to 3000 and tried 3006 too. Doesn't work

You have to add a certain number in the hit_j: tags of the ball. 1-49 will make it go up and 51 to 99 (if I remember correctly) will make it go down. 0 and 50 will have no effect. I hope I could help. :)

Learn to read, please.

Can't u figure it out by checking the balls from original LF2?

Maybe you will do that and tell me what do I do wrong then, cause I can't see any difference.

But as i remember you could only apply the z-direction control by starting the ball frame from frame 0.

Tried that and it doesn't help.

How it looks now (Click to View)

DC-Code: <frame> 0 flying pic: 36 state: 3000 wait: 1 next: 1 dvx: 4 dvy: 0 centerx: 30 centery: 24 hit_a: 0 hit_d: 0 hit_j: 0 itr: kind: 0 x: 26 y: -12 w: 45 h: 24 dvx: 7 fall: 20 arest: 6 bdefend: 10 injury: 30 itr_end: bdy: kind: 0 x: 26 y: -12 w: 45 h: 24 bdy_end: <frame_end>   <frame> 1 flying pic: 37 state: 3000 wait: 1 next: 2 dvx: 5 dvy: 0 centerx: 30 centery: 24 hit_a: 0 hit_d: 0 hit_j: 0 itr: kind: 0 x: 26 y: -12 w: 45 h: 24 dvx: 7 fall: 20 arest: 6 bdefend: 10 injury: 30 itr_end: bdy: kind: 0 x: 26 y: -12 w: 45 h: 24 bdy_end: <frame_end>   <frame> 2 flying pic: 38 state: 3000 wait: 1 next: 3 dvx: 15 dvy: 0 centerx: 30 centery: 24 hit_a: 0 hit_d: 0 hit_j: 0 itr: kind: 0 x: 26 y: -12 w: 45 h: 24 dvx: 7 fall: 20 arest: 6 bdefend: 10 injury: 30 itr_end: bdy: kind: 0 x: 26 y: -12 w: 45 h: 24 bdy_end: <frame_end>   <frame> 3 flying pic: 37 state: 3000 wait: 1 next: 2 dvx: 15 dvy: 0 centerx: 30 centery: 24 hit_a: 0 hit_d: 0 hit_j: 0 itr: kind: 0 x: 26 y: -12 w: 45 h: 24 dvx: 7 fall: 20 arest: 6 bdefend: 10 injury: 30 itr_end: bdy: kind: 0 x: 26 y: -10 w: 45 h: 24 bdy_end: <frame_end>

[Whaat]

I have had same problem but don't remember how i fixed it xp maybe it was like this:
Opoint frame:
<frame> 284 BALL
pic: 94 state: 3 wait: 1 next: 285 dvx: 3 dvy: 0 dvz: 1 centerx: 44 centery: 78 hit_a: 0 hit_d: 0 hit_j: 0
dvz: 0->1
Not sure, but i would try that. Also i'm not sure is that dvz 15 too much? Maybe you should try smthing like dvz 2 and check does that work.

[Ramond]

^ I think that will enable the character to move on the z-axis in the frame when he creates the ball.

I've had a little conversation about this with BP before (I was wondering myself), and we (or he) came to the conclusion that it is id-specific if you can control a created-ball's z movement or not. What you could try simply for testing purposes is to create the ball from an existing id that is able to be z-controlled, just from another frame. Perhaps it'd even be possible to let it "transform" into it's correct ball then?