A game I have been playing has been experiencing the issue described in 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.