[AIR 51.2.0.2] ANGLE: Meshes with repeatable texture (POT) are not rendered with Starling Framework (OpenGL context 3D)

[Adolio]

Context

This is an early report after my initial testing of AIR 51.2.0.2. The only issue I found so far is a rendering issue with all meshes where repeatable textures are applied on them. They are just not rendered at all.

How to reproduce

I don't have a snippet but it's probably relatively easy to reproduce. By using the latest Starling Framework, all meshes with repeatable textures (POT) aren't rendered.

Update 1: This seems to occur only with a large number of textures loaded via the Starling's AssetManager. Update 2: The problem disappear when the advanced-telemetry option is active.

Configuration

I'm using the libEGL.dll & libGLESv2.dll directly from Google Chrome under Windows 10 or 11. The context 3D is OpenGL (Enhanced) and I'm running things through the adl64.exe obviously with the useAngle flag on.

[Adolio]

@ajwfrost FYI this issue is still present in AIR SDK 51.2.1.1.

[Adolio]

I managed to narrow down a bit the root cause and it seems that it only occurs for POT textures registered and gathered through the Starling AssetManager. The way I enqueue POT textures is as follow:

private function enqueuePotTextures4x():void
{
	_assetsMgr.textureOptions.scale = 4.0;
	_assetsMgr.textureOptions.forcePotTexture = true;
	_assetsMgr.enqueue(EmbeddedRepeatableTextures4x); // this class contains the textures declared as [Embed] assets
	_assetsMgr.textureOptions.forcePotTexture = false;
}

Everything works fine with embedded textures directly instantiated with Texture.fromEmbeddedAsset(MyPotTexture, false, false, 1.0, "bgra", true);

I will investigate further to see if Starling is doing a special treatment in this case, maybe related to texture format (FYI @PrimaryFeather, maybe you know what's happening here).

[Adolio]

@ajwfrost

Quick update: the issue disappears when using the advanced-telemetry compiler option...

I also tried to replicate the issue with a minimal sample project but so far I couldn't, this might (or not) be related to the assets or the volume of assets I'm uploading to the GPU...

[Adolio]

@ajwfrost Could the "AIR Diagnostics" feature be used to identify the root cause of this issue? If not, can you guide me a bit to provide you further meaningful information?

[Adolio]

@ajwfrost FYI this issue is still present in AIR SDK 51.2.1.5.