Problem with the "event BeginPlay" Lock Mechanism

Unreal Courses Talk
,
#1

Hi there,

i am using version 4.14.3

i had a problem whith beginPlay->lock, as it was locking ALL my tiles even the first. it seem first that the unlock was not happening for the first tile.
After debugging with print string it looks like the problem is the OverlapEvent is called/resolved BEFORE the BeginPlay Event, so the first Gate stay red.
i added a delay node of 0.2 before the Unlock Node in the begin overlap chain and it seems to be working as intended : first green and the other gate red (actually orange with green in front, funny primary color).

Don’t know if it is version related or if there is a cleaner solution ?..

Edit : Actually a delay node of 0. works too, but no delay node and the gate stay red.

#2

I am getting exactly the same behaviour. So I’m going to try your work-around until the instructors say otherwise.

BTW I have 4.14.3 also.

Didn’t work, I either get all locked or all unlocked.

#3

More information on what’s happening:

LogBlueprintUserMessages: [Tile_C_0] locked
LogBlueprintUserMessages: [Tile_C_0] Unlocked
LogBlueprintUserMessages: [Tile_C_1] locked
LogBlueprintUserMessages: [Tile_C_2] locked
LogBlueprintUserMessages: [Tile_C_3] locked
LogBlueprintUserMessages: [Tile_C_4] locked
LogBlueprintUserMessages: [Tile_C_5] locked
LogBlueprintUserMessages: [Tile_C_6] locked
LogBlueprintUserMessages: [Tile_C_7] locked
LogBlueprintUserMessages: [Tile_C_8] locked
LogBlueprintUserMessages: [Tile_C_9] locked
LogBlueprintUserMessages: [Tile_C_0] locked
LogBlueprintUserMessages: [Tile_C_1] locked
LogBlueprintUserMessages: [Tile_C_2] locked
LogBlueprintUserMessages: [Tile_C_3] locked
LogBlueprintUserMessages: [Tile_C_4] locked
LogBlueprintUserMessages: [Tile_C_5] locked
LogBlueprintUserMessages: [Tile_C_6] locked
LogBlueprintUserMessages: [Tile_C_7] locked
LogBlueprintUserMessages: [Tile_C_8] locked
LogBlueprintUserMessages: [Tile_C_9] locked

Looking at this, we can see that the locks/unlocks are correct the FIRST time, but then there is a second wave of locking which locks everything. So it doesn’t appear to be a race condition.

#4

Could you push this to your github?

#5

Done.
The code is at https://github.com/Raymon-H/S05_TestingGrounds.git

#6

Because Sam has his as Unlocked by default.

2017-03-25 17_00_01-S05_TestingGrounds - Unreal Editor.png755×480 106 KB

Yet you have your’s locked by default, which means you can get rid of this

#7

Yes, that IS the second round of closes. It appears that I have shot myself in the foot here:

#8

if you take RedBarrier Material by Default you need not Lock function in BeginPlay

#9

Hello Dan
I have bug in ThirdPerson character

https://community.gamedev.tv/uploads/short-url/xN8wVBYtrpiITBYF5OgKtibduJv.mp4

when I firing to AI it’s glitching but this bug is appeared when he is moving not aiming or standing.
first I thought that problem is in Collision, because I have two collision, Head Collision is for HeadShot

image
image.jpg852×763 182 KB

but collision was not problem
may be there is in Animation but I am not sure
have you any idea how can I fix it ?

#10

Is it where upon shooting there’s a quick rotation and back? I believe that happened with Sam’s too.

#11

and why it’s happened and it’s happened only when he is moving not aiming or standing ?
I spend few hours to fix it but nothing. how can I solve it have idea?

#12

I don’t think it happens in the final state so just continue on.

Privacy & Terms