Event Possessed triggers without being possessed?

Mik2121 · August 30, 2015, 1:27pm

Hello everyone. I’m working on getting a vehicle working on a 3rd person blueprint project. I was able to set it up so that the player can ride it when getting close and pressing a button. What I’m trying to do now is set visibility to a skeletal mesh inside the vehicle pawn, and set it to visible plus play an animation.

The way I have it set up, Event Possessed executes ‘Set Visibility’ and then executes ‘Play Animation’, and with Event Unpossessed it executes ‘set visibility’ to off. The mesh is by default invisible as well (so I can’t see it on the placed vehicle blueprint). However when I start the game, the ‘Event Possessed’ kicks in even though it’s not the pawn currently possessed. If I ride the vehicle (ie, possess it) nothing changes, then when I get down (ie, unpossess) the mesh goes invisible, and from there it works as expected.

![alt text][1]

So, why is the ‘Event Possessed’ executes automatically as soon as the game starts? Did I miss something (probably)?.

Thanks in advance,

Mik2121

darorck · August 31, 2015, 11:17pm

Same issue here using 4.9 and ShooterGame template.

Gunnar0 · September 1, 2015, 12:07am

So you are trying to add your player mesh into the car, correct?

darorck · September 1, 2015, 12:16am

In my case, I have a player that possess a turret, everything works fine but I have a Boolean variable (IsAlreadyTaken?) connected to “Event Possessed” to check if the turret is already taken and it triggers when the game starts.

Shadowriver · September 1, 2015, 12:19am

What controller trying to possess it? You can check that from event argument

darorck · September 1, 2015, 12:26am

When can I find the event argument?
Adding a breakpoint to the EventPossessed node, looks like the the value is the turret itself, quite odd!

Mik2121 · September 7, 2015, 1:38pm

I haven’t been able to fix this yet, but thanks for the comments. Darock, did you get your stuff fixed? I tried using the boolean too but no luck!

Shadowriver · September 7, 2015, 3:24pm

did you check the controller that trying to posses?

darorck · September 7, 2015, 3:47pm

@Mik2121 I’m checking for the controller class to avoid the problem for now.

@anonymous_user_f5a50610 Yes, the controller than is trying to possess is itself (the turret) It is a child class so I am not sure if it could be related.

Shadowriver · September 7, 2015, 6:08pm

I’m asking Mik2121 as it is his quastion i read above about your case

Mik2121 · September 8, 2015, 1:11am

@anonymous_user_f5a50610 I’m currently not checking, but I will do as soon as I get home today (I’m at work now!). I will probably go with what Darock is doing for now.

@darock thanks!

anonymous_user_563485f5 · April 13, 2016, 9:24am

Hi,

I know this is an older issue but it should be fixed with these settings under Class Defaults.

Fritsl · April 14, 2016, 7:55pm

And to compliment aJarman’s excellent info, these seettings are found here:

hillbro · January 9, 2021, 7:53pm

6 years later and this is still happening on UE4

hillbro · January 9, 2021, 7:54pm

This fixed it for me!

eatyosandwich · January 21, 2024, 11:56pm

Sorry this thread is a bit old but I can help on understanding this “On Possessed” Node to anyone else having this issue. The on possessed node is called on Possession by any controller, including player controller OR AI controller. I was also having this issue until I realized that “Event Possessed” meant any controller. So Yes, the argument that the OP posted would be a correct way to fix this if you plan on having multiple controllers possess an AI, as that is also the plan in my current project. Here’s how I implemented this fix

This way you can still have an AIC auto possess a character or pawn if you would prefer that method