If i set flux gate to 4000 RF/t and then attach a fluxduct to it with 2 creative energycells, i get 8000 RF/t out. Is this like expected, that it only limits each sender separately?

I don't know how RF API works, but i almost blew up my reactor because of it. I had set like 16 creative energycells to cryotheum duct when testing reactor and finally flux gated it to 60k RF/t going into energy injector. So i figured 1 creative energycell with 100k RF/t would be enough... how wrong i was...

Draconic-Evolution-1.7.10-1.0.2-Snapshot_9

I had an issue similar to this about a week ago; I'm not sure if it's relevant but you may want to take a look at my issue ticket and see if it might be the same issue

It looks like i may need to address this issue after all. The flux gate currently works by simply limiting the amount of RF that can pass through it each tick but it seems the cryotheum ducts must make multiple energy transfers per tick.

Make sure your capacitor banks are all connected to eachother. It's rare but it's possible they form multiple connected multiblocks (test by right clicking each one, and set their input/outputs to max). You can mitigate that by not having active flux capacitors in inventory for example when placing them down. Instead of fluxgate you can even have a wall of Resonant energycells, input from 1 side and output from the other with cryotheum ducts.

I set my flux gate to transfer 1M rf/t, connected to a massive enderio capacitor bank in one end, and a draconic energy storage with 10B rf in the other end (for testing). Even though it was set to 1M rf/t, it would only transfer 100k rf/t into the capacitor bank. What am I doing wrong?

As mentioned just above you, it is something that will be looked into.

Yeah but above me they were talking about sending too much power, but what I get is less power than specified in the gate ui.

So is there any other way to use the draconic reactor until this is fixed? Hmm. Perhaps you can modify the transfer speed of ender io capacitor banks using computers

I did check it by clicking the capacitor bank that the flux gate was connected to, and it had 5M rf/t input/output

Yep that's exactly how i thought they worked. It is possible I'm using a slightly outdated version, can't check right now. That's great if you've fixed it. However this is still an issue with cryo ducts and should probably be fixed on their end. I assume that energy conduits have the ability to retrieve the max input rate of the block they are trying to input into? If so it should be easy for them to limit the amount of energy that is transferred into each block each tick.

assuming the transfer rate of the conduit is high enough to support the transfer rate of the block yes.

First off are you using Snapshot 9 or latter (Im going to assume you are)

Try removing the gate from the equation and see if you still get the same results. That will tell you if its the gate or something else entirely.

The following setup transferred 200M RF at 1M RF/t in exactly 10 seconds meaning the flow was indeed 1M RF/t as expected.
http://puu.sh/nNI32/1c4e449833.jpg
Check if you can replicate those results.

I tried removing the gate from the equation like you said, and found something interesting. It seems the problem is with the cryo-stabilized fluxducts, like you said in an earlier post.

as you can see here, with a basic capasitor bank (the max input is of a single capacitor bank is 1000 rf/t), we're actually inputting 3k rf/t due to the fact that the cryo-stabilized fluxducts are sending the power 3 times per tick, because they have 3 connections (as mentioned by brandon3055 in a post above.)

However, when we try the same setup using resonant fluxducts (which have more than 1000 rf/t throughput, but they work differently from the cryo-stabilized fluxducts since they do have an internal storage, whereas the cryos don't)

here we properly get 1000 rf/t

So the flux gate might actually work properly, although you may need to add some extra checks for the cryo-stabilized fluxducts, since they work differently.

I also tried the same setup, but with gates in between them. Each gate was set to 200 rf/t
The one with cryos received 600 rf/t, and the one with resonant received 200 rf/t (not shown in picture).

@Divran Interesting investigation! Maybe report here as well: https://github.com/CoFH/Feedback

Just tried it (the exact same setup again) with a leadstone (also tried resonant) energy cell (instead of a capacitor bank), and they don't have this problem at all. Since it's from the same mod, they are obviously handling the cryo-ducts properly. Maybe you could check the code for this energy cell to see if they're doing anything differently?

EDIT: Nevermind, after some quick use of a stopwatch I've determined that the energy cells also have the same problem. It's a lot harder to see though since they don't have a nice rate indicator like the capacitor banks do.

Ok let me just explain whats going on here. With conventional fluxduct the duct itself has an internal energy buffer which each energy provider injects energy into. The duct then ejects energy from this buffer into energy acceptors once every tick.

Cryo ducts work differently. In order to allow infinite energy flow they would require a buffer with infinite capacity so they have no buffer at all. Instead the way they work is whenever an energy provider injects energy into a duct the duct will pass that energy directly to any attached acceptors. So if you have 3 providers each injecting energy every tick and one acceptor the acceptor will receive 3 times the energy it should per tick. (I would consider this a bug)

I fixed this problem (with the gates atleast) in snapshot 9 by adding a max per tick transfer limit.
So my question again is what version of DE are you using?

Well if it isn't then there's no need to limit it

I'll check which version I'm using later today.

EDIT: I don't have it installed on this computer, but I asked a friend who plays on the same server to give me the version of DE that we're using. He told me Draconic-Evolution-1.7.10-1.0.2-Snapshot_9. It's the latest version of FTB Infinity, if that helps. I thought you said you'd fixed it in snapshot 9 though?

Yes i did... It should be fixed in that version.

Just checked (on my own computer), and that is definitely the name of the jar file. You could try downloading "FTB Infinity Evolved" yourself and have a look.

EDIT: I'm not a minecraft developer so I can't exactly know what's the best solution for every concievable problem, but I believe I have convinced myself that the problem is probably best solved in the receiving block, rather than in the cryo-fluxducts. If you can solve it in the flux gate (or tell me how to fix it on our server if you've already solved it), that would be great. Then I can start trying to not blow everything up with the draconic reactor!

I am running a slightly older Evolved version and cant update atm but i am running DE snapshot 10 and i was not able to reproduce the issue.
http://puu.sh/nQFDC/cbac9ebb6d.png
http://puu.sh/nQFEA/6a1bdc8cfe.jpg
http://puu.sh/nQFF8/a0ac60b3cd.png

Alright so we just have to wait for FTB to update the infinity pack I guess

On Wed, Mar 23, 2016 at 6:24 AM, brandon3055 [email protected]
wrote:

I am running a slightly older Evolved version and cant update atm but i am
running DE snapshot 10 and i was not able to reproduce the issue.
http://puu.sh/nQFDC/cbac9ebb6d.png
http://puu.sh/nQFEA/6a1bdc8cfe.jpg
http://puu.sh/nQFF8/a0ac60b3cd.png

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#236 (comment)

Alright, so I'm having a similar yet somewhat different issue with the flux gate. My induction cell (Mekanism) seems to amplify the effect, making it not 3x faster, but 101x faster then it's supposed to. It only happens when using cryo-fluxducts similar to the rest.

What the flow should be:

What it actually is:

I don't know if this changes anything, but I figured I'd let you know just incase.

Mod Versions:
Thermal Dynamics 1.1.0
Mekanism 8.1.8
Draconic Evolution 1.0.2 - Snapshot 9

So yea same issue. So if you have 3 inputs to the duct and 1 output you will get 3x the output you should. If you have 10 inputs the output will be 10x. So im guessing you have 101 separate sources supplying the duct in your case.

Well it's only 1 output, the Induction Matrix. I'm guessing it attempts to input energy 101x each tick, otherwise I don't have a clue.

How many output providers do you have inside the matrix? It looks really big.

Only 2, I tried different sizes and providers and ports and no matter what it gives the 101x effect.

This is the one I'm using in my world and it does the same thing

Oh I should mention it still does it without the tesseract.

I think we have concluded that this is a CoFH bug. It should atleast be fixed for the flux gates in the latest versions of DE.