The "Pop-up dialog" device is broken after update

Summary

When the ‘do not close on button press’ function is enabled, all buttons, including the close button, stop working.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Devices

Steps to Reproduce

To reproduce the bug:

  1. Place the “Pop-up dialog” device and enable the ‘do not close on button press’ option
  2. Create a custom widget
  3. Use this widget for the “Pop-up dialog” device
  4. Connect buttons in the widget for any action
  • Start the game and check if the buttons work (they will not work)

To test if your buttons work:

  1. In the “Pop-up dialog” device, do not enable the ‘do not close on button press’ option
  • Start the game and check if the buttons work (they will work)

Expected Result

The buttons must work

Observed Result

the buttons do not work

Platform(s)

all

Video

Additional Notes

Yesterday (that is, before the update) everything worked perfectly

We’ll get someone to take a look.

I can confirm, before the update it worked perfect. Now the response events do not get fired when ‘do not close on button press’ is enabled. Which is the same issue before the previous update of the popup device.

also confirming, button events doesn’t work when using do not close

Thanks, all. We’re checking into it.

2 Likes

Does anyone know of a way to fix this? I can’t publish my projects.

I know you are aware, I just wanted to let you know this is heavily impacting a few things I am working on as well @Flak

I have some work arounds, but they negatively impact the user experience.

1 Like

This is still a problem in v38.00. If “do not close” checkbox is checked then button events do not fire either to verse or even bindings of the popup device to a trigger and check with that. It just breaks. How this makes it out the door is truly confusing. I wish testing at Epic was much much more rigorous and caring for the developers that use it.

3 Likes

still a issue with v38.00 :frowning:

Replying to boost. I am also affected

Still broken after 38.10 update

The latest message from our engineer is that the view binding may be set incorrectly. It needs to be set with a “Click Event” rather than an “onClicked” event.

1 Like

nope, it doesn’t work even when setting it up like that

if this is working for the person who sent the screenshot then I guess the unavailalble options make the diference (set triggering input action or set should use fallback default input action) or this is different kind of issue because it would be weird that something in UMG causes it to not work only on do not close on press

Can also confirm it didn’t seem to solve the issue, I setup the bindings as shown in the picture but they still did not work,

2 Likes

unfortunately this is still not working with verse after 38.10 update

It might be a good idea to have that engineer make a quick video of it working. Just drag a popup device on, set that setting, then write some verse to respond to any button, put a button or two in it and put those settings, compile verse, run it and see what happens. This is what the majority of devs are doing, we just want a popup that allows a player to click a button and it not close AND the responding button to fire an even in verse. That’s it.

1 Like

what is this “Translate response”?? That’s not how the docs shows to set this up (images don’t load on this page): https://dev.epicgames.com/documentation/en-us/fortnite/making-a-mission-selection-screen-in-unreal-editor-for-fortnite and it shows a different way on this page (which is what we all use in the real world) https://dev.epicgames.com/documentation/en-us/fortnite/ui-popups-in-unreal-editor-for-fortnite

1 Like

and finally, I just finished testing this method and it 100% doesn’t work. If the engineer genuinely has a solution, please ask this person to post a video on how to setup a popup device to work with this setting on because nobody can do it in the wild.

2 Likes

I’ll let them know.

1 Like

FORT-989880’s status has changed to ‘Ready for QA’. A member of the QA department is investigating the issue.