If it is in 1.6 I'll be surprised. If it remains in after 1.6, even more so. PC has proven what will happen if development on MFR crawls. Someone else can ask to take it over. Elo has proven this not the case with RP2. RP2 is a dead end until that simple fact changes.
RedLogic by Immibs
- Thread starter whizzball1
- Start date
-
The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
If it is in 1.6 I'll be surprised. If it remains in after 1.6, even more so. PC has proven what will happen if development on MFR crawls. Someone else can ask to take it over. Elo has proven this not the case with RP2. RP2 is a dead end until that simple fact changes.
I have the initial pulse going off every .5 second. I could definitely optimize for more pulses per tick, but I'm going for more lighting updates per tick at the endpoint which takes a slower initial delay. This setup is limited by Minecraft's stupid render code.
but is her mod and she decide what to do with it and nobody should copy her mod because you die if u copy it
But really, I think the problem is FTB's decisions regarding RP2 and less RP2 itself. Sure it's stupid that she keeps teasing us with updates then dying again, and it's stupid she's not letting anyone else help, but that's her decision. Nothing's going to change a stubborn mod author, just look at Sengir and his new farms. You can just make the best of the situation, whether that means using the rest of Forestry, leaving RP2, or actually making a map with the RP2 we already have.
The point isn't more pulses per tick. The point is that with a sequence of prime numbers you'll have a non-repeating, rapid firing, sequence which unpredictable to the normal human and plays havoc with any prediction of most systems, too. 
Same number of pages. Also, no need for a one-shot-pulse, saves you a page. You only use the OSP when the incoming wave has variable duration and you want to make sure to fix its duration to a rising edge. OSP is most useful in conjunction with levers and/or Pulse Wideners as far as I can tell.
While I love Dave's series, I can see no reason why it can't co-exist with something like this.
I'm not a complete newbie to logic gates, both in MC and IRL, but some of the things in that PRC I have never heard of before. Having someone explain what each does, in text, would be extremely handy.
Videos like Dave's are great for practical build tutorials, telling you what the functions can do in practice, but the video format imo, isn't great for explaining "this setting does this and will output a redstone signal on these conditions"
So yeah, I for one would be very grateful for something like this
The point of my series is to be introductory and tutorial and to just show someone actually setting up systems. In this regard, videos are much more information dense because you see an entire build done and see all the tiny little things someone does to make a build work. But my series is not a reference material, which is what I think people are getting at. A reference for the PRC would be great!
The biggest challenge I see to a "cookbook" wiki is the same challenge that every programming "cookbook" has. Basically it's a series of programs and you need a notation for that. It's actually worse for this, since we program in an unconnected GUI framework there is no natural syntax for PRC. We'll have to make one up from whole cloth, which greatly increases the barrier to entry both for readers and contributors. Visual representations (I'd use OmniGraffle, for example) might work, but then we don't get the search engine juice that Greyed wanted in the first place.[DOUBLEPOST=1371576878][/DOUBLEPOST]
Please do. If only so that the Technic wiki stops pulling so far ahead in the search engine war. The FTB wiki has slowly slipped on search ratings.
I guess so. Still, you can make timer as long as you wish, as long you don't need to have number of ticks as prime numbers for some reason, by just stacking counters.
The point isn't more pulses per tick. The point is that with a sequence of prime numbers you'll have a non-repeating, rapid firing, sequence which unpredictable to the normal human and plays havoc with any prediction of most systems, too.
And then just wire it up to some piston contraption for a nice show.
Sure, and you plan on detecting 25% exactly how? Your options are "full", "not full" and "empty". If it was as simple as you think, I would have done it that way.
Using a timer seems at least as brittle as the other options, but will probably be right. Using a counter and a comparator is probably the right call for you.
Still, I can't help but ask, "Can't OpenPeripherals, MiscPeripherals, or OpenCCSensors give you a more precise reading? Why guess when you can know?"
When the topic is interesting and not shallow, we can have a real conversation. Most threads here are... erhem... shallow. Facile even.
Comparators work really, really well for detecting the percentages of space inside containers. I'm sure someone can come up with a way to extend that to energy storage. You might want to ask the mod authors if it's possible to expose that information to comparators in a similar way, if it isn't already possible.
....and you only get one of the choices
....and you may only change the choice by manually opening the GUI
Seriously. M F S U. Not exactly rare equipment in modded minecraft. You should know how these things operate.
If it was as easy as you think, I would have done it that way.[DOUBLEPOST=1371582742][/DOUBLEPOST]
Except, comparators don't work to determine the filled capacity of energy storage.
I can. My point was that 10 second timers are not enough. It's also overkill for what should just be a timer. I won't suddenly want to not charge the storage back up. I just want a significant delay so the reactors don't flicker on and off.
On a completely different note, we now know the nature of Dgdas's voice.
It is a combination of Nose and GPuzzle, young like nose, and Brazilian like GPuzzle.
Back to the topic.
It is a combination of Nose and GPuzzle, young like nose, and Brazilian like GPuzzle.
Back to the topic.
Sorry, comparator function in rednet (the word space is crowded). Reset a counter and have its increment line tied to a square wave with 1 second. Pipe its output to a counter, and pipe that output to a "less than" or "greater than" comparison function. It is absolutely more work than the standard long-check timers Immibis will offer. I am just saying, "This is how it can be done."