Archive: 3 posts

---

I thought I had this one figured out, but now I'm getting inconsistent results, and it confuses me. I think I found a bug, but I'd like some feedback before I go further. Here's the deal: It's easy enough to set the "aim at target" setting on a creatinator-enabled sackbot, and then get it to menacingly point its paintinator at a nearby matching tag. But the part that I'm having trouble with is under what circumstances does it actually fire its paint gun at that target. I thought maybe never, and that the actual firing had to be controlled with some other logic hooked up to the R1 button of a controlinator mounted on the sackbot. But then I ended up with a particular sackbot who not only fired autonomously at its target, but who also wouldn't stop firing at the tag, regardless of what I did. Even in pause mode it kept pulling the trigger, even after spending the limited ammo in the paint gun. (It just kept clicking away on the empty gun's trigger.) What's weird to me is that I could copy the 'bot in the level and repeat the behavior, but if I captured it and created a new instance from my object catalog it no longer fired at all. So, is this a bug anybody else has run into? And/or is there some way through sackbot settings to get it to shoot at targets without wiring up controlinator logic? Thanks for any feedback.

2011-02-07 23:12:00 Author: LittleBigDave Posts: 324

---

One thing I've noticed about the logic is that it does not update on it's own, instead it only updates when its input changes. So in the case of your logic holding down the trigger, I think it stops when saved as an object because it sees no change in input. An active wire does not imply flow. You should add a timer set to reset itself to get a stream of trigger presses.

2011-02-08 00:50:00 Author: Lokno Posts: 68

---

One thing I've noticed about the logic is that it does not update on it's own, instead it only updates when its input changes. So in the case of your logic holding down the trigger, I think it stops when saved as an object because it sees no change in input. An active wire does not imply flow. You should add a timer set to reset itself to get a stream of trigger presses. Thanks for the feedback. Regarding signal flow, however, I'm not sure I'd put it that way. I'm fairly sure an active wire to the R1 button drives it as if the button were being held down, and the it is left to the behavior of the device it is connected to determine if that means continuous or single fire. For instance, if I wired the R1 button to a thruster, and wired a constant signal to the R1 button, then that thruster would keep thrusting until I stopped the signal. Back to my earlier quandary, it's actually not getting the R1 button wired up that is confusing me, it's what if anything sackbots do in terms of shooting tag targets when left to their own devices. (that is, nothing is wired to the R1 button) I think the answer is they don't shoot on their own, but I might be wrong, and I have at least one transient example of a sackbot that went trigger happy on its own.

2011-02-08 04:01:00 Author: LittleBigDave Posts: 324

Posts: 1077139    Threads: 69970    Members: 9661    Archive-Date: 2019-01-19

Aus dem Archiv wurden alle persönlichen Daten wie Name, Anschrift, Email etc. - aber auch sämtliche Inhalte wie z.B. persönliche Nachrichten - entfernt.
Die Nutzung dieser Webseite erfolgt ohne Speicherung personenbezogener Daten. Es werden keinerlei Cookies, Logs, 3rd-Party-Plugins etc. verwendet.