HE->RF converter doesn't seem to consume HE
thePalindrome opened this issue ยท 14 comments
Version: 4130H1
The HE to RF converter seems to provide RF without consuming HE, at least on loads of ~30 RF and lower. I would've expected < 10 RF to result in it not consuming HE (which is relatively fine I guess), but even larger loads seem to not do anything. This in combination with #431 could probably be handled in the same version bump, and is probably why the submitter of that tried it :P
I'm directly connecting it to an OC computer case and an AE2 Power Acceptor. I'm powering it off an Lithium ion battery block set to I/O mode. The battery itself is reporting a change of 0 in the instances where my power generation is running. (both in when hovering over the bar, and directly comparing the number at the top of the UI (which I presume is more accurate)
I notice that if I turn off the power switch, it takes a few moments for my ME network (with no energy storage on it at all) to shut off, which seems to imply that it is running some odd sort of state where it's not keeping up with the power network.
I can't replicate that behavior (mostly because I can't think of anything that would provide this little HE), but I've tested Thermal Dynamics' flux ducts extensively without coming across any weird behavior. #431 seems to be related to Mekanism's cables, what RF conductor are you using?
Does the delay also happen when you use an RF generator outright? Perhaps the AE2 converter has an internal buffer that lasts for a few more seconds before going out?
Okay, using a creative BC engine I managed to conclude that there does seem to be a buffer (I couldn't see it directly, but the AE2 network tool showed more power was being generated than consumed, which implies the existence of a buffer. Plus there was the few seconds of time)
So that's the delayed shutoff explained, but then why do my batteries suffer no drain whatsoever?
This little test setup shows a drain of 100 HE/s on the li-ion battery, it also works when the HE/RF converter and the AE2 energy acceptor are connected with Mekanism cables. Do you have any generators running right now or perhaps other batteries in I/O mode that might throw off the discharge rate reading? You could try isolating the battery and the converter from the network. Does it happen with any other RF acceptor too or is it really just the AE2 converter?
After dicking around for about half an hour I finally found a way to reliably replicate this issue, simply having a fluix cable next to the converter causes it to spit out energy for free. I'm not sure why it does this since fluix cables don't seem to carry RF. It also works with mekanism universal cables, so it's not the fluix cables being bugged (they're just a bit weird) nor the HE cable switch, but the converter's output.
Yup, it was definitely converter. I redid some of the math that keeps track of the energy being transmitted during one tick, it seems like it's properly deducting everything it should. I'm leaving this issue open for now, we can close it later after testing the upcoming version.
Huh, alright, the old buffer converter claimed 1 HE to 10 RF iirc, which would be where I got confused.
Taking that into account, the numbers now seem to come out correctly (and looking at the current code seems to imply 1 HE to 4 RF)
So it seems like it works! (I'll leave the actual closing to HBM, just in case there's something else they want to do to wrap this up (like maybe an updated in-game conversion ratio :P )
Alright, it's drawing power, but looks to be drawing double what it should.
My ME network is drawing 11.3 RF/t, which should turn into 22.6 HE/s but my battery is reporting a loss of 42-44 HE/s