# Is UE-51650 still being worked on?

**URL:** <https://forums.unrealengine.com/t/is-ue-51650-still-being-worked-on/737164>\
**Category:** Feedback & Requests\
**Tags:** unreal-engine, bug-report, question\
**Created:** [December 27, 2022, 7:11pm UTC](https://forums.unrealengine.com/t/is-ue-51650-still-being-worked-on/737164 "2022-12-27T19:11:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![MrPiggens](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@MrPiggens](https://forums.unrealengine.com/u/MrPiggens)\
**Post date:** [December 27, 2022, 7:11pm UTC](https://forums.unrealengine.com/t/is-ue-51650-still-being-worked-on/737164/1 "2022-12-27T19:11:50Z")

</div>

A game I have been playing has been experiencing the issue described in [UE-51650](https://issues.unrealengine.com/issue/UE-51650) a lot, and I just found that post which seems to imply it’s a bug with Unreal Engine 4 and not something wrong on my end (I have tried a ton of stuff). The page marks the bug as a “Non-Issue,” so does that mean it’s no longer being worked on since Unreal Engine 5 is out? Is there anything the developers of the game could do to mitigate the issue? It sounds like people were still trying to figure out the different sources of the bug, so I assume there’s no known way to provide a band-aid solution to it.

Any help would be greatly appreciated. Thank you.
