Issue Description:

Until now I thought it was only me since no one else had reported the issue but in today's episode of DW20's he got the same bug I have randomly occurring for a while.

https://youtu.be/Z6n0hLDZiCk?t=4m33s

What happens:

Conduits and Facades randomly become invisible when holding the YETA Wrench.

Steps to reproduce:

Don't know.

Affected Versions (Do not use "latest"):

• Server
• EnderIO: 3.0.1.139_beta
• EnderCore: 0.4.1.61-beta
• Minecraft: 1.10.2
• Forge: 2185
• Mods: list.txt

yeah, not a problem. Some people report directly to avoid being that visible to their fans, so it's not bad to have this issue to track it.

Already been reported by Dire, and I still have problems recreating it when I need to.

Alright, I couldn't find an issue so I wasn't sure if he had reported it or not.

It seems to happen every time my server reboots/refreshes!

It appears to happen on all connections to an inventory when in insert mode, export mode seems to not be affected in some cases. Also note that it also caused chickenbones translocators to disappear also when sharing the same inventory.

duplicate to #3787

Went around my base after building EnderIO from github, couldn't find any bugged conduits. Looks like it's fixed.

It can happen on any conduit, no matter if it's connected, import, export. I have yet to find a pattern, or a way to reproduce it.

So, if other blocks are also effected, it may not actually be something in Ender IO doing that...

On the other hand, it seems to stick to one of our display modes. So the block is rendered.

I've never seen it affect other blocks, I do get other visual glitches but they seem to be unrelated.

The glitch it seems to happen every time on server reboot. (Not tested on client side.)
Place cables down and reboot/refresh server and you will see the glitch every time!

Edit:
Client Side was not affected. Server Side: The glitch appears to happen when the chunk is unloaded and reloaded,(leave the area and come back). I also noticed that if you connect, break or add to the conduits that are connected in a series, it appears to update and fix the rendering glitch, at least temporarily until the chunk is unloaded again. These are the things I have noticed.

It may be the same thing. I added this "cubes in cubes" display for empty conduit bundles, which would render as empty before.

So what you see here are conduit blocks that have no conduits in them, according to their renderer.

Can you reproduce this? If so, I'd make an Ender IO build with some debugging code for you to test some things.

Everyone who has this problem: Please use build 143 from http://ci.tterrag.com/job/EnderIO-1.10/143/ (or later, I'll leave this in until the issue is finally resolved) and right-click the effected conduits with a stick. You'll find debugging info in the client logfile ("You clicked on TileConduitBundle..."), please post that here together with a screenshot and please describe which output line is which conduit.

Here is some data! See Attached!

Glitch Data for EnderIO.txt

Hope the information helps solve the issue!

Yes, @RobertLSnead, that information is indeed helpful. It turns out the rendering isn't to blame here...the conduit block is indeed empty (on the client).

For you, changing the Yeta Wrench display mode doesn't change anything, does it?

Any (error) messages in the server or client log about writing/reading TileEntity NBT data or sending/receiving network packages?

I really hope so. I could never reproduce it but for my very first try when Dire contacted me on IRC.

Not sure why this was closed? I am getting the following render glitch with ver. 3.0.1.142 beta.

This might be a different bug, if you look on the screenshots and videos we posted the facades outlines don't even render. Yours do.

I was not able to get any render differences from the glitched out conduits, different wrench modes work fine on the normal conduits. I was also not able to find any error messages on client nor server. I have attached the log files for your viewing pleasure.

fml-client-latest.log.txt
fml-server-latest.log.txt

I'm not sure what happened but, I was messing with the wrench modes and dragging it across from glitch to normal and now it keeps crashing when I get on my server. Crash log attached.

crash-2016-12-19_16.14.07-client.txt

see #3931 for that crash

Well, I was able to find another way around that bug lol. I did notice that I can shift click with the wrench and the conduit does drop as normal, this again is only temporarily as usual.

Is there a way to force update the conduit chains? It's strange how it fixes it self when connecting onto the same chain of conduits or if breaking the chain of conduits. Conduits need to be of the same type. This fix is still only temporarily. Not sure how the conduits determine the chain it is a part of? Just a thought.

Your problem is that the conduit's data isn't sent from the server to the client. As this is the job of the base game, and it usually works just fine, I have no idea where to even start looking for a cause.

I haven't forgotten you, it's just that I have no clue what to do. For now try to be consoled by the fact that this is only a display error, those conduits should still work fine.

I am not sure entirely how the code is setup or works but, I do have an interesting idea how to solve the problem. It tends to fix itself with a chain update (break or add to existing chain). Is it possible to check at a given tick to check the chain it is connected to and see if one of the conduits has that state and then force a chain update to force render? Just an idea.

I could add code to the conduits that runs client-side and detects that the conduit list of the is empty, then sends a network packet to the server to trigger a forced update. But, that'd just be a workaround for one type of block. There is a problem getting server data to the client and I see no reason this should effect conduits only. It's just that you don't see it with the other blocks because they render the same was all the time.

I've got the same problem. It's limited to one chunk only, which contains my Mekanism ore processing.
Just updated to the latest version to get some of the debug info. The empty conduits are displayed in The One Probe as Conduit Connector.
I'm also reporting it to the Mekanism repository, because the pipes of it are also gone.

Clientlog, serverlog, modlist
https://gist.github.com/thommy101/995fa39fbf44eb8d46d8a3eb141087cc

Screenshots
http://imgur.com/a/RsDsT

--EDIT--
My issue is resolved after removing the thermal evaporation plant of Mekanism. All pipes and conduits rendered correctly after a relog.