Because you don't need to and an interface requires a reference to the code that needs the motion controllers. Even though I showed this with a component on the player, it can work with any component, actor any way. Without having a hard reference between the player and that actor.
@@GDXR There is a hard reference, it's just hidden "under the hood." The reference viewer just doesn't show it. But also, the pawn will always be loaded when you use your controller, so a hard ref is not a problem. Anyway, there are many ways, thanks for sharing.
so.... why not just use a interface like everyone else? 😄
Because you don't need to and an interface requires a reference to the code that needs the motion controllers. Even though I showed this with a component on the player, it can work with any component, actor any way. Without having a hard reference between the player and that actor.
@@GDXR There is a hard reference, it's just hidden "under the hood." The reference viewer just doesn't show it. But also, the pawn will always be loaded when you use your controller, so a hard ref is not a problem. Anyway, there are many ways, thanks for sharing.
very queer thumbnail ngl :S