Archive: 11 posts

---

If you give a Tag a name, does that over-ride the colour setting? Do colour & name both have to match, or is just the name enough?

2011-01-26 23:39:00 Author: Bovrillor Posts: 309

---

The color and the name must match for the sensor and the tag to talk to each other. I believe that you if you do not specify a tag name but just color for your sensor then all tags of that color, regardless of name will activate it while a sensor of specific color and name will only activate when you have that exact combination.

2011-01-26 23:47:00 Author: Trindall Posts: 297

---

Wow, that's actually rather interesting - especially the bit about sensors ignoring a tag's name if they don't require one.

2011-01-27 00:04:00 Author: Bovrillor Posts: 309

---

Wow, that's actually rather interesting - especially the bit about sensors ignoring a tag's name if they don't require one. I had a setup that was using green tags with names for each function but when I wanted to test a one-off idea i just put a tag sensor in with the color green but with no name. When I played with the controls I saw that any green tag was activated that my one-off tag also got activated. Possibly I'm mixing up what I saw and what was actually built but it does make a bit of sense to me. Using a color with no name on your sensor gives you basically a OR of all of the other named inputs of that color which could be handy in some applications.

2011-01-27 00:38:00 Author: Trindall Posts: 297

---

Yeah, there are certain applications where that could save a good chunk of thermo!

2011-01-27 14:48:00 Author: Bovrillor Posts: 309

---

You need both color and label. Also, a tag sensor sensing normal green tags won't sense a green tag labeled, "Blah," for instance. A tag sensor sensing green tags labeled "Blah," for instance, does not sense a normal green tag.

2011-06-16 16:10:00 Author: L1N3R1D3R Posts: 13447

---

not that it matters most of the time, but the system starts getting buggy after 100 tags.

2011-06-16 17:37:00 Author: Unknown User

---

not that it matters most of the time, but the system starts getting buggy after 100 tags. It still works ok. If you hold your cursor over the tag, you get the correct name, but if you go to edit the tag, it'll show something else. On the level I'm working on now, I've probably got more than 200 tag names!!

2011-06-17 07:25:00 Author: Ali_Star Posts: 4085

---

It still works ok. If you hold your cursor over the tag, you get the correct name, but if you go to edit the tag, it'll show something else. On the level I'm working on now, I've probably got more than 200 tag names!! If this is starting to bother you, you may be able to reduce tags: instead of "option01", "option02", "option03", etcetera, you can use one tag named "options", feed it with an ana.log signal (i.e. put a counter in front of it) and intercept it with a tag sensor set to Signal Strength. Decoding that ana.log signal back to split values, you can use a positional sequencer with batteries spanning the value ranges on the sequencer's canvas. This works best for transmitting properties that have an exclusive value range, like weapon01/02/03 or difficulty01/02/03. Also, there appears to be a little bit of latency involved wiring it through a sequencer.

2011-06-17 11:53:00 Author: Antikris Posts: 1340

---

If this is starting to bother you, you may be able to reduce tags: instead of "option01", "option02", "option03", etcetera, you can use one tag named "options", feed it with an ana.log signal (i.e. put a counter in front of it) and intercept it with a tag sensor set to Signal Strength. Decoding that ana.log signal back to split values, you can use a positional sequencer with batteries spanning the value ranges on the sequencer's canvas. This works best for transmitting properties that have an exclusive value range, like weapon01/02/03 or difficulty01/02/03. Also, there appears to be a little bit of latency involved wiring it through a sequencer. You may as well have been speaking Dutch, haha! I'm not that advanced with my logic I'm afraid. I've never used a tag set to "Signal strength".... I'm guessing this is to do with how close they are? I don't really understand all this about having batteries set to certain percentages, split values etc. Thanks for your help anyway. Most of the logic for the main part of my level is done, so I don't need to worry about that anymore, I'm just doing the final touches regarding presentation etc. I hope this does better than my last level :/

2011-06-17 13:34:00 Author: Ali_Star Posts: 4085

---

You may as well have been speaking Dutch, haha! As a matter of fact, I really do speak dutch. I'm not that advanced with my logic I'm afraid. I've never used a tag set to "Signal strength".... I'm guessing this is to do with how close they are? I don't really understand all this about having batteries set to certain percentages, split values etc. No, it is not proximity (that is what I thought first as well, with a LBP1 mindset). Normal setting detects whether there is a tag present (or whether it has a signal and is considered 'ON&apos. Signal Strength means the strength of the signal that goes into a tag that is present; for instance, you hook a counter set to 5 of 10 into a tag, then the sensor of that tag (set to SS) will output a '50%' signal as well.

2011-06-17 14:22:00 Author: Antikris Posts: 1340

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.