Corrupted text rendering when using DirectX 11 (dx11) and Vulkan

[ruizlenato]

I found a bug where the text gets completely corrupted (rendering as thick black blocks) when using either the DirectX 11 or Vulkan backend.

[kolkov]

@ruizlenato Thank you for the report!

We tested with all three backends (Vulkan, DX12, GLES) on Intel Iris Xe (Windows 10) and cannot reproduce — text renders correctly everywhere.

A couple of questions to help us debug:

1. Environment info:

• What Windows version?
• AMD GPU driver version? (Device Manager → Display Adapters → Properties → Driver tab)
• Go version? (go version)
• Is this the latest main or a specific release tag?

2. About the backends:

• We don't have a dx11 backend. When you set GOGPU_GRAPHICS_API=dx11, it falls back to the default (Vulkan). So the window in your screenshot is actually rendering with Vulkan.
• The GLES and DX12 crashes (0xc000013a) — did these crash immediately on startup, or after the window appeared?

3. About the text corruption:
Looking at your screenshot, I notice the title, section headers, checkboxes, and radio button labels all render correctly — only the ListView items show black blocks. This is interesting because ListView items go through a different rendering path (RepaintBoundary with scene.Scene display list caching).

4. Full terminal output:
Please share the complete terminal output when running with Vulkan (the default):

go run . 2>&1

5. Vulkan validation (very helpful if you have Vulkan SDK installed):
Install the Vulkan SDK if you don't have it, then run:

$env:VK_INSTANCE_LAYERS="VK_LAYER_KHRONOS_validation"; go run . 2>&1

This enables GPU-side validation. Any errors in the output would pinpoint the exact issue — AMD drivers often have Vulkan spec deviations that Intel silently tolerates.

[ruizlenato]

@ruizlenato Thank you for the report!

We tested with all three backends (Vulkan, DX12, GLES) on Intel Iris Xe (Windows 10) and cannot reproduce — text renders correctly everywhere.

A couple of questions to help us debug:

1. Environment info:

* What Windows version?

* AMD GPU driver version? (Device Manager → Display Adapters → Properties → Driver tab)

* Go version? (`go version`)

* Is this the latest `main` or a specific release tag?

2. About the backends:

* We don't have a `dx11` backend. When you set `GOGPU_GRAPHICS_API=dx11`, it falls back to the default (Vulkan). So the window in your screenshot is actually rendering with Vulkan.

* The GLES and DX12 crashes (`0xc000013a`) — did these crash immediately on startup, or after the window appeared?

3. About the text corruption: Looking at your screenshot, I notice the title, section headers, checkboxes, and radio button labels all render correctly — only the ListView items show black blocks. This is interesting because ListView items go through a different rendering path (RepaintBoundary with scene.Scene display list caching).

4. Full terminal output: Please share the complete terminal output when running with Vulkan (the default):

go run . 2>&1

5. Vulkan validation (very helpful if you have Vulkan SDK installed): Install the Vulkan SDK if you don't have it, then run:

$env:VK_INSTANCE_LAYERS="VK_LAYER_KHRONOS_validation"; go run . 2>&1

This enables GPU-side validation. Any errors in the output would pinpoint the exact issue — AMD drivers often have Vulkan spec deviations that Intel silently tolerates.

1. Environment info:
What Windows version? Windows 11 25H2 (26200.8328)
AMD GPU driver version? 31.0.21923.11000
Go version?go version go1.26.2 windows/amd64
Is this the latest main or a specific release tag? Latest Main

3. About the text corruption:

2. About the backends:
The GLES and DX12 errors (0xc000013a), which I'm not sure if they are actually errors, only occurred after closing the application, when I pressed Ctrl+C in the terminal, but I noticed that the application becomes extremely slow in DX12.

4. Full terminal output:

$env:GOGPU_GRAPHICS_API="vulkan"; go run . 2>&1
2026/05/06 12:25:17 INFO adapter selected name="AMD Radeon(TM) RX Vega 11 Graphics" type=IntegratedGPU

5. Vulkan validation (very helpful if you have Vulkan SDK installed):

[beanaroo]

I'm not sure if this is related. I've only just discovered the project and when trying out one of the example apps I see similar rendering issues on the ListView.

Go 1.26.2 on MacOS 26.4.1

2026/05/09 10:19:31 INFO adapter selected name="Apple M5 Pro" type=DiscreteGPU

[kolkov]

We've identified and fixed the root cause in v0.1.19 (just released).

The issue was double rendering of ListView items — each item was rendered into both the root texture (inline) and its own boundary texture (overlay blit). The alpha-blended overlap produced the thick black blocks you're seeing.

Fix: Per-boundary GPU textures with DrawChild skip pattern — child boundaries are now SKIPPED during parent recording and composed as separate textures. No more double rendering.

v0.1.19 also includes:

• 0% GPU idle (frame skip when nothing dirty)
• Offscreen boundary culling
• 34 integration tests for the render loop pipeline

Could you please test with v0.1.19?

go get github.com/gogpu/ui@v0.1.19
go run ./examples/hello/

@beanaroo — this should fix your issue on Apple M5 Pro as well. Please try the same update.