You discovered a bug in the engine, and you are sure that it is not a problem of your code? Just post it in here. Please read the bug posting guidelines first.
Probably because the code in the D3D8/9 drivers for filtering configuration is wrong. Notice how the following code doesn't even look at the filtering values other than anisotropic...
I think the two fragments from vitek are the same besides the Caps check for the trilinear support. So there will be no more filter support than before!? So to say: It was correct and should have worked in all Irrlicht versions AFAIK.
Haha, that's hilarious. I didn't even read the code I had in my copy of the video driver. I just blindly copy/pasted it. I remember there being an issue with these flags before 1.3, but never checked to see if it was fixed. Apparently now it is exactly the same as what I have, just formatted differently.
I never really thought about it, but looking at the code it seems filtering is set for all layers of a material. It would be nice to have per layer filtering. I'm sure it would be useful for something (although nothing springs to mind).
In my current project I'm using a character that's from the 8-bit generation so he should look like pixellated. It's no big deal for me to stick with OpenGL, but I'm not imagining things.
Per-layer setting will come soon. If I can keep the API compatible with the old one (i.e. only extending the old one) it will be in the next version, otherwise it will be in the next API-breaking one.
But as said in the previous posts the filtering should work for both accelerated drivers!