Line Trace or collision not accurate?

Development World Creation
, , , , ,
1

Hi! I have a problem regarding the collision using a ‘Line Trace By Channel’ or ‘Get Hit Result Under Cursor By Channel’. There is sometimes an offset with the collision. When i activate the Show Collision option it looks good.
I have the option ‘Complexe Trace’ on.
I use line trace to stick a spline along a mesh.

I have no idea where it could come from…
Thanks!

345932-collisionbug.png

2

Yes he got collision, you can see it on the picture (i activated show collision). The purple squares show impact Point, collision work but there is an offset.

Another exemple without debug info and the mesh is hidden this time:

345922-exemple2.png

3

Here is another image of the mesh, i dont know if it can help

345924-meshexemple.png
345924-meshexemple.png559×508 252 KB

4

The red line means it’s not finding anything. Does the mesh have collision?

5

Could it be the floating point error?

  • how far away from the world centre are we
  • how long is the trace

Could you show your tracing method?

6

Hmm, really don’t know, sorry.

I would try just tracing from a stand alone blueprint to the mesh and move the blueprint around a lot to make sure your tracing works the way you think it should.

Apart from that, there can certainly be some gotchas to working with splines.

7

I dont think it’s floating point error,

  • World location -800x/1100y/1400z
  • Both Linetrace and Get Hit Result Under Cursor By Channel reproduce the bug… (+the line trace is not long, less than 1000 units)

345999-linetraceexemple.png

346000-linetracelength.png
346000-linetracelength.png997×472 248 KB

8

Can you show the vector code going into the line trace? ( that’s the crucial bit ).

9

Yes, if i can’t fix the ‘collision’ bug then i will fix it by detecting the offset points

10

I dont think the problem is here, line trace look good :frowning:

346013-getstartandendpoint.png
346013-getstartandendpoint.png1390×328 113 KB

346014-functionlinetrace.png
346014-functionlinetrace.png823×508 84.1 KB

11

Hey, i just noticed that the bug is reproducing on specific areas on the mesh…

346015-areacollisionbug.png

12

That’s worth following up…

13

Look like the line trace passe sometimes through the first collision, idk if it that can be that or not

346018-linetracethroughmesh.png
346018-linetracethroughmesh.png1435×637 415 KB

346019-mesh.png
346019-mesh.png571×841 383 KB

14

I dont know, I never used ‘show player collision’ but I don’t think it displays anything useful in my case

346070-showplayercollision.png

15

Ok i found the bug it’s probably a floating point error on collisions. It’s because I resized the mesh x100 after the import, the collisions are good if i scale before the import. It’s still weird that the ‘show collision’ option doesn’t show errors…

16

Ah, but show player collision would have probably alerted you to it?..

17

If the collision was off from scaling, you would see it here.

18

Collision look good but errors still here :frowning:

346091-showplayercollision2.png
346091-showplayercollision2.png874×595 21.3 KB

19

Hello,

We’ve made a switch to a new bug reporting method using a more structured form. Please visit the link below for more details and report the issue using the new Bug Submission Form. Feel free to continue to use this thread for community discussion around the issue.

Thanks,

20

Out of sheer curiosity how far does the trace penetrate through the mesh?