Nativized Assets - Latent Action Manager callbacks failing / skipping code

Development Programming & Scripting Blueprint
, , , , ,
1

Hey -

How are you testing this behavior? Can you provide screenshots of your blueprint to help me match the setup you’re using? How are you using the Latent Action Manager? Please provide reproduction steps to help me test the behavior locally.

2

Hey -

Have you been able to create a sample project to show the issue you’re having? If not, can you provide setup/reproduction steps and/or screenshots of your blueprints to help me reproduce the issue locally?

3

Hey -

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 follow up.

Cheers

4

Altho nativizing assets seems to work much much better in 4.16, there are some serious issues with the Latent Action Manager. Some delays will not continue to execute after the time is up and skips to execute code.

I will investigate this further, but debugging in visual studio so far has shown clearly that latent action callbacks of delays do no execute or end up executing seemingly random case states further down the line instead of their correct callbacks.

5

Well the source files are generated after nativizing the bp assets, after which its just a matter of attaching visual studio debugger to the process and stepping through the code with breakpoints and traces.

We spend hours analysing what was going on, and in the end we found that after executing a delay, the latent manager should resume to execute the next case after the delay was completed, but instead executed some random case which either also would call the latent action manager or something, it is still unknown why it jumps to a seemingly random case state and skips a chunk of the code/script.

There was no special case use of the Latent Action Manager, it is what handles delays and such in the unreal engine core and the project only used nativized blueprints, no custom c++ work.

I’ll see if I can put together a sample project to demonstrate the issue. Other then that, what seems to be the problem is delays, array for-loops etc.