Compiling a widget causes a widget component using it in the game view port or a blueprint viewport to stop rendering. Moving it afterwards will sometime make it start rendering again

Development Programming & Scripting UI
, , , , ,
2

This bug doesn’t happen on 4.16 but happens on a fresh project on 4.17 (Flow version)

I also might have found a related bug but a widget that I had updated with a new image didn’t show up with that new image and so it was out of date with what I was seeing in the widget editor, no matter how many times I compiled it or re-added it.

A third bug is that when removing the currently assigned widget from the widget list drop down on a widget component, it wont actually remove it from the blueprint view port editor. It is still there.

I’m going to test a clean version of 4.17.1 rather than this nvidia flow version to see if it still happens.