TextureArray.map(MAX_SIZE_BUG)

PeterPM

Using the recommended basic shader, and a simple script, the bug is reproductible.

You cant go on a bigger canvas then (5747*5747 = 33028009) pixels.

Trying 5747*5748 = 33033756 or any other factors that get close to this value, you get a black screen.

extends ColorRect


# Declare member variables here. Examples:
# var a = 2
# var b = "text"
export var layer = 0
var map = TextureArray.new()
var temp_image = Image.new()
# Called when the node enters the scene tree for the first time.
func _ready():
	map.create(5747,5747,1,Image.FORMAT_RGBAF,0)#LIMIT OF WORKING
	#map.create(5747,5748,1,Image.FORMAT_RGBAF,0)#DOES NOT WORK
	#map.create(5747,5747,2,Image.FORMAT_RGBAF,0)#DOES NOT WORK
	temp_image.create(1000,1000,false,Image.FORMAT_RGBAF)
	temp_image.fill(Color.red)
	map.set_layer_data(temp_image,layer)
	material.set_shader_param("tex",map)
	pass # Replace with function body.

GDScript code

shader_type canvas_item;

uniform sampler2DArray tex;
uniform int index;

void fragment() {
    COLOR = texture(tex, vec3(UV.x, UV.y, float(index)));
}

Shader code

So, anyone can reproduce? (--- Debugging process started --- Godot Engine v3.4.3.stable.official.242c05d12 - https://godotengine.org OpenGL ES 3.0 Renderer: Intel(R) HD Graphics 4000 OpenGL ES Batching: ON)

Megalomaniak

Do note that GPUs have a max_texture_size, it might just be the limits of your specific GPU in play here.

PeterPM

Well, i posted the full debbug metadata.

It is wellcome to other people to test the limits i found, and report the same data.

So we can determine that thing.

If that is the case, at-least a recommended max size should be referenced.

I was basing myself on the 16384*16384 you get on the sidenote of the Image Ref: "Note: The maximum image size is 16384×16384 pixels due to graphics hardware limitations. Larger images may fail to import."

There is not such a thing on the TextureArray or the TextureLayered.

Having a per hardware limit to a texture size is an anoisance.

I belivie this is indeed a bug, but lets further investigate:> @Megalomaniak said:

Do note that GPUs have a max_texture_size, it might just be the limits of your specific GPU in play here.

PeterPM

HTML5 from the editor run. I indded need to add +2 instead of +1 of the aforementioned max possible value, but, when soo, i did get that error.

PeterPM

@PeterPM said: HTML5 from the editor run. I indded need to add +2 instead of +1 of the aforementioned max possible value, but, when soo, i did get that error.

Thats not the case, i continued to increase values, and the loading times ever increased, but in the majority of times, it froze, got a error of irresponsiveness, i clicked on wait, and it loaded

I stopped at map.create(8000,8000,1,Image.FORMAT_RGBAF,0).

the i jumped to 17000,17000 and get black screen, 15000 ,15000 and, 9000,9000 too.

then i got it working on 8200, then 8290, then it stoped working on 8200 but continue to work on 8000(by stoped working i mean it loads, but black screen, not the red rectangle)

So, its very intermitent, and the tab and browser and system seens to hang when finished loading, even more on the ones that does not show the red rectangle.

So, please, anyone, try to reproduce on the web and native run.

I need peer confirmation so i can open a issue.

Thanks for the collaboration.

PeterPM

I am using a chromium based browser, on firefox it hang and black screen on very small numbers.

duane

I could be misunderstanding you, but I'm not able to reproduce this issue on my system. I made a loop to try every size from 1000 to 15000 (which took about a half hour), and never got any black frames until 11870, after which it always failed, presumably because the texture was too big.

It might be a problem with your system.

PeterPM

11870, simply is your number.

By the docs, the maximmum suported by Texture is 16384.

PeterPM

And please, if you can send your code, and even expand it to compare it to a simple ImageTexture, to see if this is reproductible on Texture Class as well, or if is something of the TextureArray

cybereality

That's very large. I've had performance problems on WebGL even with a few 4K textures, so even assuming it's within the 16K OpenGL limit, it still won't run at 60 fps. Why do you need so many pixels?

PeterPM

I> @cybereality said:

That's very large. I've had performance problems on WebGL even with a few 4K textures, so even assuming it's within the 16K OpenGL limit, it still won't run at 60 fps. Why do you need so many pixels?

I am having really bad performance on WEBgl because TextureArray is only available on GLES3.

I want and will make another post, but maybe not, on tackling the perfomance of html5.

But i dont need that big of a texture per-se, i am justing exploring the limits, and having found this inconclusive hoof of maximum texture, is a thing to notice.

And even you said that 4k had problems.

So, i am simpling gonna ask, what is then the MINIMUM texture size that is SAFE?

cybereality

You want to stick with GLES 2.0, which is WebGL 1.0. WebGL 2.0 has recently got better support, but it's still pretty sketch. I think by the time Godot 4.1 is ready, WebGL 2.0 will be okay, but right now in Godot 3.x it's not really viable, so I would recommend not using it.

The size of the texture is whatever size you need for your game and nothing more. If your model looks good with 256x256, then use that. And texture arrays always seem to have sketch support in my experience. Unless you are doing something very advanced like real time MRI visualization, I don't think they are needed.

PeterPM

I preety much want to be able to do "real time MRI visualization" and other stuff.

There is something already done in godot on the field that you recomend?

PeterPM

But yeah, that seens to be the case. There is any hope on getting shader acess of TextureMesh on gles2

duane

@PeterPM said: And please, if you can send your code, and even expand it to compare it to a simple ImageTexture, to see if this is reproductible on Texture Class as well, or if is something of the TextureArray

Here's the project -- it's just your code in a loop. I'm not sure what you mean by comparing it.

cybereality

I have tested texture arrays. They do work, at least on desktop (I didn't try web). But you have to be realistic about what you can do in a web browser, especially since lots of people have crappy laptops. So I'm sure you can still do whatever it is, but be realistic about the quality you need.

PeterPM

Karroffel!