When using Auto Possess to possess a pre-placed Pawn, the PlayerController’s “On UnPossess” event is being triggered immediately after the “On Possess” event. I’m only getting a single Possess event, so the last event I receive is the UnPossess event. The Pawn does still receive input as expected, and the PlayerController’s GetControlledPawn returns the correct Pawn except during the UnPossess event - then it’s null.
I was able to reproduce this with a fresh Third Person Template project - just added a new PlayerController blueprint, and added Print Strings to their On Possess and On UnPossess events - I get the “Possessed” message first, then the “UnPossessed” message, then nothing, but the Pawn did seem to stay Possessed (I can move around as normal).
This does not seem to happen when spawning from Player Starts (I only get the Possessed event) - only when auto possessed.