Can a texture default filtering option parameter be added?

[JohnLKkk]

I noticed that after many glTF models are converted to j3o, they seem to all use nearest filtering, which looks terrible visually (severe flickering when the camera moves...) and is very costly for texture bandwidth. Could a parameter be added during conversion for setting textureMin/MagFilter?

[pspeed42]

That's because JME does that. JmeConvert is just calling JME code.

It would be a really simple groovy script that you could write to add to the JmeConvert command line to set all filtering. Probably just 4-5 lines of groovy code.

[oxplay2]

Its not really JMEC issue.

I think the issue wasnt about Texture Filtering param, but about mipmaps where Trilinear/Bilinear require mipmaps that are most probably just not generated.

Reason: Texture.java
texture.setMinFilter() have glued code:

        if (minificationFilter.usesMipMapLevels() && image != null && !image.isGeneratedMipmapsRequired() && !image.hasMipmaps()) {
            image.setNeedGeneratedMipmaps();
        }

But its executed 2 times for GLTFLoader, first time before setting proper Filterings, and second time when set proper Filterings via this method.

While JME .j3o loader is using this only first time, because second time it setup filterings by texture.read() instead texture.setMinFilter();

so for texture.read() just need add glued code, or call texture.setMinFilter() second time.