Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
a prob at ball hit frames
#1
hi all, can you help me please?

i create a ball that can move forward, then skyward, then backward (not boomerang moves)
when i test it at beta, it work normally, but when i reach frame 17, it disappear, why? (i have test other balls without 10, 20, 30, and 40 hit and disappear frames and it work succesfully at other balls)
this is da code:
Shin Hanazumi
The Second Flower of Hanazumi Kazoku
Junior Data Changer
Reply
Thanks given by:
#2
Eventually the images are incorrect? Can't see a flaw in the code itself.
My Creations: (Click to View)

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


Greetz,
Alblaka
Reply
Thanks given by:
#3
(10-07-2011, 10:58 AM)Alblaka Wrote:  Eventually the images are incorrect? Can't see a flaw in the code itself.

no, not the images, if only da images, its shadow wont disappear, but in this case, the shadow follow the images to disappear, so like... hmm, missing frame
Shin Hanazumi
The Second Flower of Hanazumi Kazoku
Junior Data Changer
Reply
Thanks given by:
#4
You have state:3005, the shadow isn't visible.

Unless your grammatically confusing sentence above is meant to say "It suddenly has a shadow, indicating a missing frame issue".
My Creations: (Click to View)

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


Greetz,
Alblaka
Reply
Thanks given by:
#5
(10-07-2011, 11:13 AM)Alblaka Wrote:  You have state:3005, the shadow isn't visible.

Unless your grammatically confusing sentence above is meant to say "It suddenly has a shadow, indicating a missing frame issue".

hmm, sorry my english is bad, i mean..
umm when i enter and change the next to 17, or higher, the ball is disappear, not only at pic: 4
Shin Hanazumi
The Second Flower of Hanazumi Kazoku
Junior Data Changer
Reply
Thanks given by:
#6
I'd recommend to abandon any hard-coded property-frames (that is: 0, 10, 20, 30, 40, 50, 60). There are some random "bugs" caused by frames that automatically kill the object after their execution (I think, frame 100 or so acts similar), create ice-chunks (frame ~200), and so on. Try to shift the whole sequence out to some unused areas to see if that helps ;)
Silverthorn / Blue Phoenix
~ Breaking LFE since 2008 ~

"Freeze, you're under vrest!" - Mark, probably.

» Gallery | » Sprites | » DeviantArt
Reply
Thanks given by:
#7
I thought that no one will write the right solution for a moment. But at least bp solved it:p

semi-offtopic:
and ice shattering problem in frame 200 can be solved. If the frame before the frame 200 doesn't have state 13; shatter effect happens.
[Image: llqsMqz.jpg][Image: llqsMqz.jpg][Image: llqsMqz.jpg][Image: llqsMqz.jpg]
Reply
Thanks given by:




Users browsing this thread: 2 Guest(s)