Garheardt the Black Posted November 8, 2018 Share Posted November 8, 2018 Hi! I suggest a logic splitter that: -only allows signals to flow in one direction. This would allow: -Bulk production and command of identical parts that can react to the environment without confusing one another. -Significantly reduced time spent programming individual parts. Thanks! Love the game! 1 Link to comment Share on other sites More sharing options...
0 Lurkily Posted November 8, 2018 Share Posted November 8, 2018 How about localizing logic so that a disconnected part doesn't need a splitter to act independently? Along with permitting signals to cross a wireless part, that would accomplish what's needed here without complicating the roster of parts with similar-but-different splitters. It would keep subdrones manufactured by a factory from crosstalking, but a wireless part to trigger logic on the subdrone, letting certain signals still be effective in controlling them. Link to comment Share on other sites More sharing options...
0 Garheardt the Black Posted November 8, 2018 Author Share Posted November 8, 2018 That could work too! Link to comment Share on other sites More sharing options...
0 Garheardt the Black Posted November 8, 2018 Author Share Posted November 8, 2018 I just programmed ten automated turrets for a battleship and either of those parts would have saved me 90% of the work! Link to comment Share on other sites More sharing options...
0 Lurkily Posted November 8, 2018 Share Posted November 8, 2018 If you can separate the turret from central control, you can put the logic opposite a splitter, and the duplicated parts won't crosstalk. The wireless part might provide control beyond a splitter, but right not it also acts as a splitter. Here's another request of mine, so that it transmits its own signals only to child parts, but child parts can transmit signals to its parents: Link to comment Share on other sites More sharing options...
0 Garheardt the Black Posted November 8, 2018 Author Share Posted November 8, 2018 Aye, good thoughts. I wanted autonomous turrets that I could still give commands to, like when to actively seek targets and later to cease and retract. I was able to get a prototype working, but had to program the individual parts one at a time. Because who wouldn't want a battleship with functional gun ports armed with retractable autonomous guns? Link to comment Share on other sites More sharing options...
0 Lurkily Posted November 8, 2018 Share Posted November 8, 2018 With the second suggestion, you could split them off, use a wireless part to transmit a signal to that part's one child, a switch, and that switch could serve as a control switch to put each turret into an active or sleep mode. Right now it's just a lot of logic and tag suffixes or prefixes. Link to comment Share on other sites More sharing options...
0 Garheardt the Black Posted November 9, 2018 Author Share Posted November 9, 2018 Interesting. I tried something similar, but the moment I put a wireless part in, the turrets started to cross talk. I wonder what I did different? Link to comment Share on other sites More sharing options...
0 Lurkily Posted November 9, 2018 Share Posted November 9, 2018 Hard to say without seeing it. In any case it can't work now- if the whole turret is a child of the wireless part, then you accomplish nothing. If only the control logic is achild of wireless, it can't talk to what it's supposed to control. Link to comment Share on other sites More sharing options...
0 Lurkily Posted November 9, 2018 Share Posted November 9, 2018 I will add that I haven't used wireless enough to be REALLY familiar with its behaviour. Link to comment Share on other sites More sharing options...
0 Garheardt the Black Posted November 9, 2018 Author Share Posted November 9, 2018 Nor I. For the most part, all I was reliably able to make it do was negate the splitter, defeating the whole point of the thing 😆 Link to comment Share on other sites More sharing options...
0 Lurkily Posted November 9, 2018 Share Posted November 9, 2018 Right now you can isolate splitter children, without isolating the wireless block's children, but you can mostly do that with creative hierarchies of connections, too. The changes I want would make both parts more versatile, but not more limited in any way, I don't think. Link to comment Share on other sites More sharing options...
0 unmog Posted November 10, 2018 Share Posted November 10, 2018 On 11/8/2018 at 5:49 AM, Lurkily said: How about localizing logic so that a disconnected part doesn't need a splitter to act independently? Along with permitting signals to cross a wireless part, that would accomplish what's needed here without complicating the roster of parts with similar-but-different splitters. It would keep subdrones manufactured by a factory from crosstalking, but a wireless part to trigger logic on the subdrone, letting certain signals still be effective in controlling them. This is what Id prefer, might as well give us more reasons to use wireless receivers for things we separate that we still want to communicate with. Link to comment Share on other sites More sharing options...
Post
Garheardt the Black
Hi! I suggest a logic splitter that:
-only allows signals to flow in one direction.
This would allow:
-Bulk production and command of identical parts that can react to the environment without confusing one another.
-Significantly reduced time spent programming individual parts.
Thanks! Love the game!
Link to comment
Share on other sites
12 replies to this post
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now