Archive: 5 posts

---

Been a while since I created a topic on here so I thought I would start with a real brain teaser.. I put together a system that relies on no specific order any tag can be on in any order and all other tags have to wait in line and that's what I need it to do. I tried feedback loops but couldn't figure out the math for it.. the math for a feedback loop is to add a percentage that when other percentages are added you don't go over 100% or the don't equal one another not so easy to do... you can use 1 3 5 7 but not 9 and you need 10 numbers the reason you cant use 9 is 1+3+5=9. Instead of using a feedback loop I put this together http://ic.lbp.me/img/ft/ccc812fac0d732a55bb3a54d7a8c31357f6d09c8.jpg the blue tag sensors on the left receive a pulse and trip a counter, the counter turns on the small color microchips on the right and waits for the selector to select it, then 10 seconds later the timer on the small microchip resets the counter.. there are 3 problems with this.. 1. it don't happen in 1 frame takes 10 frames.. 2. its not manageable or expandable without a lot of work.. 3. uses as much thermo space as a sackbot.. Now I need to lighten the load thanks for any feedback on this

2014-08-12 17:30:00 Author: JKY Posts: 119

---

If the magic mouths have user recorded audio then that will be why it uses up as much thermo as a sackbot. The rest of the logic shouldn't have any noticeable impact on it - there simply isn't enough of it. I'm sure your system could be redesigned so that it doesn't use a selector, which is the reason it takes 10 frames to happen. More details on what it does would be required to give a more useful response. It appears that it's a system that triggers different magic mouths, where if a magic mouth is triggered and another magic mouth is already active then it will wait for it to finish before starting. But I may be wrong.

2014-08-12 18:54:00 Author: fluxlasers Posts: 182

---

You are 1000% correct and there are no voice recordings but still uses that of an empty sack bot

2014-08-12 19:22:00 Author: JKY Posts: 119

---

My approach would be very different. This is what I came up with: http://i2.lbp.me/img/ft/772f54ce341122c7957e8c044484c088289bc2a3.jpg The trigger input (a player sensor here) starts the upper timer, which acts as a measure of time spent waiting to activate, and broadcasts the waiting time through the tag. The waiting time is then compared with the waiting time of other broadcasting chips in the level, and if it is higher than all the others it was in the queue the longest, so it activates the magic mouth and the lower timer to shut it off. It also broadcasts a 100% signal to make sure other waiting times don't catch up and activate before this one is done displaying. I tweaked the upper timer to 5000+ seconds, but it would be enough to just add up all the display times of the magic mouths. It's a bit messy, and not optimised. For one, if you tweak the upper time to Start Running Up you might be able to get rid of the selector, and you could leave the waiting timer running but supress the broadcast, but I'm not sure which would take up the most thermo. It's hard to make judgements about thermo at this point, because you might be looking at the texture/sticker thermo here instead. Also, I realise now that there is still the possibility of two activations in the exact same frame to deadlock the system. You could detect the deadlock (tag sensor output equals waiting timer output) and resolve it via a priority system, or maybe by letting a randomiser delay the input of the waiting timer randomly until one wins.

2014-08-13 11:51:00 Author: Rogar Posts: 2284

---

This is very well thought out example thank you very much sir

2014-08-13 12:15:00 Author: JKY Posts: 119

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.