Description

User Can hide a 3D widget component that is in world space. However, if they use a widget component that has been switched to Screen space this is no longer possible.

List of ways that do not work for hiding SCREEN SPACE 3D widgets:

  1. Set visibility node by casting
  2. Component is hidden in game (details panel)
  3. Setting visibility via the details panel
  4. Setting draw size to 0,0
  5. Setting Visibility within the Widget Blueprint via the Set visibility node

NOTE: Checking Actor is hidden in game will work if it is done in the details panel. The issue is that it cannot be set dynamically

Steps to Reproduce
  1. Open Editor
  2. Create a Widget Blueprint
    Right click content browser > User Interface > Widget Blueprint
  3. Create an Actor Blueprint
    Right click content browser > Blueprints > Actor
  4. Open the Widget Blueprint
  5. add an image to the designer tab
  6. Click and drag the corners of the image to make it the size of the entire canvas
  7. Compile and save
  8. Open Actor Blueprint
  9. Add a Scene component (within the viewport tab)
  10. Add a Widget Component (within the viewport tab)
  11. Add the New Widget blueprint as the widget class for the widget component
  12. Set space to "Screen" (instead of world)
  13. Open the event graph
  14. Get a reference to the Widget Component
  15. Set the Widget Component to hidden in game
    Right Click Event Graph > Type 'H' > Choose the 'H' Key > Drag off the blue pin of the widget component reference > Drop and type "Set is hidden" > Drag off the press execution pin and run it into the Set Actor is hidden in game node
  16. Add the Actor Blueprint the the level
  17. Click Play in Editor
  18. Press the 'H' key
  19. Notice that the Screen space widget does not disappear

Have Comments or More Details?

Head over to the existing Questions & Answers thread and let us know what's up.

0
Login to Vote

Fixed
ComponentUE - Editor - UI Systems
Affects Versions4.7.6
Target Fix4.8
CreatedMay 5, 2015
ResolvedMay 5, 2015
UpdatedApr 27, 2018
View Jira Issue