So we’re trying to create a visual effect using the new retainer boxes, and it works great. However when you use retainer boxes with UMG elements for 3D world widgets, the colours get oddly washed out. They seem to work fine when added to viewport, but acting strangely in world.
We’ve broken it down step by step to make sure we weren’t doing anything odd, and the ONLY difference is the use of the retainer box. Attached is an image explaining the situation, we’ve used as simple material as possible, with as simple a UMG as possible. The image shows a standard 3D widget on the left, and a 3D widget using retainer box on the right.
As stated before, retainer boxes on viewport widgets work fine. It may not be completely clear from the image, but all elements of the UMG get washed out, not just images, but text, borders etc.
I should also add that this isn’t an issue with post process settings like eye adaptation, we have all this stuff turned off.
Thanks in advance!!
Sorry for the delay. I did some digging, and it looks like this is a known issue with retainer boxes not playing nicely with translucent materials. (UE-33285) We’re planning to investigate a fix for 4.14, I’ll post back here if I hear any new info.
In the mean time, the report notes that additive and masked blend modes work as expected. You may be able to use that as a workaround.
Thanks for your reply. It seems to happen to us no matter the blend mode of the effect material. When we set it to Opaque, we get the same issue, and if we set it to Additive, the material doesn’t show at all, just a black box. I should also point out that after further fiddling, we found that it still has the same issue even when we have no effect material plugged in. The texture still looks washed out :(.
Another issue we have found, is that certain blocks of text (not all of them) disappear when using a retainer box, is this a known issue?
Sorry for dropping all this stuff like this, if you want me to make a more detailed post I’ll be more than happy to do so
Sorry to hear that you’re running into a different problem. I was able to reproduce the issue, and filed a bug report to be investigated (UE-35531). I’ll update you here as soon as I hear any updates.