Ok, i tought i was going crazy until i tested this in a fresh setup.
I was having trouble doing a simple line trace for my feet. The problem was two fold in that on start up my feet where always pointing towards the world origin until a one of my other trace functions kicked in and everything worked fine…
Until i was trying to add a new trace that required the right vector of my scene component.
This is where this problem manifested for real. i was testing and testing and testing but the trace just wouldnt happen correctly. So after adding the debug setup in the first screenshot it would always try and trace to the world origin.
BUT WHY??? So i tried a new file, to check if i did something else somewhere that interfered with this, but to my surprise it still does the same thing here.
I simply made a new Scene_Component_BP, added it to the Character_BP and added the debug code to the Scene_Component_BP. Even trying to constantly set the scene components location to my capsule components location does nothing.
This also counts for normal Actor_BPs.
Calling the same debug setup from inside the Character_BP also results in the same problem.
Ah, ok that would make sense. I tought the forward vector would already be carrying my world location, just adding it fixed it.
That FindFloorResult is interesting, but sadly not useful in my case. I’m making a procedural walk cycle so i need a different trace for each of my feet. Since i assume the FindFloorResult works with the Capsule_Component.