Archive: 16 posts

---

Is there a way to achieve this? Basically, I have a timer which sends a out a pulse every 0.1 seconds. Is there a way to make it even quicker?

2011-07-25 12:18:00 Author: Ali_Star Posts: 4085

---

What like 0.01 seconds? No but why would you need it quicker?

2011-07-25 12:39:00 Author: craigmond Posts: 2426

---

you can wire a NOT gate into itself. this will make it on for one frame, off for one frame on for one frame and keeps going like that. i think a timer set to 0.1 is one pulse after the 3rd frame then takes a frame to reset. you could also use a 2 port selector with both outputs wire back into the opposite input so you get the inverted output aswell

2011-07-25 12:41:00 Author: evret Posts: 612

---

What like 0.01 seconds? No but why would you need it quicker? Well, I was thinking of about half the speed, so about 0.05s. But I have my reasons.... and they're super secret you can wire a NOT gate into itself. this will make it on for one frame, off for one frame on for one frame and keeps going like that. i think a timer set to 0.1 is one pulse after the 3rd frame then takes a frame to reset. you could also use a 2 port selector with both outputs wire back into the opposite input so you get the inverted output aswell Cheers, will give that a go. EDIT: Works a charm. Thanks.

2011-07-25 12:55:00 Author: Ali_Star Posts: 4085

---

You could also use a sequencer dividing 0.1 seconds into 4, so 0.025s intervals. Not sure what the frame counts are for that. There are some issues when using it like this though. Example, using an OR gate with a pulse every 0.05 seconds (4 batteries into OR gate), produced a constant signal, even though there were times when no battery had power.

2011-07-25 20:12:00 Author: SSTAGG1 Posts: 1136

---

or you can use a counter that is wired to its on reset. that way its only one simulation frame which is much faster that 0.1s. Basically a counter is more precise than a not gate because it will activate only as many times as you want it to.

2011-07-25 22:47:00 Author: LBP2_Tutorialist Posts: 225

---

one simulation frame which is much faster that 0.1s. Just FYI, one clock cycle in lbp is .033 seconds, or 1/3 of .1 second.

2011-07-26 03:55:00 Author: Sehven Posts: 2188

---

or you can use a counter that is wired to its on reset. that way its only one simulation frame which is much faster that 0.1s. Basically a counter is more precise than a not gate because it will activate only as many times as you want it to. I might give this method a crack. The above method that I tried (evrets method), after further investigation, had a side effect that made it useless for my situation.

2011-07-26 08:58:00 Author: Ali_Star Posts: 4085

---

I might give this method a crack. The above method that I tried (evrets method), after further investigation, had a side effect that made it useless for my situation. Sounds to me like it'd produce identical results to the fedback NOT gate. What's this undesirable "side effect" of which you speak?

2011-07-26 14:47:00 Author: Aya042 Posts: 2870

---

Sounds to me like it'd produce identical results to the fedback NOT gate. What's this undesirable "side effect" of which you speak? I was thinking that it'd be identical, but there's no harm in giving it a try. It's not a must anyway. If I can't achieve the affect I want, I'm not gonna lose any sleep over it, I'll just stick with 0.1. The side effect... I think is due to anything less than 0.1 being too quick for it to handle, so something doesn't happen when it's supposed to. It's all super secret though. So secret that it's gonna change the face of LBP2 gaming for ever! Well.....no, but hopefully it'll get more plays than my last couple of levels .

2011-07-26 15:09:00 Author: Ali_Star Posts: 4085

---

if the NOT gate is too fast you can use a 3 port selector, wire the top into the middle, middle into the bottom, and bottom into the top, then use any of the outputs. this should be slightly faster than 0.1, but slower than the NOT loop

2011-07-26 15:23:00 Author: evret Posts: 612

---

if the NOT gate is too fast you can use a 3 port selector... ...which is actually the only other possible pulse frequency between the fedback NOT gate and the self-resetting 0.1s timer. Due to the nature of the simulation engine, all events are quantized to 30Hz, which only gives you so many options for pulse frequencies. The fastest rate at which a single wire can oscillate is 15Hz, which you can get in a number of ways - the fedback NOT gate being the simplest. The selector approach mentioned above is probably the easiest way to get all possible pulse frequencies, i.e.... Two ports = 15Hz Three ports = 10Hz Four ports = 7.5Hz Five ports = 6Hz Six ports = 5Hz ...from which you can easily spot that the frequency (in Hz) is just 30 divided by the number of ports. The self-resetting 0.1s timer does not (as you might expect) give 10Hz, since it takes an additional frame to reset itself, so it actually only gives 7.5Hz, making it equivalent to a four-port selector.

2011-07-26 15:49:00 Author: Aya042 Posts: 2870

---

A counter set to one, and wired to its own reset is what you want. It can be triggered by a button press, or a switch, and times 0.033 seconds, which is just about what you are looking for...

2011-07-26 15:58:00 Author: poorjack Posts: 1806

---

You can also use 30Hz with I/O chained feedbacked selector for animation... but only for animation

2011-07-26 15:58:00 Author: Shadowriver Posts: 3991

---

...which is actually the only other possible pulse frequency between the fedback NOT gate and the self-resetting 0.1s timer. Due to the nature of the simulation engine, all events are quantized to 30Hz, which only gives you so many options for pulse frequencies. The fastest rate at which a single wire can oscillate is 15Hz, which you can get in a number of ways - the fedback NOT gate being the simplest. The selector approach mentioned above is probably the easiest way to get all possible pulse frequencies, i.e.... Two ports = 15Hz Three ports = 10Hz Four ports = 7.5Hz Five ports = 6Hz Six ports = 5Hz ...from which you can easily spot that the frequency (in Hz) is just 30 divided by the number of ports. The self-resetting 0.1s timer does not (as you might expect) give 10Hz, since it takes an additional frame to reset itself, so it actually only gives 7.5Hz, making it equivalent to a four-port selector. Does this kinda relate to the fact that (if I remember correctly) small grid size movement relates to a mover set at 100% accel and deaccel, and speed 7.5 (activated with a pulse)?

2011-07-26 16:33:00 Author: Ali_Star Posts: 4085

---

Does this kinda relate to the fact that (if I remember correctly) small grid size movement relates to a mover set at 100% accel and deaccel, and speed 7.5 (activated with a pulse)? Nope. It's just coincidental.

2011-07-26 16:38:00 Author: Aya042 Posts: 2870

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.