I think I have discovered a bug in UMG (in 4.26, but it also happens since 4.24), which can be visible in the editor as well as in the build. It occurs when you display a progress bar in a retainer box and play in different resolutions. I don’t know what it depends on, but depending on the position of the retainer box + progress bar combo and depending on the resolution of the viewport (or in the build the window), the progress bar is displayed incorrectly and looks like it is filled, although its percent is not filled. I have made a video here to illustrate this better:
Please tell me this is a bug that can be fixed. As I work with progress bars and retainer boxes, this is a huge problem for me, as I blend the actions of the progress bar (not only fill and background), with a retainer box.
Edit: I have tried to submit a bug report via bug report form, but when I clicked “submit” it just ended up in a never ending loading screen and the bug did not submit. So I’ve collected the infos of the bug report form in a pdf file. retainerbox_BugreportForm.pdf - Google Drive
Hello there, I have submitted the bug under the Case # 00276144. Are there any concerns about creating an issue for this @ staff? Even though it may not be a major issue, the bug is 100% reproducable and also affects a build.
Yikes, this is a tricky one. I spent a few hours trying to figure out wtf was going on and still couldn’t pin down the cause. After finding this post I can confirm I’m experiencing the same issue. I’m using UE 4.26 installed from the launcher.
I guess for now I’m going to remove the retainer box, which seems to fix it, but is undesirable because I think it will result in a considerable performance hit.
We’ve made a switch to a new bug reporting method using a more structured form. Please visit the link below for more details and report the issue using the new Bug Submission Form. Feel free to continue to use this thread for community discussion around the issue.
Hey , using chrome debugger tools I was able to determine the submit async HTTP request is failing with the error below, which indicates the “affected versions” picklist item “4.25 Plus” has an invalid value which is causing the request to return an error.
After omitting that option I was able to submit the report.
{“actions”:[{“id”:“275;a”,“state”:“ERROR”,“returnValue”:null,“error”:[{“fieldErrors”:{},“pageErrors”:[{“statusCode”:“INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST”,“message”:“bad value for restricted picklist field: 4.25 Plus”}],“index”:null,“duplicateResults”:[]}]}],“context”:…
Hey , I tried submitting a bug report for this via just now, and the bug report form hangs on submission, it seems like it’s not working, here’s what I see after hitting submit:
Ah, my apologies that is happening! Are you able to try another browser or use a private browser at this time? This should immediately resolve this issue.
Hi ,
thanks for the info. The marketplace team kindly submitted the bug for me under the Case # 00276144. Just curious how’s the current state as I haven’t heard yet from the team. Normally someone would’ve created an issue for it.
So, I took a look into the source code to see what could cause the bug, so I compared the source code of the retainer boxes between 4.23 and 4.24 and found a change which might cause the bugs.
It’s really annoying and a real problem. I had the bug today, and totally freaking out searching why the progress bar is looking full all the time.
Is there any known workaround? @Epic: Fixed would be great!
The change of GetCachedGeometry() to GetTickSpaceGeometry() is not the actual issue, but is related to some refactoring of the retainer widgets that occurred in 2020
This has been tracked down to a commit on September 11, 2020 which also apparently affects the rendering of rich text widgets in a retainer box
I have locally reverted my UE5 Early Access source code that contains this change, and my progress bars work properly within a retainer box … obviously this is not a long term fix, and I don’t understand what else reverting this code might break, but it might be a work around for some until this issue can be addressed.
