TextureRect Glitch

duane

I've just submitted an issue on this, but maybe you have some more insight on it. When I run this project, I get a nasty glitch in my background.

All it's doing is making a repeating background image and putting viewport/container on top. My current workaround (yuck) is

	back.stretch_mode = TextureRect.STRETCH_SCALE
	await RenderingServer.frame_post_draw
	back.stretch_mode = TextureRect.STRETCH_TILE

Edit: 8,630 open issues! Woot!

fire7side

Did you check your import settings? It has to be set to repeat or something.

duane

fire7side Did you check your import settings? It has to be set to repeat or something.

Thanks, I didn't think about that.

https://docs.godotengine.org/en/stable/tutorials/assets_pipeline/importing_images.html#import-options

In Godot 4.0, changing the texture filter and repeat mode is no longer done in the import options.

Instead, texture filter and repeat modes are changed in the CanvasItem properties in 2D (with a project setting acting as a default)

So I added this line to set the background TextureRect's texture_repeat mode, but it still produces the glitch on any setting (0-4). 🙁

	back.texture_repeat = CanvasItem.TEXTURE_REPEAT_ENABLED

Edit: Just for fun, I tried all the filter options, but they didn't change anything.

duane

Oh! This is strange. If I preload the texture, it works fine. (But only in the minimal project -- my real project still breaks.)

	back.texture = preload('res://art/back_tex.png')

I wonder if I should close that issue...

fire7side

I had that problem, but it was in a scene texture or material or something. I remember changing a repeat setting and it worked but I can't remember exactly where it was. I know it wasn't on a texture rectangle. It seems like 4 is unnecessarily complicated. Like you have to find a nearest box somewhere if you want to have pixelated sprites. It used to be a lot simpler. Maybe it's for speed or something. I can never remember where it was either. I have to search around every time.

duane

It turns out some change in 4.2 fixed it -- no repeat setting necessary. I should probably just start using 4.2 already.