Cable components seem wrecked in 4.12:
Those big brown boxes used to be a cable running from a rock to the mountain in the middle.
New cables show nothing at all.
Please fix it up, this is a very useful cosmetic component.
Working fine on my End. If you Converted your Project from a older Version double check if the settings did not get messed up. In Worst case try to recreate the Cable or make a new one. Let us know if that solves your Problem.
As you can see from the initial report making a new cable didn’t resolve it. The settings all looked correct and were identical between project versions.
Hi ,
- Does this occur in a clean, blank project with no additional content or is it limited to one project?
- What steps can I take to reproduce this error on my end?
- Have you run a verify on your engine build to repair/replace broken or missing files to see if this fixes the error?
- Is it the cable component or the material that is causing the error to occur?
I verified the engine when it first happened.
Cables seem to work in a fresh empty 4.12 project, but nothing works in the upgraded project regardless of material or settings.
The artifact geometry doesn’t always seem to happen but the cables are consistently missing otherwise.
To reproduce (I assume):
- Create a 4.11 project
- Add cable actor
- Upgrade to 4.12
Edit: whoa, “realtime” was switched off in my project by default. It looks like it’s the initialization state of the cable that’s wrecked and after that it bounces around and settles down. Maybe change this to a “cables are broken on first frame” bug, as it’s been that way for quite a while and it’s annoying. In 4.11 the geometry wasn’t messed up but cables still spawned energetically and whip all over the place for a while when you press play.
On top of that cables in the editor shouldn’t rely on “realtime” being checked - they should just preview as their resting state.
So did you try to create a new Cable like I suggested? Or did you simply drop in a existing Cable Actor (that is broken) into your scene again? If that does not happen on a Blank Project a fresh recreated Cable should solve your issue.
Actually I read absolutly everything asside from your “Edit” now I can Tell you that you need Realtime enabled so it can go trough the Iterations to find its resting state 
otherwise UE4 would block you until it done all Iterations and thats a really painfull laggy thing if you try to move it around.
Dont mean to be Rude but it sounded like you simply used a old somehow Broken Component thats why I was asking. Not meant to be Rude just wanted to be sure.
@ You’re kind of rude, not really reading anything anyone is saying and not really helping mate.
Finding the resting state is trivial though? And it doesn’t need to be blocking?
Hi Anti-damage,
This is expected behavior.Without realtime on, you are seeing the initialization of the object for the first frame, which could cause artifacting as well as the object simply not appearing on screen for a frame. This should not affect gameplay behavior. Additionally, if you turn on Realtime for a moment, it will allow the actor to initialize, then you can safely turn off Realtime if that is needed/desired for development purposes.