I took a look at your level and it acted as you said that it would. However, I opened up a clean project and could not reproduce your issue. After that I went back to your project and created a new widget and again was unable to reproduce this issue in the project that you provided. While the original setup does cause the error, I am unable to create a reliable test case with the current information given.
Quick questions:
Can you reproduce this in a clean project?
If you are able to reproduce this, can you provide accurate reproduction steps for this issue?
I did find that this works with your current setup and could be a possible workaround depending on the complexity of your widgets.
Steps:
I Duplicated the Widget that you provided
In the Original widget I deleted the scrollbox and textblock
I changed the images Zorder to something higher than the scrollbox’s (I used 3)
I then navigated to the duplicated widget and removed the image
In the level blueprint I made sure to add the duplicated widget after the original (The original was the one with the image and the duplication was the one with the scrollbox and textblock) This causes the widgets to be add to the viewport in the order of Image > Scrollbox and textblock
I hope this helps until another less hackish solution can be found.
I called the project UMG_ZOrderBug because I did also notice I could sometimes get the background to appear if I changed the z orders around
I made the background 1 and the scroll box 2, and then it showed up, briefly, but then when I added new widgets or changed z order of other widgets, it would revert again, so that was not a reliable solution
Please note all reliable testing has to be done in Standalone or commandline version of game.
#Very Worth Noting
Please note I do not experience this bug in standalone with UMG Images that are based on Texture2D brush content, it seems to be only materials.
Thank you for the detailed steps for the reproduction of this issue. I was able to reproduce this issue 100% of the time on 4.6. After that I was able to test this issue elsewhere and found that the problem has been fixed on an internal build and will be available in a later release of the engine. Once again thank you for your time and information.
UPDATE: After further testing I was able to reproduce this internally as well.
“After that I was able to test this issue elsewhere and found that the problem has been fixed on an internal build and will be available in a later release of the engine”
I just tested this on 4.7 and it won’t be in there. Can you provide the link for the Github fix for it? It will be painful to wait another version or so to use standalone. Thanks, I appreciate it!
I just tested this again in 4.7 and it appears to be working on my end. Could you supply me with the steps that you took in order to achieve this issue?
I am using the the 4th preview of 4.7. Is this the same version as the one you are using to create this issue? Would you please attach your project so that I might take a look at it?
I would like first to apologize. It appears I was wrong when I said that it was fixed internally. I must have missed a step in the reproduction process or have done something differently. I tried again today and was able to reproduce this issue across multiple builds. Thank you for bringing this to my attention as well as for you information and time. I will update the known issue with new information.