Flickering problem in accelerating actor

karlpower

Hi guys,

See in video the bunch of balloons that has an accelerate (@150accel & 90deg) behaviour. The actor image is flickering while the elephant actor is being moved. The elephant actor is the main actor and is controlled by the joystick. The elephant also has the attribute scene.Camera.Origin.Y constrained to elephant.position.Y-500. The reason I have set up the control camera like this is so that the control camera is not active when the joystick is released. As you can see, the flickering stops when the joystick is released, so I can only attribute the problem to something to do with the control camera set up.

Any any any ideas?

Much appreciated.

Socks

@karlpower said:
This definitely makes sense, because as soon as I added another actor, the flickering stopped, but the new actor then flickered when he was undergoing the same accel as the balloons. Thanks socks!

Glad it worked.

I'm too lazy to go into detail but shuffling layers about and even adding in 'null' or buffer layers (actors that do nothing) usually sorts these issues out.

Information within layers permeates upwards - so imagine you have 12 layers (either 12 actual named layers or simply 12 actors in the scene) - starting with 1 at the bottom going upwards to 12 at the top . . . . now imagine you move the bottom most actor (actor A) with your mouse, and the actor at layer 2 (actor B ) follows actor A via a constrain, it will work fine as the location data only has to be passed upwards one layer (and after all the rules in layer 1 have been processed) . . .

Now swap the order, move B down to the bottom and A up to layer 2, so now when you move actor A (now at layer 2) with your mouse, the location data - before reaching B (which is now right at the bottom) needs to be passed through layer 3 then 4 then 5 then 6 then 7 then 8 then 9 then 10 then 11 then 12 then looping back around to 1 . . . . well no data really gets 'passed around', just that the rules in all these layers need to be processed/triggered before the data from layer 2 reaches layer 1 . . . .

Result = latency issues.

This issue seems more pronounced when a camera constrain is involved.

Socks

@karlpower said:
Any any any ideas?

Swap the layer order of the balloons and the elephant.

karlpower

So just whatever one is on top of the other just switch it?

karlpower

This definitely makes sense, because as soon as I added another actor, the flickering stopped, but the new actor then flickered when he was undergoing the same accel as the balloons. Thanks socks!

karlpower

Thanks for the info

Everything working better now!