If you have a move or spawn an object too far away line-tracing for dynamic objects will stop working and input will regularly call input release without reason.
Our team and another team had this problem and I’m just posting here to make you aware of the problem.
At the minimum it would be nice if there was thrown an error/log warning if an object comes to far away to cause problems, possibly even automatically destroying it.
We solved our problem but it was very hard to debug. Further information can be found in the original thread.
Thanks for posting additional info. About how far is the line tracing before it loses the hit? I tested this by moving a dynamic object about 500,000 units away from world origin and the line trace would still register a hit.
Any ideas on how to repro this on my end? I know last time we had issue finding a good repro.
We haven’t heard back from you in a few days, so we are marking this post as resolved for tracking purposes. If you’re still experiencing this issue, please feel free to post back here with additional information to reopen the post.