search

SonarSonic / Flux-Networks

Wireless Energy - Minecraft Forge Mod
MIT License
110 stars 59 forks source link

Flux points not transferring as much FE/t as they should, but works fine with a cable #491

Open Nevrai opened 2 years ago

Nevrai commented 2 years ago

Describe the bug

Attaching a flux point to certain machines that use a lot of energy (e.g., 150k FE/t or more), such as the isotopic centrifuge in Mekanism, doesn’t provide them with enough energy to run efficiently, so the machine runs but constantly significantly dips in power and runs slower than its max speed, but attaching a cable with a high transfer speed (such as Mekanism’s ultimate universal cable) to the flux point and then attaching the cable to the machine makes it run just fine. I tried turning on power surge and bypass limit, but they did not help. I also tried turning on power surge and bypass limit on the flux point attached to the source of the power, which didn’t help either. My energy source has more than enough power and output (currently, a Mekanism induction matrix with 50 trillion FE and a max output of 210.5M FE/t).

This has happened a lot with many different machines, including ones from other mods, such as RFTools’ builder and crafter, not getting enough energy/t to run efficiently unless using a cable attached to the flux point rather than a flux point directly on the machine. For some reason, the flux point isn’t able to keep up with the energy output, even when it’s configured not to have any power output limit and configured to run in power surge mode, but attaching a cable to it and then the cable to the machine makes it work just fine. Seems like a bug to me, and it’s something I hope can be patched, as whilst Flux Networks is by far one of my favourite mods, it’s been an issue that’s been the most frustrating part of using Flux Networks to me—and others I’ve spoken with who’ve experienced the same issue.

To reproduce

  1. Place a machine that uses about 150k FE/t or more.
  2. Attach a flux plug to it (with a flux point on any source of energy that should have more than enough energy and output).
  3. Try again by putting a cable in between.

Versions

BloCamLimb commented 2 years ago

I'm not sure whether these machines have transfer limits, for example, RFTools builder accpets 20,000 FE/t at most by default. And do you have any other way to power these machines at the same time? Such as connecting them both with a cable and a flux point. Flux points will always simulate energy transmission and compute the maximum request for the next cycle, which happens at the end of the tick. At least Mekanism's cable can store energy of fixed capacity. So the cable does double buffering in this case, or the cable itself ignores the transfer limit of the machine. Have you tried to also add storages to the network?