Boomerang Effect bug (C3 runtime only)

I filed a bug report for this, but maybe someone can have a look at my events and let me know if I am doing something wrong.

I was using Rex's Move To plugin, but removed it and replaced with standard events since it was not going to be supported with the new C3 runtime.

The series of events is working perfectly in C2 runtime, but when you enable C3 runtime, it doesn't work at all. Hopefully it is a bug that can be fixed, but if someone sees something funky with my events, let me know.

Bug report on Github is here:

https://github.com/Scirra/Construct-3-bugs/issues/2420

KENYONB You forgot to untick the Bullet properties >>>Set Angle

If you untick that it should work on both C2/c3

About MoveTo:

-chadorireborn Ported to C3 Run Time it was just one feature missing the Target by UID

https://www.construct.net/en/forum/construct-3/plugin-sdk-10/construct-3-runtime-a-few-cons-137539

-Swell if you are interested you can vote on here for MoveTo to be included on C3 as stand-alone Behaviour

https://construct3.ideas.aha.io/ideas/C3-I-574

I dont why it keeps replacing the Link so I will posted normal construct3.ideas.aha.io/ideas/C3-I-574

tarek2 you're right. un-ticking Set Angle fixes it. THANK YOU.

but why does my current setup work on C2 runtime and not C3 runtime?

and yes, I agree Move To should be separate from Tween in C3 and added as its own standalone behavior. Rex's Move To was so useful and I miss it. I've voted. I hope the Construct crew will listen and add it.

Thanks again for the quick help.

tarek2 you're right. un-ticking Set Angle fixes it. THANK YOU.

No problem mate I'm glad to help

but why does my current setup work on C2 runtime and not C3 runtime?

If I have to guess I would say that C2 Run Time is the one that behaves strange as when you tick the "Set Angle" Construct it will keep setting the Object's Angle to the Angle of motion and taking your capx as an example when "boomerang_move" collides with "boomerang_target" it never stops moving so it should carry on moving to that Angle of Motion like the C3 Run Time does I guess, at least this is how I understood it.

But don't take my word as 100% accurate as this is just me guessing I would love to hear the proper explanation of why from one of the Scirra Team

One thing I know for sure if you are going to manipulate the Angle of Motion on the Run Time is best to Untick the "Set Angle" so you have the freedom to change the Angles of Motion on Run-Time however you like other ways you will have the bullet behaviour trying to set the objects Angle and also your events trying to set the Object's Angle swell conflicting and causing unexpected Results like this one.

and yes, I agree Move To should be separate from Tween in C3 and added as its own standalone behavior. Rex's Move To was so useful and I miss it. I've voted. I hope the Construct crew will listen and add it.

Thanks again for the quick help.

Awesome Thank you mate,

I also hope this Time they include it as the last Pull Voting for MoveTo if I remember correctly it riched up to 40+Votes, it's definitely very useful and I see very often people asking for it here around the Forums.

But don't take my word as 100% accurate as this is just me guessing I would love to hear the proper explanation of why from one of the Scirra Team

I think it might be a bug. Events should override the set angle tick. but hopefully I get an answer from my bug report sometime this week. We'll see.

Awesome Thank you mate,

I also hope this Time they include it as the last Pull Voting for MoveTo if I remember correctly it riched up to 40+Votes, it's definitely very useful and I see very often people asking for it here around the Forums.

Mee too and I remember! I requested the official Move To behavior before they merged it with Tween:

https://construct3.ideas.aha.io/ideas/C3-I-440

I was disappointed when they merged it with Tween. Move To was just perfect for what it was. It cut the number of events in half in order to do the boomerang effect in my example file. We'll see what happens.

Mee too and I remember! I requested the official Move To behavior before they merged it with Tween:

https://construct3.ideas.aha.io/ideas/C3-I-440

I was disappointed when they merged it with Tween. Move To was just perfect for what it was. It cut the number of events in half in order to do the boomerang effect in my example file. We'll see what happens.

Hhaha is true I didn't even release that it was you who created the Pool, I got bad memory man that is the one I was talking about :)

Indeed you will save Events and Collisions Checks, I saw in your example that you check Collisions in two Events so yeah that will be cool let's see.

let's spread the word for more votes!

Ashley fixed the Set Angle bug for bullet in r130

github.com/Scirra/Construct-3-bugs/issues/2420

So now it behaves just like C2 runtime as expected.

Ashley fixed the Set Angle bug for bullet in r130

https://github.com/Scirra/Construct-3-bugs/issues/2420

So now it behaves just like C2 runtime as expected.

Nice! so it was C3 then the one faulty :)

let's spread the word for more votes!

Yeah man Facebook, Twitter, youtube etc...hehe

To be honest we should get some of the votes from the Pull that made 40+ that will be fair for us as it took one year almost to collect those 40+ votes we shouldn't have to start from the beginning but heee that's Life in it :)

> let's spread the word for more votes!

Yeah man Facebook, Twitter, youtube etc...hehe

To be honest we should get some of the votes from the Pull that made 40+ that will be fair for us as it took one year almost to collect those 40+ votes we shouldn't have to start from the beginning but heee that's Life in it :)

Agreed. They really should reopen that idea and unmerge from Tween and merge with the new idea.