Little Fighter Empire - Forums › Little Fighter 2 Zone › Data Changing › Solved Problems v
[solved] dvz-ing opoint?

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Last Post
[solved] dvz-ing opoint?
vandesdelca Offline
Experienced Member
*
Posts: 417
Threads: 56
Joined: Jan 2009
Thanks given: 33
Thanks rec.: 77 / 46
#1
05-10-2009, 09:09 AM
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)
my current project

http://www.webtoons.com/en/challenge/gay..._no=122621

Find
Reply
Thanks given by:
Alblaka Offline
DACI-Dragon / LFE-Lurker #1
*
Posts: 1,696
Threads: 60
Joined: Jan 2009
Thanks given: 1818
Thanks rec.: 894 / 530
#2
05-10-2009, 09:16 AM
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..
My Creations: (Click to View)

Return (String) System.getNewsOfTheDay();
Barely active, expect slow responses. If at all.


Greetz,
Alblaka
Website Find
Reply
Thanks given by:
TheNave Away
Extraordinary Member
*
Posts: 1,003
Threads: 3
Joined: Mar 2008
Thanks given: 275
Thanks rec.: 609 / 418
#3
05-10-2009, 09:21 AM (This post was last modified: 05-10-2009, 09:21 AM by TheNave.)
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
Find
Reply
Thanks given by: Alblaka
Azriel Offline
heartless
Global Moderators
Posts: 1,073
Threads: 38
Joined: Mar 2008
Thanks given: 24
Thanks rec.: 767 / 348
#4
05-10-2009, 09:21 AM
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~
[Image: ZucdcMY.png]
2019/05/24: Into The Wild
Website Find
Reply
Thanks given by:
vandesdelca Offline
Experienced Member
*
Posts: 417
Threads: 56
Joined: Jan 2009
Thanks given: 33
Thanks rec.: 77 / 46
#5
05-10-2009, 09:41 AM (This post was last modified: 05-10-2009, 09:46 AM by vandesdelca.)
(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)
my current project

http://www.webtoons.com/en/challenge/gay..._no=122621

Find
Reply
Thanks given by:
no one Away
The lazy stick
*
Posts: 759
Threads: 43
Joined: Jul 2008
Thanks given: 53
Thanks rec.: 273 / 146
#6
05-10-2009, 10:42 AM
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.
Find
Reply
Thanks given by:
Azriel Offline
heartless
Global Moderators
Posts: 1,073
Threads: 38
Joined: Mar 2008
Thanks given: 24
Thanks rec.: 767 / 348
#7
05-10-2009, 07:51 PM
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~
[Image: ZucdcMY.png]
2019/05/24: Into The Wild
Website Find
Reply
Thanks given by: vandesdelca




Users browsing this thread: 2 Guest(s)