Also I cannot see any difference between "HighQuality" and "Linear" settings. But it's very noticeable in WPF. Are you sure using trilinear texture quality when "HighQuality" selected? I'm talking about images loaded by NoesisGUI (defined by path in ResourceDictionary).

The difference between HighQuality and Linear only makes sense if you are using mipmaps. By default Unity doesn't generate mipmaps for 2D Textures. We also decided to do that in NoesisGUI v1.2, mipmaps are not generated.

Do you think you could get better quality with them?

Yes, in some cases trilinear texture filtering give us much better quality with scale animations. It looks much better in WPF with "HighQuality" setting.

But we need to have a control over it, as not all the UI textures need to have mipmaps. Maybe a good solution will be taking mipmaps property from Unity TextureImporter settings for an UI texture when NoesisGUI build the streaming assets.

In the next major (1.3) version we are working on, we plan to use the textures generated by Unity avoiding our preprocessing step. That way, you can activate mipmaps if you wish.

So, when adding mipmaps you are not observing excessive blurriness? Would be nice if you could attach the texture you are testing.

Great to know about this change with v1.3. It's definitely fixes this issue, but also makes RenderOptions.BitmapScalingMode option useless (and deceptive - it would good to mention about this with a warning during NoesisGUI assets build phase).

I'm not in the office at the moment so I couldn't attach images right now. But yes, it's definitely looks better when slow scale animation playing and a little bit blurry when static. It seems to be improved when setting "sharper" mipmap bias for Unity texture instance (if the texture assigned manually to an ImageBrush of course).

Also I've noticed that even the VoidExpanse game logo image rendered in Unity looks not as smooth and good as in WPF project with "HighQuality" setting applied - it has noticeable sharp edges in Unity (looks more like nearest neighbor filtering instead of bilinear), especially if the image rendered in the lower resolution than its native size.

Could you attach the XAML + images with the voidexpanse logo to exactly compare WPF vs Noesis?

This is something I will carefully study.

Besides, the original problem of the ticket is a different think. Sergio, did you have time to investigate it?

It seems WPF "HighQuality" uses trilinear filtering, so that's why I've noticed it looks different in WPF.
Bilinear filtering looks no good when image downscaled (and when scale transform is animated it looks even worse, more like "nearest neighbor"). I've attached two images to compare (made with WPF application, VS2013 project also attached). Of course trilinear filtering looks little bit blurry when downscaled, but for my opinion it's better than jagged lines.

I cannot detect any visual difference between Unity and WPF with "Linear" quality.