UMG images do not inherit texture filter setting

Images in UMG do not correctly inherit the texture’s filter setting. The only way around this is to make a material, and then choose the material in the UMG Image component instead of choosing the texture directly.

Here is what choosing the texture directly looks like

http://puu.sh/m7iFS/c5d323d64a.png

Here is what it looks like if I instead make a material and choose that

http://puu.sh/m7iIG/0bc28dec5d.png

This bug has existed for as long as I know, 4.8 4.9 and 4.10 and probably earlier.

Here are my texture settings, and it looks sharp in the texture preview.

http://puu.sh/m7iMZ/e36cf0b860.png

Hello,

It sounds like you have been able to reproduce this in a clean project, is that correct? If so, do you have steps that we can use to reproduce this issue reliably on our end? Is this only with the particular texture that you have shown in your image, or does this occur with any texture?

Thank you

Yes I can reproduce this in a clean project.

  1. Make a UMG Widget with an image in it
  2. Import a texture and set it’s filtering to Nearest
  3. Set the Image in the UMG widget to be that texture

This happens to all images all the time, it has never worked.

I’ve attempted to reproduce this using a few different textures, but have been unable to do so. Could you send me this “Score” texture that you are using so I can import it into my project and see if I can get the same results? Thank you.

Just to be clear this is for low resolution pixel art files. If you’re attempting to do this with something similar to a photograph the difference might not be enough for you to tell.

Try both of these files.
http://puu.sh/m7l3w/c92826ca56.png
http://puu.sh/m7l4Y/e42508bbe2.png

To make it easier to tell you may have to zoom in on the image, as these files are low resolution.

Here is another example, the first one is using the texture directly and the lower one is using a material. Only the lower one is properly inheriting the Nearest texture filtering.

http://puu.sh/m7kXO/7c41c64940.png

Hello,

I have been able to reproduce your issue, and have entered a bug report (UE-24798). Thank you for your report. I will provide an update on this issue when it becomes available.

Have a great day,

Sean Flint