AttachTo not updating StaticMesh location with Physics Enabled (MotionController)
I've been trying to get this working for the last...day more or less, and it's driving me absolutely bananas!
I've been following the Unreal video for creating interactions with motion controllers, and it's partially working. I'm spawning and deleting objects no problem, but I can't for the life of me get "picking" objects to work. (Such as in the can-toss demo they're talking about)
I have MotionControllers, which have a collision model of
I also have a basic Sphere. This is a blank SceneRoot, with a child StaticMesh with
OK, so in my mind that all looks fine. I have created Blueprint Events to handle object overlaps as per the video (for the left controller):
It checks to see if we're currently holding something, and if not, we set the in-range boolean to true, and set the current "available" object to a reference to the BP_Ball object that we're intersecting with. If we move out of range, we unset the in range boolean (assuming that we aren't currently holding something).
Assuming that we are overlapping, we should be able to pull the trigger on the Left controller, and
Now, this is where what i've done differs from what's in the Video. In their video, I think they are somehow passing in a reference to the StaticMesh itself, as their node from Object to the AttachTo target looks like this:
Whereas mine looks like this:
The reason I think this is because later on in the video, you can see that their BP_Ball hierarchy is the same as mine, but they seem to be referencing the name of the StaticMesh:
For reference, my trigger logic
OK, so if I don't set
Likewise, if I set
This whole issue hurting my head. I know i'm close to the solution, but I just can't get the pieces to fall into place!
asked Jun 01 '16 at 04:12 PM in VR
So, turns out that the object cast in the Pickup and Drop routines was the culprit.
I had incorrectly assumed that the DefaultSceneComponent was of the same object type as a Utility Scene Component. However, it turns out that DefaultSceneComponent is actually a SimplePrimitive, with a collision prim, which would explain why adding a new collision sphere to the scenegraph suddenly caused the BP to work.
Follow this question
Once you sign in you will be able to subscribe for any updates here