I have the same exact issue. Transparent cables =) Have you found any solution?
I am having the same exact issue, I can’t find any way to fix it
Hello,
This was already reported as an Engine Bug UE-149249
Issue is related to Unreal 5.0. It does not occur on previous versions.
Unfortunetly we have to wait for ver 5.1
Meanwhile there is a partial fix for that.
You can attach the End of cable to not moving object if it possible in ur projects (it should be in the prototype posted above)
When the End of cabel isn’t moving, the issue will not occur.
EDIT: Also please upvote this ticket UE-149249
Cheers
2 Likes
I just voted, thanks 
Only my start of the cable really moves, the end location for my grapple hook only moves when it needs to attach to a new grapple spot and then stops moving but stays invisible. Not just in the sky it has issues on everything but weirdly enough the grey grid prototype material makes it more visible? Weird stuff.
I had same issue, using attach end to component name and socket name in cable tab instead using parent socket fixed mine, dont know if that apply to yours.
Guys, I have just discovered that cable renders properly when non-ninite mesh is on the background and it turns invisible in front of nanite meshes and in front of the sky.
1 Like
‘Attach end to component’ didn’t help in my case, ‘attach to socket name’ - too. Neither either of them, neither both.
Guys, some good news, today I noticed that the issue was fixed 13 days ago: https://github.com/EpicGames/UnrealEngine/commit/65733c97e85aaf5bb3f3816063cae83d24a6843b
So, we’ll have to wait until the next UE5 update unless you’re using the source version.
Ah fingers crossed it’ll fix any cable issues, thanks for letting us know
1 Like
Temp Fix found,
- Give the cable component a material
- Make the material translucent, Default lit, Surface
- Give the material a base color or texture
- Set the opacity to 1 of the material
- Fixed
#A_ColtZz Fix
13 Likes
It works, thank you. Hopefully, Epic will include the their commit to the next 5.0.3 update.
Unfortunately, I don’t see there the UE-149249 fix for the cable component. Not sure why. Any ideas?
1 Like
I belive hotfix-patches are only pushing fixes to bugs with high severity like crashes, stability issues or issues afecting main functionality of engine.
Probably every fixed bug needs to be retested by their internal QA before merging code into main branch. This one is more of a minor visual issue so they don’t even bother about it for now.
1 Like
I see. I’ll wait a little more and probably end up switching to the source version of the engine in order to paste the fix into the cable component class.
1 Like
Temp Fix found, - Set the material to translucent material.
That fixed it for me.
1 Like
Thank you very much, problem solved!
Problem solved. Thank you. Hopefully it will be fixed for 5.1
Hello all
Unfortunately it wasn’t fixed at 5.1. We were having problems not only with nanite but with metahumans, the cable component wasn’t rendering proprery.
We tried the opacity solution but, when you use it with fog, the cable becomes highly highlighted. After exaustive tests, we managed to find the problem: The Anti-Aliasing option at movie render queue
For some reason, cable components with opaque materials don’t render properly when you use more than 1 step of Temporal Anti-Alias… we used to use 8 steps.
When you use only one step, it renders propery, so you don’t need to use opacity and have problems with fog.
Hope this was helpful!
1 Like
And there’s still no solution for realtime applications. Temporal Super Resolution AA (on by default) introduces this issue. Switching to TAA doesn’t make much difference. Other AA solutions are trash looking.
This is too late and we have new engines too but for people who are using 5.0 for some reason and having the same issue:
I found a way around hope it helps.
In the details panel for the cable under Rendering section check “Use attach parent bound”
This seems to fix the issue.
Cheers.
