Mod Feedback [By Request] RotaryCraft Suggestions

[Pyure]

Just keep it always full and have the speed/torque CVT settings flick back and forth on a timer.

Less fiddly that way.

The CVT thing is obvious; I actually have mine on a sequencer rather than a timer since it allows more fine-tuned control.

However keeping it "always full" isn't a solution, its a late-game workaround.

I'm seeking decently-engineered solutions here if possible.

 

[Braidedheadman]

I always take my readings off the input chest (with a second attached to handle overage) rather than the extractor and time the operations of my boring machines and ore processing lines based on what state the chest is in. The advantage of doing it this way is that until I had enough power to run a bore at 1op/t and my ore processing lines at 1op/t, the timing between the front and back end was never in sync anyway and so the chest became my "has work" logic gate. Being a chest, it naturally has a much large capacity than the internal item buffer in the extractor and therefore allowed me to run each end for longer periods of time (re: gas turbine fuel efficiency) before switching between ore mining and ore processing. Rednet's programmable controller provides excellent logic and RSS utilities when implementing this resource stream at both early and end game stages.

 

[Pyure]

I always take my readings off the input chest (with a second attached to handle overage) rather than the extractor and time the operations of my boring machines and ore processing lines based on what state the chest is in. The advantage of doing it this way is that until I had enough power to run a bore at 1op/t and my ore processing lines at 1op/t, the timing between the front and back end was never in sync anyway and so the chest became my "has work" logic gate. Being a chest, it naturally has a much large capacity than the internal item buffer in the extractor and therefore allowed me to run each end for longer periods of time (re: gas turbine fuel efficiency) before switching between ore mining and ore processing. Rednet's programmable controller provides excellent logic and RSS utilities when implementing this resource stream at both early and end game stages.

Good way to attack the problem. I may do something similar. Thanks.

 

[KingTriaxx]

I did something similar, but I used the output chest instead. Output chest is empty, run the extractor in grind mode for two minutes. Then switch to high speed filtering mode for two minutes. When the output empties again, the cycle starts over. Of course when I did that, there wasn't the engine limit on the junction boxes, so I had six or eight performance engines running it.

What is the 1op/t speed/torque on the Extractor? I mean, can I plug it straight into the Tokamak, or do I need a gearbox?

 

[keybounce]

Plug it straight into a Tokamak ...???

At that point, do you even need to do any shifting?

 

[Braidedheadman]

You'll find the formulae for the extractor's output speed here:

RotaryCraft Wiki: Extractor

Solve for speed using Time(one tick) for Minecraft's tick rate (20 ticks per second) and gear up accordingly.

You'll need to meet the speed and torque requirements simultaneously for a straight 1:1 power train to run at those speeds. Note that doing so is incredibly energy inefficient. Alternatively, you can make a 1-tick extractor work with far less power if you use a 2-clock timer and CVT to alternate power between torque and speed extractor stages.

 

[KingTriaxx]

Isn't the point of playing this mod going over the top?

I also love that I can play this mod, and still have no idea what any of the math behind it is.

 

[Braidedheadman]

I rather think that the point of this mod is about designing and implementing good engineering solutions to (sometimes) tough/tricky problems, which necessarily means finding the most productive methods and remaining energy efficient while not over-complicating one's designs.

Reika's mods reward good design far more than they do "over the top" or brute force.

[Edit] If the math isn't your forte, there are online tools you can use to help out. This site, for instance, accepts algebraic formulae, which, like any calculator, can help take some (not all) of the burden off one's shoulders when calculating a machine's target rate:

https://www.mathway.com/

(Note: copy-pasting formulae into the calculator's input field doesn't work very well. You'll want to type them in manually, making full use of their UI for certain symbols, like log₂).

 

[KingTriaxx]

Hmmm... nah, over the top is the way to go. Otherwise what's the point of 1op/t?

I over engineer everything. Most people make a cobble gen out of water, lava, and a block breaker. I used a BC quarry drilled to bed rock and using lava and water to make it generate for me. Very fast when provided with enough power and will break it forever. There's no point in doing something if I can't overengineer it. So yes, I would want to run a grinder off of the absolute top of the power production chain. Not because it's necessary, but just because I can. And then see how many grinders I can run off of it. I could do all the math and have an exact number, but that's no where near as much fun.

 

[RavynousHunter]

Running the extractor at one tick for all steps requires 512 Nm @ 1,048,576 rad/s (536,870,912 Watts), or eight gas turbines thru an 8:1 speed gearing. A single HP turbine running at full tilt (w/ water) can run sixteen extractors at one-tick for all stages. Sooooo, if you've got a decent reactor capable of running a HP turbine, and you want to never worry about ore processing literally ever again, hook that mother up to a shaft power bus and split it off to a bank of 16 extractors. Put bedrock drills on them for further madness.

Hmmm... nah, over the top is the way to go. Otherwise what's the point of 1op/t?

I over engineer everything. Most people make a cobble gen out of water, lava, and a block breaker. I used a BC quarry drilled to bed rock and using lava and water to make it generate for me. Very fast when provided with enough power and will break it forever. There's no point in doing something if I can't overengineer it. So yes, I would want to run a grinder off of the absolute top of the power production chain. Not because it's necessary, but just because I can. And then see how many grinders I can run off of it. I could do all the math and have an exact number, but that's no where near as much fun.

No need, with the grinder. Put everything you have into it, as they can run multiple operations a tick.

 

[Braidedheadman]

Or you can do it in just 16MW; eight micro turbines, or 1/4 of the power of one gas turbine. I was working out a design to do it for even less on average using ElectriCraft and tuning power input for each stage separately (~16MW, ~8MW, ~8MW, and ~8MW respectively for what works out to an average of ~10.49MW) but I never got around to it before our server croaked.

 

[Pyure]

Anyone know if the Steam Turbine (the small 1-block version that consumes standard Steam) requires liquid Nitrogen? Its not in the manual.

edit: confirmed, requires liquid nitrogen to keep temperature low.

 

[keybounce]

You can use multiple machines, each running slower, for a faster overall output.

 

[Celestialphoenix]

Running the extractor at one tick for all steps requires 512 Nm @ 1,048,576 rad/s (536,870,912 Watts), or eight gas turbines thru an 8:1 speed gearing. A single HP turbine running at full tilt (w/ water) can run sixteen extractors at one-tick for all stages.

I think the extractor might also be one of those machines which that lets you process multiple items per tick.

 

[RavynousHunter]

I think the extractor might also be one of those machines which that lets you process multiple items per tick.

I don't think so, since it doesn't inherit MultiOperational, but I could be wrong.

 

[Celestialphoenix]

I'll grab my snorkel and go changelog diving:
V7:
RotaryCraft: Added ability for several machines (including Grinder and Extractor) to run multiple operations per tick

 

[RavynousHunter]

Huh, must be a special case, then.

 

[Pyure]

Does anyone here ever find a half-decent use-case for flywheels?

 

[Aetherpirate]

If you're going to use EC, I think you need them to stablize the output, otherwise the EC network updates all the time as the values change.

 

[Pyure]

If you're going to use EC, I think you need them to stablize the output, otherwise the EC network updates all the time as the values change.

I forgot about that actually. But flywheels predate EC. There must be other valid use-cases.