Purpose of engine.getCaps().maxTextureSize?

[mizuwu]

I might be missing something here, but I don't understand how even though a texture larger than engine.getCaps().maxTextureSize can still be mounted onto the mesh.

Whether it be by link or getting the path of the image relative to the source doc, the image can be loaded in most instances.

However, in another project that I'm doing, the restricted image size does not let me pass in larger images.

Would like to know what could've been the different about this one particular project vs the other ones that allow large textures?

I've heard that it might be because of the browser applying resizing functions to the images, but I want a more definite answer.

[Guest]

If you provide a texture bigger than device limit, we will scale it down for you

[mizuwu]

13 minutes ago, Deltakosh said:

If you provide a texture bigger than device limit, we will scale it down for you

That's interesting. Would there be cases where this fails? :0

[Guest]

Well I can think of a case where the browser cannot load the image but it has to be HUGE

[mizuwu]

12 minutes ago, Deltakosh said:

Well I can think of a case where the browser cannot load the image but it has to be HUGE

For example, my iPhone has a maxTextureSize of 4096. Although it works at 4096, the texture would fail at 4097 for my particular program.

I can't think of any reason why this program would fail when my prototypes allow larger textures.

[Guest]

Can you repro on the Playground? I would like to understand why the converter is not working in this case