I knows they're better and more expensive than gold waterproof pipes but what's how much does a filled pipe can transferred per tick? I believe for the gold they carries 40 milibuckets per tick so how much can a liquid conduit do at full pressure? Also can they be used for any liquid transferring or can it only carries some and does it works on any container including iron tanks? They'll also carries the max liquid automatically right? As long you change to extraction mode on the pipe adjacent to the container with enough liquid.
Thermal Expansions liquid conduits how much fluid can they carries per tick?
- Thread starter Harvest88
- 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
I can tell you they'll work with any liquid and will work with iron tanks, but I don't know the flow rate, sorry.
I don't really think of them as more expensive than gold waterproof pipes, but that's because I have plenty of copper, lead, and redstone, not much gold (since I've made most of it into electrum and various TE machines) and nothing to make into waterproofing.
I don't really think of them as more expensive than gold waterproof pipes, but that's because I have plenty of copper, lead, and redstone, not much gold (since I've made most of it into electrum and various TE machines) and nothing to make into waterproofing.
even if they were to carry less, they're still much more server friendly, just for that I'll never use BC pipes again.
but if they're like the conduicts, they probably can carry and hold a lot, because the conduicts can hold tons of energy and won't blow up.. they're just too good.
but if they're like the conduicts, they probably can carry and hold a lot, because the conduicts can hold tons of energy and won't blow up.. they're just too good.
I had this same question earlier and after reading the wiki the only answer I can give you is it varies. According to the wiki the viscosity of the liquid is factored into how quickly the liquid flows. Going by that, steam should flow quickly, water should flow "normally" (as it's generally the base liquid for viscosity), and honey should flow more slowly. The problem is, without extensive testing, the exact numbers aren't known, and the mod author has been tweaking the liquiducts on top of that.
They carry a lot more than golden waterproofs, it seems, but from what I can tell, they don't auto-extract. Only machines that automatically output their stuff will dispense into them automagically. ie: A Magma Crucible, but not a Fermenter. For any non-TE machine, you'll still need to use Wooden Waterproofs, which means it's limited to the size of a wooden waterproof pipe.
Wrench at the connection to set to extract mode, apply redstone signal to extract.
The version included in Magic Pack right now isn't fully updated, and so some select machines (Forestry in particular) don't behave well with this, but it works fine otherwise:
In particular, the squeezer/fermenter output tends to screw up on updates when extracting: when you connect the liquiducts it'll pull what it can and then the ducts will drain and nothing more will flow through until you do something to update the ducts (like breaking and replacing one). This is known issue stuff that got fixed shortly after in the 2.1.2 release, but the version included in Magic World is still 2.1.0 and so you'll see this behavior until it is updated.
I did a quick test with a steam boiler a few days ago.
Liquiducts don't simulate fluid movement at all. Instead, they instantly teleport liquid from all available inputs to all available outputs, regardless of how long the pipe is. This has the following implications:
- Throughput of liquiducts is for all intents and purposes infinite, limited only by the speed you can pump liquid into it.
- Since there's no flow, there's no such thing as backflow either.
- A liquiduct pipe has a certain storage capacity, which seems to be around 4 buckets of liquid, independent of pipe length. A single section stores as much as a five kilometer long pipe does.
Here's a screenshot of my test setup.
Ignore the texture bug in my test world, these black things are industrial steam engines. Each one produces 8 MJ/t. A single golden waterproof pipe will feed one. A single liquiduct will feed two, because the boiler will not output any faster than that. However, with four liquiduct inputs hooked up to the boiler, you can feed all eight industrial steam engines even though the connection is only a single liquiduct.
Liquiducts don't simulate fluid movement at all. Instead, they instantly teleport liquid from all available inputs to all available outputs, regardless of how long the pipe is. This has the following implications:
- Throughput of liquiducts is for all intents and purposes infinite, limited only by the speed you can pump liquid into it.
- Since there's no flow, there's no such thing as backflow either.
- A liquiduct pipe has a certain storage capacity, which seems to be around 4 buckets of liquid, independent of pipe length. A single section stores as much as a five kilometer long pipe does.
Here's a screenshot of my test setup.
Ignore the texture bug in my test world, these black things are industrial steam engines. Each one produces 8 MJ/t. A single golden waterproof pipe will feed one. A single liquiduct will feed two, because the boiler will not output any faster than that. However, with four liquiduct inputs hooked up to the boiler, you can feed all eight industrial steam engines even though the connection is only a single liquiduct.
You're on the right track, Omicron, although you're not entirely correct with that. Bear in mind that steam is a bit of a special case since it's flagged as a gas.
You're correct in that "flow" isn't being simulated - in general, the system runs in steady state and it would be absurd to run those calculations every tick.
The speed of transport does depend on the amount of liquid in the system - it's pressure-based.
The system's capacity does increase per duct. Larger systems hold more, and thus require more liquid IN them to output at full speed. The nature of the calculation itself may change a bit.
You're correct in that "flow" isn't being simulated - in general, the system runs in steady state and it would be absurd to run those calculations every tick.
The speed of transport does depend on the amount of liquid in the system - it's pressure-based.
The system's capacity does increase per duct. Larger systems hold more, and thus require more liquid IN them to output at full speed. The nature of the calculation itself may change a bit.
Ah, okay, I didn't even know there was such a thing as a "gas" flag 
Looks like I'll have to test again with actual liquids to get reasonable values. Do all liquids behave the same in terms of throughput, or are there differences? I seem to remember reading something about viscosity somewhere...
Looks like I'll have to test again with actual liquids to get reasonable values. Do all liquids behave the same in terms of throughput, or are there differences? I seem to remember reading something about viscosity somewhere...
Actually, the energy conduit has a lower throughput and stores less energy than BC pipes - it just distributes it in a better fashion. Most BC engines aren't sensitive to the power request function, however, and will just keep dumping their energy, whether or not it can actually be transmitted.
And what happens with that energy? Because many times I've stopped the engines and after a while using my machines, the 3 cells were still full and no energy was going down.. after some more time it did start to down of course, but it seemed to me like the conducits stored almost everything my fuel engines where producing.
Maybe it is a bug or maybe it is because I'm using the version in the magic pack and you changed it in newer versions?
Thanks for once again taking the time to come in here and talk shop with us, King Lemming. For me at least, Thermal Expansion was the "surprise hit" of the FTB Beta Pack (I really honestly hadn't given it a good look before), and as a server admin I don't think I'll ever run a modded server without it as long as you keep putting it out because of the emphasis you've put on making everything nicer for us load-wise. The sheer depth of customization you continue to expand upon is also pretty darn amazing, sir, and I look forward to seeing some of the things that have been hinted at for the future of the mod. =)
Glad you like it. I'm just sorry that certain things haven't worked out quite as well as I would have liked in all cases. :/ Minecraft definitely has a lot of limitations, and some approximations have been made in the name of keeping things efficient. Hate to keep pushing these tiny revisional releases on people, but we just keep finding some corner cases where things crop up in live play that just never occur in testing.
And bigger things are coming, I just want a solid foundation on the old stuff first. We're almost there, and we do have a few things in development - which believe me becomes annoying to comment out every time I want to do a bugfix revision.
And bigger things are coming, I just want a solid foundation on the old stuff first.
We're almost there, and we do have a few things in development - which believe me becomes annoying to comment out every time I want to do a bugfix revision.
Every time I've run into something, you've had a patch up for it within a few hours. That's a track record to be proud of, in my opinion.
(The 2.1.0 update triggering my Industrial Steam Engines attached to my High Pressure Boiler to go into feedback and explode was a minor setback, but considering I could never have made such a system nearly as compact as it is without TE I was very quick to forgive, and a quick reboot settled the rest of that issue =)).
(The 2.1.0 update triggering my Industrial Steam Engines attached to my High Pressure Boiler to go into feedback and explode was a minor setback, but considering I could never have made such a system nearly as compact as it is without TE I was very quick to forgive, and a quick reboot settled the rest of that issue =)).