Build 293.10 - Release version

Quick update: build 293.6 is available.

did you get a chance to look at the object selection/scoping bug I found? it seems really strange to me at least :)

What was this, please? I released an update on 293.5 for Android that uses multi-touch, is this something I need to worry about?

Quote:

---

Android: fix in Multiple Touch object, not behaving like the PC version.

---

If you are not using multi touch true conditions as not first event then test your application with new version. If only multi touch conditions as first event nothing to worry about it

Found another bug with child events!

Seems the old bug (I think?) with just having a "break" action as the only action in a child event does not work when running as exe. (It works when running from editor)

I've isolated and made an example, this does not work for me at least using the latest build (293.6)

Attachment 30380

@SirEatAlot basically a lone Break works the same as a call to a non-existent loop, it's just disabled and discarded during building build.
It simply thinks it has no actions. Of course this shouldn't work this way, but that's the explanation.
Same happens on events that only has Debugger actions for example.

Quote:

---

Originally Posted by NaitorStudios

@SirEatAlot basically a lone Break works the same as a call to a non-existent loop, it's just disabled and discarded during building build.
It simply thinks it has no actions. Of course this shouldn't work this way, but that's the explanation.
Same happens on events that only has Debugger actions for example.

---

Hmm that makes no sense to me? Doing a break somewhere in a chain multiple of child events should break that chain, I can't see how this would the same as calling an empty loop? But maybe it's just me..

That's the point, it shouldn't.
Since it's isn't doing anything to any object, variable or option, it gets deleted for "Optimization purposes".
Probably just a overlook, Fusion by defaults removes any "blank" event during building.

Quote:

---

Originally Posted by NaitorStudios

That's the point, it shouldn't.
Since it's isn't doing anything to any object, variable or option, it gets deleted for "Optimization purposes".
Probably just a overlook, Fusion by defaults removes any "blank" event during building.

---

Ok so it is probably a bug then.. I get that actions like debug outputs gets deleted since they have no effect on the execution of the code, but a "break" event can of course be very important even if it's not directly connected a specific object.

What I end up doing now is insert "fake" actions that sets a temp global value to 0 just to ensure the break events actually triggers X)

BUG:

calling a loop that doesn't exist or a loop with no actions now causes the application to crash >__<