[Bug] EnderIO Conduits unresponsive to redstone
andr9528 opened this issue ยท 4 comments
Not Completly sure how to replicate, but my current setup to only allow pyrotheum production when i have < than x amount of pyrotheum and above 4096 redstone, is failling to pull out the pyrotheum, when both conditions are meet.
The Picture above shows that redstone is on, from the hidden redstone conduit, and that the fluid conduit is suppose to pull out when given a redstone signal.
The picture above shows that the conduit is set to the correct mode. The redstone conduits on the machines all have a redstone AND filter in them taking in signal from yellow and orange.
A temporay fix is to toggle the redstone requirement off and then on again, but as soon as the active redstone signal goes offline, because the conditions isn't met any longer it goes to the same issue, meaning in that as soon as the redstone comes online again it won't pull out, just as before the temporary fix
I'm writhing it here as EnderIO's template stated that if issue was found playing a modpack, it should be reported to the modpack developer. Tell me if you want me to create an issue on EnderIO's github linking to this issues, as i will gladly do that.
After slightly more testing i found that causing a block update next to the fluid conduit will make it work correctly even with redstone signal flickering on and off, for now at least, Will update further on this tomorrow if it broke again after a would restart, which wouldn't surprise me if it did.
Fell free to message me if you are missing any details which might help in seeking out the issue
I'm closing it for now, under an assumption that it's fixed in a newer enderio version (and so will be fixed by 1.3). Comment if the bug is still present in the newest enderio version.
As i expected on world reload the issues reappeared. And again causing a block update beside the fluid conduit makes it function correctly yet again it seems.
I have other setups in my world with logistic pipes that already require an block update on world reload to reconnect to their targeted block, could these issues be related?
My temporary fix for the logistic pipes is a pressure plate that causes a piston to push a block besides the logistic pipe, but due to the natural compactness of EnderIO conduit i do not have the space to introduce the piston setup here, without either severely degrading the appearance of the build or the layout of the hole build.
After letting my build sit at few minutes more, i noticed that it would bug out again, meaning that the block update fix only works for a few minutes at a time. I guess i have to remodel how i get the redstone signal to the conduit...
Using a vanilla AND gate to do the logic seems to do the job for now, but it is not exactly good looking...
