Version: fluxnetworks-1.12.2-4.0.14-31

When connecting both RF (Ender IO - Vibrant Photovoltic Cell) and EU solar panels (IC2 Classic) to a Flux network, that leads into an MFSU in IC2 Classic, sometimes huge minus buffers appear in the Flux networks. They reach 0 eventually, and then the buffer goes down again to a very small minus number like... -500k or something like that.

Is there something we are missing?

Seeing the same issue with a flux point (or whichever the output one was) connected to and EnderIO Enhanced Energy Conduit, connected to a bunch of Mekanism devices and a few Cyclic auto-crafters.
Buffer shoots to -50k or something like that, then climbs back to zero, and back down to -50k.
All devices are currently not using energy (as in, their buffers are full and not in use), but no energy ever ends up in my FluxNetworks Storage.

MC Eternal modpack 1.3.5b, fluxnetworks-1.12.2-4.0.14-31.jar

Power, in my case, is coming in from a Refined Canola Oil setup (oil generators connected to an enderio conduit, connected to a fluxplug.

Here is an image

The plug is connected to an IC2 Classic Solar Panel.
The point is connected to a BatBox.

There will be a new(?) energy transfer system, for now, the issue is not easy to debug and fix. It may also be caused by other mods, for API or capability is not used correctly. We will now test on 1.15 and try to fix the old versions

@BloCamLimb Would that also fix #95 ?

And I see. I hope you guys can come up with something. I love Flux Networks ^^

This is probably due to others mods returning invalid integers. i.e. negative energy usage. - It's hard to track down but as BloCam says we will test on 1.15.2 first and see if we can't backport some extra checks to prevent negative values messing up the buffers.

It is possible #95 could also be linked to bad implementations

I just got this spammed in my server console. Is this related as well?

It appeared many many more times.

can,t you add a funktion to the config to disable the buffer? , with draconic evolution it load all in the buffer and then it does not transfer it to the energy core

@08shiro80 Sadly not, the buffer is the key to how Flux remains much more server friendly, and makes priority features and other things possible. When we release our final 1.12.2 version i'll look into resolving this buffer issue with some of the changes I've already introduced to the 1.15.2 version. The buffer should only ever be as a big as one tick's max transfer, which obviously in DE case can be pretty massive, but energy is never lost in a buffer as soon as space is available it's transferred and as the buffer generally only receives what it can transfer so in most cases it's transferred instantly.

IC2 API is no longer supported