Recent content by Amitloaf

Yes, i'm sure something is wrong. I will make a video. Thank you!

Please help. I sat and played with it for a while and it seems like it involves some sort of bug. It works ok normally but when I have a composite inside another composite when the outer composite is of a lower priority abort type iand the internal is a self abort type, that's when it breaks. It...

Also - What's weird for me, is that it didn't switch from Success to Failure. It was on failure immediately when the Idle task started. It might have been returning success before, but it's not on this iteration on Idle

But then i'll have to flip it anyway, won't I? So it actually returns true. I'm just wondering. I can use the interrupts but it's still weird for me as failure will never go into a task.

Yes - why would I want a lower priority abort to abort a task on failure? If it fails obviously it won't be able to get into the higher priority task. Right now this is exactly what happens. It aborts the lower task, evaluates, fails and goes back to the lower task, effectively doing it twice...

Also - Now i'm having the other thing around - A conditional of lower priotity returns true but doesn't abort the lower priority one. Either i'm missing something or something is really off.

I got this: 10.60923: Watcher - Watcher: Push task Idle (Idle, index 50) at stack index 0 10.94257: Watcher - Watcher: Conditional abort with task Looked At (BehaviorDesigner.Runtime.Tasks.Sequence, index 7) because of conditional task Can See (CanSee, index 8) with status Failure How can it be...