CharacterMovementComponent has inconsistent owners in the packaged shipping build
We're experiencing some issues with our character pawns not moving correctly in the shipping build as in the editor build in 4.12.
After some debugging, it seems that the culprit lies within the GetCharacterOwner() function of the CharacterMovementComponent:
In the shipping build, GetCharacterOwner() and GetPawnOwner() of the CharacterMovementComponent are returning the default class object of the pawn we're expecting, but GetOwner() is returning the proper owning actor.
In the development editor build, each of these functions return the proper instance of the owning actor.
From our testing, this issue is not present in the 4.10 shipping build.
I am marking this topic as resolved for tracking purposes, as we have not heard from you in a few days. If this issue persists, feel free to respond to this thread. For any new issues, please create a new Answerhub topic.
Have a great day
answered Jun 27 '16 at 12:07 PM
Sean L ♦♦ STAFF
Follow this question
Once you sign in you will be able to subscribe for any updates here