So, while we want it to look and feel like the logic is carried by wires through the grey joints of the craft, this is programming, and these variables and such are globally accessible by all the drone bits because this is all virtual, and there exist no physical constraints unless you choose to impose them. This would allow the main drone core to send a startup command to the baby drone while the baby is still physically and logically connected to it's factory, and also allows the baby to fly free and be independent from it's future twin sibling. Unless, of course, the severed section of tree carries with it a wireless logic receiver component. When a connection in the tree is severed, whether from factory decoupling or decouplers or plain old damaged/destroyed parts, any parts down the tree branches from that point cannot send signals up through the broken tree area or receive signals from above. The desired behavior for this idea is the following: When drone parts are still physically linked to the drone core, they receive and send logic signals up and down the tree. I understand that decouplers and factories where added later in game development, and while I surely am not familiar with the game's source code, if you will let me I think I would like to try and outline a way that this could be implemented. The solution, I believe, is similar to what trying to explain - which is when a drone is decoupled, whether from factory or plain decoupler, is that the logic should be split off also. Works, but like all the methods outlined here it requires extra logic parts on the baby that become dead weight shortly after launch. Print the drone baby and eject it above the drone, and when it drifts below the drone core it would latch the on-state. This works, but now my drone baby will sometimes activate prematurely if my main drone accidentally uses some of the baby's fuel.Ī third method was to use the speed sensor, combined with jump rockets or magnets to kick the baby off to a running start, but to solve the premature activation problem I needed the main drone to be slower that I'd like.Ī fourth method was to use the distance sensor set to "own drone", and have a suitable ejection magnet so that the drone baby would turn on when it doesn't detect the parent anymore - the flaw with this method is at the start of a round the distance sensor will sometimes spawn undetected for what must be a single game tick, and the babies would turn on right away.Ī fifth method was to use the directional sensor set to drone core twisted 90 degrees. This works but is slow, and sometimes my main drone gets too warm, and newly printed drone babies would turn on too soon even with the heater off.Ī second way was to put some non-logic split thrusters on the baby drone, and have the drone activate when it detects a non-full fuel tank. One way was to put a heater on the main body that activates when the factory decouples, and a temp sensor in the logic-split part of the drone baby that turns it on when it gets warm. To get around this problem, I have resorted to a myriad of unreliable ways to kick-start my drone baby. Plus the failed latched-on signal gets transmitted from the first printed drone to the second! Worse yet, if I still want to create an activate on/off switch on the drone that switches on when the factory decouple button is pressed, it has to be downstream of the wireless connector - but if it is downstream of the wireless logic connector, it's signals are not passed to the rest of the drone baby that is sandwiched between the wireless logic connector and the upstream logic splitter. If I put a wireless receiver on the logic-split drone, all parts down stream of the wireless connector hear and transmit to the main core, and if there are two copies of the drone, then they still cross-talk each other. But if I build a logic splitter into my factory created drone, it cannot detect when the factory decouple button has been pressed, an action which I would also like to simultaneously turn the now decoupled drone-baby on.īut I cannot. The way things work now, if I want to have a deployable swarm of factory created drones, I absolutely must build them on a logic splitter, otherwise each drone cross-talks with each other and, for instance, they cannot each have a gravity sensor to stay level - the multiple copies of a gravity sensor all try to talk over each other with different readings. Right now, I am attempting to solve a very difficult problem, which is to both have a start signal for a drone, and for there to be multiple factory copies of a drone. I also think that logic shouldn't be wireless without the transmission block.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |