Level Emitters Power Wrong Export Bus

[Draxhax]

I'm currently running rv2 beta 7 and I'm having issues with level emitters transmitting redstone power to the incorrect export bus. I'm currently utilizing level emitters to automatically craft common resources for expanding my ME network storage. However, the level emitters are no longer working as expected. Now I have an excessive amount of resources that are not needed and serious deficit in resources that I do need.

I've built a mini version of the setup I'm currently using to demonstrate my current problem. In this instance, I have three showing, but I've only configured two.

In this first screenshot, I have only configured the middle level emitter and export bus. The level emitter above the export bus is turned off, however the system is still trying to craft sand -- as seen by the crafting monitor.

I then turned off the other level emitters and increased the minimum amount for crafting sand. I canceled all pending work requests and reconnected everything. The only level emitter lit is the one above the sand, and after waiting for a full minute now, no request has been input for crafting sand.

I went ahead and configured the export bus to right to craft smooth stone and added a furnace with an interface on it. Please note that crafting sand and smooth stone both require cobblestone, as such, I could not possible craft either resource without having cobblestone in the system to begin with (which I have plenty of.) The level emitter is not lit above the export bus for stone, however the one from sand is powering it.

Here's some screenshots as to how I have quickly configured the emitters and buses used for this example. These aren't the exact numbers I normally would use, but I believe they provide a good enough example.

Sand Level Emitter:

Sand Export Bus:

Smooth Stone Level Emitter:

Smooth Stone Export Bus:

I was originally running rv1 stable 1 where this was working, however the server kept crashing on restart due to some bug with the crafting export buses that I believe was fixed in rv2. However, now in rv2, this configuration is no longer working properly.

As an example to the issue I've run into with this, I try to keep about 5000 of certain items in stock. This problem has now caused me to have over 70,000 Pure Fluix Crystal, 74k Pure Nether Quartz Crystal and currently only 7 Pure Certus Quartz Crystal. In this case, I had the Fluix crystal on the left and Nether crystal on the right and the one lit was for Certus Crystal. I have a huge deficit for that crystal now and a massive surplus of the other two.

[Cisien]

To solve the issue this caused, you can craft the pure crystals into storage blocks, then craft the storage blocks back to the original item.

As for this bug, it is probably some vanilla Redstone behavior, try separating these busses by a block. It seems like a bug that cables are relaying Redstone like a full block

[yueh]

This looks like the cables are acting as a full block. Which is not the normal behaviour of AE2.

I remember another mod breaking the normal behaviour of a non full block and causing it to emit a redstone signal to every adjacent block. But I cannot remember which one it was. It could be RefinedRelocation or RemoteIO, for some reason I faintly remember them in that regard.

I can only recommend that you reproduce it with AE2 alone. This will not have the issue.
And then slowly add the other mods back until it breaks.

[Draxhax]

I'll see what I can do. I'm currently using a slightly modified version of the Modsauce pack, so it will take some time to go through the massive list of mods until I can find the offender. Let me know if you happen to remember what that mod is and I'll let you know my results.

Thank you!

[yueh]

This issue #646

[Draxhax]

I checked the changelogs on modsauce and it looks like they added RemoteIO in their latest release. Based on the issue you've linked and that change in the log here, I suspect you're completely correct. A test with just Forge and AE2 installed resulted in exactly what you had expected.

Update: I added RemoteIO 1.8.1.B84 and the issue occurs. I noticed on the github for RemoteIO, the author marked it as closed and supposedly-fixed 8 days ago, but I don't see a release available with that fix. It would also appear that the github source itself hasn't been updated in a month, so I cannot attempt to compile it either.

In the interim, I will customize my client/server setup even further by removing RemoteIO until the fix is available from there.

Thanks for your time!

[JelmarG]

In the meantime, you could try keeping the cables separated? If it's the cables that are acting like some kind of redstone conduit, something like this might work for you. Unless of course the signal travels all along the top cables as well. If so, ignore my comment ;)

[Draxhax]

I just removed RemoteIO from my server and client for now. Nobody on my server has utilized anything from RemoteIO yet, so there was no impact created with its removal for now. I'll just wait for a release and test it out manually before I add it back in.