Key event doens't trigger custom the first time in sublevel

Isjtar · February 28, 2019, 2:34pm

Hello,

I’m using keys to make sublevels visible and trigger a custom event that launches the sequence of that sublevel.Strangely I need to press the key twice most of the time for the sequence to actually trigger. While running I can see that the first time, the event is not going to the sublevel blueprint. I press again and everything is as it should.

I’ve tried triggering twice, with a delay, inverse the order, nothing seems to work.

The levels are set to always loaded.

Any ideas?

Thanks!

Isjtar

Everynone · February 28, 2019, 3:21pm

Do you use the J key in any other blueprint? Keys are consumed as default. Put a print string directly after it, to see if it’s the key that fails or the execution flow further down the line.

Isjtar · February 28, 2019, 3:27pm

I don’t. Also I just replaced it with another event (MIDI), same problem.

Everynone · February 28, 2019, 3:31pm

So if you just mash the key, does it print inconsistently?

I don’t. Also I just replaced it with
another event (MIDI), same problem.

You replaced a key with an event - so how are you triggering that event now?

Isjtar · February 28, 2019, 3:40pm

Yes if I mash it, everything it’s good, in the persistent BP. It’s only in the sublevel BP that things don’t happen like they should.

If I put the key in the sublevel BP it prints properly as well.

The MIDI event is triggered by a MIDI controller, through OnMIDIEvent.

Everynone · February 28, 2019, 3:55pm

What’s up with the Remote Event - I’m not quite familiar with this. How does it work?

Isjtar · February 28, 2019, 4:24pm

You give an event a name and you can catch it with the same name in another BP.

Everynone · February 28, 2019, 4:25pm

Is this from a plugin? Or something you exposed to BPs? Nvm, found it. Never used it before…

So essentially, this thing does not seem to do its job? You can clearly see the key event go off but it does not always deliver the event call in a sublevel?

Is that the case here?

Isjtar · February 28, 2019, 4:28pm

No it’s a feature since a while, not very documented.

Everynone · February 28, 2019, 4:40pm

The level has to be visible to fire an event. As weird as it sounds. Could this be the problem here?

Isjtar · February 28, 2019, 4:50pm

Yeah I’m thinking that as well. I tried before but I must have missed something. If I add a delay long enough, it works.

This is no solution though as it flashes to the player camera and only then starts the sequence…

Everynone · February 28, 2019, 5:28pm

Yeah I’m thinking that as well. I
tried before but I must have missed
something. If I add a delay long
enough, it works.

The delay you’re talking about goes between the level visibility and the event call, right. So if you delay the event long enough, it does trigger? Nasty.

Delay 0 does not cut it?

Isjtar · February 28, 2019, 5:34pm

Yeah that’s where it goes. No, i need at east 0.02 and I’m willing to bet it varies depending on how heavy the content. Super nasty.

Everynone · February 28, 2019, 6:05pm

Maybe like this:

Isjtar · February 28, 2019, 6:39pm

Yes, this helps, thanks!
Still get a flash but at least not an arbitrary delay time.

Everynone · February 28, 2019, 7:22pm

Maybe you can mask it with a fade away widget of sorts. Many quirks in the engine, still

Good luck with the rest.