Report this content
We want the Dreams coMmunity to be a safe, diverse and tolerant place for everyone, no matter their age, gender, race, sexual orientation or otherwise. If you believe this content to contradict these principles, you can file a report for our coMmunity teams to investigate.
Note that misuse of the reporting tool will not be tolerated.Item being reported:
I tried making my own logic for this kind of behaviour, and managed to do it without too much setup. Until this is something built-in, I thought I'd leave links to it here, in case people find it useful.
https://indreams.me/scene/dWorUXrzRJp
My setup is... somewhat simple. But there are a couple of key aspects to this setup that may not be obvious, and may be worth knowing about if you have problems using it:
- The ex-gate for re-queuing will open only when the queued stuff has been run through. So it will only re-queue everything once the queue is all done.
- Also, each iteration (plus re-queuing) takes 1 frame.
- Technically the data comes out 1 frame after its iteration, but in practise that's probably not a big deal. You could use variables/keyframes to remove that delay if you needed to.
- Wiring the "active" signal into its own "close gate" can cause a condition where the gate doesn't close itself in some situations. Wiring the active signal through something else first can change the order things are processed and avoid that issue.