Hello! I've encountered an issue while using this mod on my server. From time to time the cables seem to change their rotation and they all face upwards regardless of their position. Their texture looks like the one which appears when the item is in the player's hand. I don't know why this happens and it seems random. They are still working, but the issue is annoying.

Mekanism version: 1.15.2-9.9.11.403
Forge version: 31.1.18

I'm still getting this issue in Enigmatica 6, which does not have Immersive Portals

Actually it might be the TARDIS mod since I added that, I will ask on their gitlabs page

Same issue here. And almost happened at the same time (as the time of this issue).

Mekanism version: 1.15.2-9.9.10.402
Forge version: 31.1.16

+1

I've also noticed that the issue is generally resolved by destroying a segment of the cable, then replacing it, but only temporarily.

Can anyone reproduce this in singleplayer, or does it seem to only occur on servers?

If it would be possible for someone to provide a replication procedure it'll be much easier to track this down.

We've been trying to replicate this on singleplayer for the past 15 minutes but to no avail. It still may be possible on singleplayer but if that's the case it is very rare. On the other hand it happens quite often on multiplayer. It really seems random. My friends say, that it happens when you place some blocks near it, or if you place or destroy a cable. It even happened when none of us where doing anything that was directly connnected to the bugged cables. If we spot something on our server I'll write it here.

Interesting. Even if it’s just reproducible on a server, a rough reproduction procedure could really help. I wasn’t able to get it to happen in my own server testing, although I didn’t try breaking or placing adjacent cables very much like you mentioned.

We've got other mods installed alongside with Mekanism but I doubt that they cause any interference. We use only Mekanism and Mekanism Generators from the Mekanism family. One guy on a discord channel suggested that this happened to him when he quickly entered previously unloaded chunks.

I will try to reproduce this on singleplayer and will provide the info asap.

Really appreciate the insights, all of these are really helpful. If you notice anything else interesting please let us know. I'm making this my priority over the next couple days, hopefully we can get it figured out.

You're welcome. The mod is awesome and definitely worth developing so if we can help we are happy to do that. We found some new behaviours about the bug, I will upload some photos with explanations in a few minutes.

Sometimes when this happens it also shows that the cable is not transporting anything. After breaking and placing again one cable it goes back to normal. It functions properly despite not displaying any energy going through the cables.

Here are two perspectives of the same cable. Sometimes just the content of the cable is not shown properly.

We found out that sometimes when one player rejoins the game it fixes the issue for the other players.

All of the above happened after teleporting to that place from other far away place. I might be wrong but I suspect that even alt-tabbing from the game can cause this issue sometimes.

I notice that in your recent screenshots it appears that the bugged models are oriented laterally rather than vertically. Makes me think this is a model caching issue. Do the same cables screw up in the same way each time you teleport back from far away?

It doesn't happen everytime we teleport, just sometimes. And yes, they always end up the same as on the screenshots provided. Vertically placed cables seem to be alright, but when they change direction from vertical to horizontal it shows that they are in the "default" state too I think.

Here they change direction but are still in the "default" state. So I think that the vertical/horizontal rotation doesn't matter. It just ignores the rotation and gives them wrong state.

Question- to fix the issue, am I correct that you can simply break and/or replace a cable and they will go back to normal? Also, is it only cables connected to the modified network or all cables in view?

In my experience, breaking and replacing a cable temporarily fixes it, but since the issue occurs intermittently, it will go back to the "default" state. This temporary fix only affects those on the modified section of cable in my experience, not the entire network or all cables or all cables in view.

The suggestion that it happens when transitioning into an unloaded chunk seems likely. If the issue is tied to state being out of sync between server and client that would also explain why it hasn't been reproducible in single player.

By modified ‘section’ of cable, I’m guessing you mean all cables connected to the cable modified? So if you have 5 connected cables and they’re visually broken, breaking and replacing one will temporarily make them all function properly again?

I noticed that despite the transmitter not rendering properly, the contents seem to continue rendering. That’s strange, as it means the client is still getting the sync packets from the server.

Yeah, that is correct, it would only fix those 5. Any other bugged cables that are not connected will stay bugged regardless of them being in player's view.

One of my friend says that sometimes when he fixes one set of cables, other gets bugged, but he also states that it is not a rule and he doesn't know whether it causes it.

@pupnewfster has committed two changes which should hopefully fix this issue. One was actually a packet range calculation mistake which would cause the networks to not sync to the client. I'm marking this as 'fixed in dev,' but we won't close it until you test the new build and don't experience any problems. Hopefully we'll have a new release out soon.

We've pushed Mekanism 9.9.15 to Curse with the mentioned changes. I'll leave this open to give y'all time to test it out. Let me know if you still encounter the same problems; if not, we'll call it fixed 😄

Still able to reproduce, unfortunately. I was again able to temporarily fix it by destroying and replacing a segment of cable, but I teleported out and back in to the chunk and they all reverted to their vertical state again.

I'll reiterate what Iwo-Witterel said - seems cables are semi-randomly falling back to their vertical state, but still function normally.

I actually have not seen the issue they observed though where the cables appear empty; every time the issue has happened to my group, it has been like the first screenshot, where the energy/liquid/gas/items are still flowing, but the cable orientation is vertical.

Sad :(

Just to be sure, both your client and the server are using the latest version, correct?

Yeah, I did update both. An interesting sidenote that I just observed though is that the issue now seems to be localized to a smaller area when teleporting in/out of the chunk. Haven't been able to determine if that's a rule or a fluke yet, but it looks like just the chunk I teleported to is broken and the rest is fine.

Tried to reproduce a few more times, and the chunk boundary seemed to be a fluke. Subsequent attempts seemed to just affect random sections of cable. I do think the issue is occurring less frequently now, but that could be due to other factors (less load on the server, since I'm just teleporting back and forth as opposed to actually building/playing).

I think your suspicion about caching is probably spot on, considering that the issue happens pretty randomly and seems most likely to happen when loading/unloading chunks.

I've pushed a somewhat inelegant fix which hopefully will solve these problems. It'll be ready for you to test soon.

We've updated the Mekanism version to the newest and the issue still persists :(

This should be fixed in 9.9.16, which is now up and on curseforge. If not please comment and we can re-open it (though we will be entirely out of ideas of how to potentially fix it if it is still broken)

Unfortunately still seeing the issue on random sections of cable. It now seems to sometimes resolve on its own, sometimes resolve when you destroy/replace a section of cable, and sometimes doesn't happen.

Out of curiosity is that a chunk border where that image shows them being still broken?

Does it depend on the version of Java being used?
May I ask about your Java version?
I'm still using Java8

Sorry @pupnewfster haven't had a chance to play since then, so I'm not sure if it was a chunk border, but I don't think so...

We are also using Java8.

Should be fixed in 9.9.18, apparently accidentally referenced it from the commit in a way that closed the issue even though it is not released yet.

v9.9.18 is released, please let us know if you encounter the issue again!

Bad news, it still doesn't seem to be fixed. I just updated to 9.9.18, and the cables still go back to their vertical state. I replaced the cable (which fixed it), unloaded the chunk by flying away and then flew back. When I got back the cables were vertical again

Can you please provide a list of mods in the pack.

I'm not playing in a pack, I've manually downloaded these mods (not sure if that is usefull info but still).

I have also tried to create a new server with just mekanism and see if the issue is there too but I haven't been able to recreate it (so it might be a mod conflict after all). I'm not sure what is causing it on my main server either so I can't be sure of that. Anyway here are the mods:

https://gist.github.com/ocram9/81edf7801ad32b5f767db4df877c18c5

By pack I meant the group of mods you are playing (not necessarily a prebuilt pack). So thank you for the list. Are you able to reproduce this issue without Immersive Portals? Backup your world first so that removing the mod doesn't break your save as you can revert to it after testing.

Removing immersive portals seems to have fixed it :)
Is the compatibility fixable on your end or should I contact the immersive portal devs? If it is even possible to make them compatible

Going to go ahead and close this issue then as I believe it is qouteall/ImmersivePortalsModForForge#49 given based on their response in that issue, my guess is they are overriding forge's IModelData system.