I tried this and you were correct. It was my debugging that was flawed. I am getting back world coordinates on the component, but the component is not following the main mesh, causing the coordinates I was getting back, to seem as if they were local since they were very close to 0,0,0. The component isn’t attached to the mesh for some reason. I would guess it’s timing due to creating the subcomponent in C++, before the blueprint was finished loading. I will try a deferred spawn and hack the timing for creation. If it doesn’t work, I’ll open a question about that separately. Thanks for taking the time to verify (unfortunately) my flawed debugging.