SpawnDefaultController doesn't send ReceivePossessed blueprint event

In my game blueprint I’m spawning a Character and then using SpawnDefaultController to create the Controller and have it possess the character automatically. This works fine, but I never get a RecivePossessed event for the Character.

We have a blueprint Character (MyCharacter) and blueprint AIController (MyAIController). MyAIController is the default controller for MyCharacter. Here is the level blueprint:

That works fine (MyCharacter and MyController are spawned in the scene)

Here is the event graph for MyCharacter, the possessed event never happens.

I’m running 4.1 binary from the launcher on Windows 8.1.

Poking through the engine I have found what I think is the problem.

At Pawn.cpp:312 we have already set Controller to the new controller:

Controller = GetWorld()->SpawnActor<AController>( AIControllerClass, GetActorLocation(), GetActorRotation(), SpawnInfo );

And later there is a check at Pawn.cpp:484 which fails:

// dispatch Blueprint event if necessary
if (OldController != NewController)

Hi Clapfoot,

Thank you for reporting this to us. In order to help us reproduce this issue, we could benefit from some additional information. Please see this post for some bug-reporting-guidelines which can be very helpful, and then Edit your post with any additional information you can provide. In particular, any information you can provide that would help us be able to reproduce this issue would be great.

Thanks.

Ok, i’ve fleshed out my explanation.

Thanks for the additional information, Clapfoot. I did a very quick setup to match what you have, and I was able to get the second Print Screen to fire from the Event Possessed node. I do have a quick clarification question, though. You mentioned using 4.1: Are you on 4.1.0 or 4.1.1? I tried using 4.1.1, and I am using . I need to get access to a computer using Windows 8.1 and try again.

I tried again with a build from source - that version is 4.1.1-0+UE4 on Windows 8.1.

Hi Clapfoot,

I apologize for the delay in getting back to you on this issue. Have you upgraded to version 4.2? If so, are you still experiencing the same issue?

Hi Clapfoot,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.

Thank you.