Single Line Trace by channel not accurate

RARoadkill · July 24, 2014, 1:05am

Having a issue with my blueprints. Have turrets that rotate to face their target, however I don’t want them to shoot unless they can see their targets. So I made a blueprint that does a single line trace and returns true or false if it hits the intended target. However the lines seem to be less accurate the closer the target is to the turret

Sorry for the mess, this function is due for cleaning. it seems to work however up close this happens

the turrets up higher are pointing directly at the turret on the ground. I know this because if I force them to fire they hit the turret dead on. However because the lines are going off in the wrong direction they never get the call to fire.

Any help on getting this to work would be great.

Thanks.

Fenrix_1 · July 24, 2014, 5:14am

Lots of ways of coming at this one.

there is more than one type of trace node, some do boxes, and area based tracing
also you probably can get away without even using a trace using a detection volume
you could use impact point instead of location, impact is supposedly more accurate,
trace complex tickbox may help too

you could cheat this by adding a detection volume around the turret at about where it has trouble finding the target. assume if something is that close, it can see it.

hope that helps.

RARoadkill · July 25, 2014, 1:37pm

How would I use a detection volume, can you point me towards the documentation of that?

anonymous_user_e5b88159 · July 25, 2014, 5:34pm

Here’s the setup I’m using. Originally the LoS function was in the turret BP, but I moved it out to my personal library. Now the function in the turret BP is just a call to the library function:

RARoadkill · July 25, 2014, 5:45pm

This looks like it might do the trick, I will try it next chance I get. Thanks for the reply

RARoadkill · July 25, 2014, 6:10pm

I would like to compare if you don’t mind. my seems to be working but I am always looking to improve blueprints. Still getting the hang of them

anonymous_user_e5b88159 · July 25, 2014, 6:09pm

No problem. Hope it helps. My tracking is handled through a separate function. l can post that as well, if you need it / just want to compare.

RARoadkill · July 25, 2014, 6:53pm

Great, thanks for the posts. you have been a big help

RARoadkill · July 25, 2014, 6:55pm

Yeah I have made that mistake before. What I end up doing most of the time is just making a sphere component or something like that and making the mesh a child of it. then I can do all my rotation other functions on the sphere component and the mesh will follow.

anonymous_user_e5b88159 · July 25, 2014, 6:42pm

Here you go. My turret is two pieces. The base and the barrel, with each turning separately. I did it that way so the base could rotate with yaw, and the barrel could rotate with yaw and pitch. It also gives me the opportunity to hide the barrel section when I destroy the turret, leaving the base behind with some spawned effects. It’s just a little test/learning map for me, so I’ll be posting it in the forums when I’ve gone as far as I intend to with it. Anyway, here’re the pics:

anonymous_user_e5b88159 · July 25, 2014, 6:53pm

Note, on the MakeRot node for the base, you can ignore the 180 rotation for the roll value. When I imported the mesh from blender the settings were wrong and it came in upside down. I was lazy, and rather than reimporting, I rotate it to the right position, and use this to ensure it stays right side up while turning. I’ll fix it at some point…

anonymous_user_e5b88159 · July 25, 2014, 6:57pm

Happy to help.

anonymous_user_642ca581 · October 14, 2014, 9:05am

Did you resolve this? It looks like the trace start is from the turret. I’d try placing a socket at the turrets pivot point and start the trace there.