Thanks for the report! Yes, I was thinking about adding a new method to Texture. But I need to think more about it.

I wish we can get this method in Texture class or at least as an argument in WrapD3D11 method.

Hi Vladimir, resurrecting this... :)

Sorry for the late reply, this is more complex that adding a float parameter to the texture class. Because it changes de API that our clients need to implement for custom render devices. In modern APIs, MipMapLodBias is not isolated and cannot be set to the GPU. Instead of that, this value is part of a bigger object, SamplerState for example in D3D11. This objects needs to be precreated. This can be done, but we would like to avoid it because it is extra work that need to be done by our clients, we want to avoid increasing the complexity of implementing a custom renderer. Anyway, we are close to 3.1 and this is a good moment to take a decision about this.

I have playing with our examples, and I am observing that a MipMapLodBias of -0.75 works almost perfect and very close to BitmapScalingMode set to HighQuality in WPF.
So, I propose hardcoding this value or a bit better, just exposing that number in RenderDevice, with the rest of configuration functions like SetOffscreenWidth, etc...

This way, instead of a value per texture, you will have the same value for all textures. This is probably what you would end up doing.

What do you think?

Hi Jesús,
I'm sorry for the very late reply. I've totally forgotten about the email and this ticket as in early May I was totally overwhelmed with 1.0 release and heavy DDoS. attacks on our servers.

Global MipMapLodBias sounds like a good solution for us. We're using very few raster images for the UI itsel—mostly there are item icons, and these are rarely animated so negative LOD bias should not cause any noticeable artifacts.

Regards!

3.1 was released with an internal bias of -0.75, please let us know if it works fine in your game. Thanks!

Hello!
Sorry for the late reply. We've upgraded to 3.2 a few months ago and nobody complained about the icon bluriness so I guess it's working great!
I wish you can provide this setting in RenderDevice as you've proposed in the message above. This way we can not only determine the best setting (e.g. I would like to have no bias when rendering in 4K) but also ensure that the mip map bias works as expected.

Regards!