GetHitResultUnderCursor sometimes fails when clicking on landscape

Jonathan_Dorman_1 · December 19, 2014, 10:48pm

This might be related to another issue I’m working on with landscape collisions. I’ll keep looking into it, but I won’t be able to work on it again until Christmas vacation is over.

Thanks for your patience.

undercover · December 20, 2014, 1:07am

That’s no problem, I will be having Christmas vacation as well Sounds good that you might have identified the source of the problem.

undercover · January 8, 2015, 11:06am

Hi again! Just wondering what the status is with this issue, will a fix make it to 4.7? Please let me know when this issue is solved. Thanks!

Jonathan_Dorman_1 · January 8, 2015, 3:06pm

Hi ,

We’re still investigating the cause of the bug. A fix will not likely be included in 4.7.

anonymous_user_b9532c9a · March 13, 2015, 5:26pm

Hi ,

I apologize for the delay in response. I tested your demo and was able to reproduce this on my end. I have entered a bug report, UE-11821, to be assessed by the development staff.

undercover · March 16, 2015, 12:28pm

Okay, when do you think we can expect this issue to be solved? 4.8?

anonymous_user_b9532c9a · March 16, 2015, 5:11pm

Unfortunately I do not have a timeframe of when a fix will be available.

anonymous_user_b467b02b · June 12, 2015, 2:18pm

Hi, I have the same problem, ie. the blueprint function “GetHitResultUnderCursor” sometimes returns Vector(0,0,0) in a landscape. When trying in a plane it works like a charm, the problem occurs with a landscape.

When is this bugg correction planned to? It seems like a basic functionality to support, click and move a pawn in landscape. Thanks!

anonymous_user_b9532c9a · June 12, 2015, 3:24pm

Hi Slate128,

This bug is still being assessed, if your landscape is a flat plane you should be able to get it to work correctly by slightly sculpting the landscape with the landscape tool.

anonymous_user_624ad6e91 · July 31, 2015, 8:39pm

has this bug been fixed for 4.8? Iam not getting issues with hit under trace, but iam getting this issue under object. (Only hits if its a certain radius away from my character).

anonymous_user_b9532c9a · August 2, 2015, 3:13pm

Hi Venros,

This bug report is still being assessed by the development staff. Unfortunately I don’t have a timeframe of when a fix will be made available.

anonymous_user_73094a6c1 · November 12, 2015, 12:06pm

I got this same bug unfortunately. I can send my project if need be. 4.9.2

anonymous_user_3dfb2cf5 · November 17, 2015, 9:17am

I got that bug, too.

Weird thing: as soon as I sculpt a small area in a landscape components the error doesn’t occur in that component anymore. The bug only occurs when the landscape component is completely flat.

So I made this blueprint:

and added a landscape with default values. Then I made a small dent in the landscape component on the right:

Now the ‘No hit’ bug will not occur in that component anymore. In all other components the ‘GetHitResult’ will return false at a lot of locations.

Hope that helps someone.

anonymous_user_73094a6c1 · November 25, 2015, 1:12pm

Any of this bug getting fixed? I’m using 4.10

anonymous_user_b9532c9a · November 25, 2015, 2:19pm

Hi ,

As mentioned here: Sometimes GetHitResultUnderCursor returns 0,0,0 on landscape - World Creation - Epic Developer Community Forums

This issue is specifically caused by a PhysX accuracy error. We have brought this to the attention of NVidia and we are awaiting a fix on their end.