Ic2 conections
DeezNutz9 opened this issue ยท 17 comments
Modpack version
Input version here
Can the issue be reproduced?
Yes
Logs
Input pastebin link to crash-report or latest log, if applicable
Issue
Whenever I play Enigmatica 2 Expert my cables to my ic2 machines disconnect at login and donnt reconnect. I cant play it like this
If this is a feature request, feel free to delete the template.
I am seeing this issue as well. Any of the levels of IC2 cables disconnect into separate pieces, and this also includes the Batbox, CESU, MFE, MFSU and machines. It's like the client stops recognizing them as connecting entirely.
Also tried Basic Universal Cables from Mekanism, no connection to any of the machines.
Tried Immersive Engineering cables, no luck either.
FYI, when I reload the game from scratch, everything does seem to reconnect and work.
but here's the weird part. When the basic universal cable connects to the output of that CESU, it will power any machines downstream from it, but it is not actually pulling the power out of the CESU, it's just providing infinite power downstream.
I think that might be a bug... :)
@NillerMedDild Can you reopen this issue? Still having this happen, where the cables connect just fine when I first launch, but if I close out and reopen within the same java process, the cables disconnect. Means I have to relaunch from scratch every time.
I might look into what causes this.
Basically, the ic2 energy net handles all EU power transfers. For whatever reason, it can just die sometimes.
Please let me know ANY consistent methods of reproducing this that you are aware of. I'm also aware it can happen for no reason at all, but that'll be harder to fix.
This ought to reproduce it:
Still having this happen, where the cables connect just fine when I first launch, but if I close out and reopen within the same java process, the cables disconnect
I use the Curse launcher. After loading the game the first time, everything connects properly. If I close the game instance but leave the java running to rejoin the world, everything is disconnected. If I close the game, close down java and bring it back up from scratch, everything is connected again. So the act of closing the world and bringing it back is creating the disconnected cables.
I haven't played the game in a number of months, but that is what was happening.
This ought to reproduce it:
Still having this happen, where the cables connect just fine when I first launch, but if I close out and reopen within the same java process, the cables disconnect
Honestly I'm failing to understand what exactly they mean by that.
What do you mean by
leave the java running
Closing the game instance also shuts down the JVM for it. Are you running a server or something?
Steps to reproduce:
- Join world, cables work
- Exit world (Quit to main menu)
- Join world, cables don't work
then that's not closing the game instance.. but that gives a lot more info, thanks.
So, quick theory based off of the info we have so far:
Ic2's energy net handles all power connections. That's something we all know.
Things register to the energy net, and remove themselves.
The issue comes when leaving a world - the info stored by the energy net is not removed, despite no longer being valid. This in some way leads to no energy net connections working at all if a new world is loaded.
This sadly doesn't explain every possibility, especially as this issue can just happen at random intervals. It is however a good starting point in my opinion.
Have you tried breaking and replacing the cables?
Which kind of cable are you using?
I've tried breaking and replacing them. I use mechanism pipes but I even tried replacing with ic2 cables and it still happens. Nothing connects to machines.
confirmed IC2 connections lost after loading. Moved to new chunk, reloaded MC from desktop, worked until load from save, IC2 connections lost after load from save. Broke and moved connections and machines to compact machine, same result. Machines are being recognized by AE2 interfaces. Breaks the pack completely.
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.