Little Fighter Empire - Forums
[solved] dvz-ing opoint? - Printable Version

+- Little Fighter Empire - Forums (https://lf-empire.de/forum)
+-- Forum: Little Fighter 2 Zone (https://lf-empire.de/forum/forumdisplay.php?fid=7)
+--- Forum: Data Changing (https://lf-empire.de/forum/forumdisplay.php?fid=11)
+---- Forum: Solved Problems (https://lf-empire.de/forum/forumdisplay.php?fid=14)
+---- Thread: [solved] dvz-ing opoint? (/showthread.php?tid=2852)

[solved] dvz-ing opoint? - vandesdelca - 05-10-2009

sry for spamming at the thread but... i don't know why, why do my DC-ed stuff always have some problems:(
and now when i opointed object that opoint another object and so on, the opoint kinda strange
it looks like this:
Spoiler (Click to View)
i'm sure the centery and centex of the object was right, cus when i activate the object at the lowest of the BG, the opoint is normal =====>
so... is there a problem with the data?
Spoiler (Click to View)


RE: dvz-ing opoint? - Alblaka - 05-10-2009

The balls fly "down" if you are somewhere, but "straight" if you are on the lowest bg part?

> Your T3s can be affect by dvz (pressing up/down) and therefore fly further downwards or something... on the lowest edge of BG flying down isn'T possible, therefore they go straight...


I don't think, that is really the problem, but i cannot find anything else that could cause such a thing..

RE: dvz-ing opoint? - TheNave - 05-10-2009

Is the combination DvJ or DvA, if yes then when you press these buttons at the same time the opoint can be affected by the "down"-button so it flies down on the z-axis

to solve this add a dvz: 550 in the first frame of your ball

RE: dvz-ing opoint? - Azriel - 05-10-2009

sourcecode related. when u opoint an object, its z value is always opointer's z + 1.

to fix this, just use hit_j: thingy. in the first frame, do wait: 0 (or maybe it's 1? try it) and hit_j: 49.and 2nd frame make it hit_j: 50 (to stop the z movement).



Azriel~

RE: dvz-ing opoint? - vandesdelca - 05-10-2009

(05-10-2009, 09:21 AM)TheNave Wrote:  Is the combination DvJ or DvA, if yes then when you press these buttons at the same time the opoint can be affected by the "down"-button so it flies down on the z-axis

to solve this add a dvz: 550 in the first frame of your ball

the combination is D>JA.
@azriel:
do i really have to set that hit_j thing? using dvz 550 isn't the solution?
and which hit_j: is the faster? 49?

problem screenshots:
Spoiler (Click to View)


RE: dvz-ing opoint? - no one - 05-10-2009

Quote:do i really have to set that hit_j thing? using dvz 550 isn't the solution?
Both of them will work.

Quote:and which hit_j: is the faster? 49?
Compare to what?
Anyway, Test it out, you'll know the result.

RE: dvz-ing opoint? - Azriel - 05-10-2009

i doubt dvz: 550 works. as i said, the sourcecode automatically makes the z value of any opointed object 1 + the z value of the object that is creating it.

hit_j: 48 means move up 2 px every time unit.
hit_j: 49 means move up 1 px every time unit.
hit_j: 50 is the middle (stop movement)
hit_j: 51 means move down 1 px every time unit.
hit_j: 52 means move down 2 px every time unit.



Azriel~