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 gotcha with this one. Remember debugging visually - if stuff lights up right from the beginning (which your thrust module does), you're checking for conditions you don't even care about. You only want the smoke to appear when you thrust, which you could easily do by just hooking the incoming signal (coming in the thrust microchip) into the emitter's off switch. Otherwise, you'd always get some result and (apparently) the emitter defaults to this location, probably because that's where it was first (I'm really just guessing here). Fact is, you're always trying to emit the smoke, but only in the correct position when you get a hit result.
Still not quite there yet because of that. Now we can see that your rocket smoke is exclusive as long as you get a result. Otherwise, we can see that one tree try to lift off again with a huge cloud below it.
So instead of what we did, I'd just use the scope's "hit something" node. Your emitter used to fire every single time you got thrust in, even if there is no surface for the smoke to bounce off. Just get an AND-gate and get "hit something" and the main signal you already wired into the emitter. Hook the gate into your emitter once more and it'll work out just as you wanted.