[BUG] Function parameter not saving (UMG)

Development Programming & Scripting UI
, , , , ,
1

I an issue with UMG where when I attach a parameter to a function on a widget it wont save the change.

Here is a video of it in action. - YouTube

This UMG widget has an interface implemented, and when the interface event (‘Use’) is called then it gets a reference to MyCharacter actor, which contains a reference to the HUD widget, which contains a reference to my SkillBar widget. I then want to call a function on the SkillBar widget with a parameter that takes a struct (‘Skill’)

From what I have tested :

*Making a modification to the execution path (white wire) will save.

*Breaking the Skill parameter from the Event Use saves.

*Attaching any struct to the ‘Add Skill’ function will not save ( this includes the output from the Event Use, and just creating a new Skill object).

I really can’t seem to figure this one out. If you need any more debugging of this issue please let me know, as I can’t really work on the project with this bug anyway…

2

Hello thunderbeans,

Thanks for the information given. However, I have a few questions for you that will help narrow down what issue it is that you are experiencing.

Quick questions:

  1. What version of the engine are you using?
  2. Can you reproduce this in a clean project?
  3. If so, could you provide a detailed list of steps to reproduce this issue on our end?
  4. Can you provide screen shots of any blueprints that my be involved with this issue?
3

1). Version 4.7.2

2). No I’m afraid I cant, I’ve tried multiple different ways.

3). /

4). Im not too sure what other blueprints may be effecting this? It seems to be something with the actual saving of the blueprint not the execution of it.

4

Hello thunderbeans,

Would it be possible for to send me a copy of the project that you are having issues with so that I can take a closer look?

5

Hello thunderbeans,

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.