← Back to AI Insights
Gemini Executive Synthesis

Game launcher and initial UI rendering on Windows with AMD/Intel integrated graphics, specifically a completely black window preventing interaction, introduced in Alpha 3.

ROIPAD RESEARCH · PUBLIC SOURCES

Discussion evidence and market context

Snapshot 2026-11-03 10:15:04 UTC · Sources and methodology

CALCULATED FROM STORED SOURCE RECORDS

Feedback evidence available for this record

5 distinct substantive comments in the bounded stored sample.

Dated comments span 2026-10-25 02:32:54 to 2026-10-25 20:15:51. Sample: up to 180 stored records, deduplicated and capped at 60 substantive comments. Launch discussion and issue-tracker samples are not representative customer surveys.

What the discussion sample says

5 distinct, substantive comments in the stored sample. Below the configured minimum of 20 comments; no sentiment inference published.

Technical Positioning
Reliable and consistent UI rendering across diverse GPU hardware (NVIDIA, AMD, Intel) and operating systems. The goal is a functional and visually correct initial user experience.
SaaS Insight & Market Implications
This issue reports a critical 'black window' bug affecting the game launcher on Windows with AMD and Intel integrated graphics, specifically introduced in Alpha 3. This prevents any user interaction or configuration, rendering the product unusable for a significant segment of the user base. The problem is traced to three new features in Alpha 3: a 'render-target path (feedback loops),' 'graphics pipeline libraries,' and `maintenance5`. The inability to reproduce on NVIDIA or Mesa's software Vulkan driver strongly suggests a specific incompatibility with AMD and Intel Windows drivers. This highlights a severe cross-platform rendering challenge and the fragility of relying on advanced Vulkan features without extensive driver compatibility testing. For a B2B SaaS product, such a foundational UI failure on common hardware is a major blocker for adoption and necessitates immediate, targeted driver-specific workarounds or architectural adjustments.
Proprietary Technical Taxonomy
Black window AMD or Intel graphics Alpha 3 initial configuration launcher savagewind.exe Savage Wind Configuration.exe AMD Radeon RX 9070 XT Intel Celeron 6305

Raw Developer Origin & Technical Request

Source Icon GitHub Issue Oct 25, 2026
Repo: Revivedx/SavageWindRecomp
Black window on Windows with AMD or Intel graphics since Alpha 3 (hotfix 0.3.1 out, logs needed)

### Savage Wind version

0.3.0 alpha

### Game version

1.9.0

### Your PC

windows 11 9070xt i7 12h

### Where in the game

Before entering the game — initial configuration launcher, before selecting any game files.

### What happened, and how to make it happen again

**Description**

SavageWind 0.3.0-alpha.3 opens a completely black window on my AMD Radeon RX 9070 XT. This happens with both `savagewind.exe` and `Savage Wind Configuration.exe`, before selecting or loading any game files.

The previous version, 0.2.0-alpha.2, displays the configuration launcher correctly on the exact same PC.

**Steps to reproduce**

1. Extract SavageWind 0.3.0-alpha.3 for Windows into a separate folder.
2. Launch `Savage Wind Configuration.exe`.
3. The window opens but remains completely black. No menus or configuration options are visible.

**Troubleshooting performed**

- Vulkan successfully detects and selects the AMD Radeon RX 9070 XT.
- Tested FIFO presentation mode — no improvement.
- Tested disabling the independent Vulkan presentation thread — no improvement.
- Tested different display refresh settings — no improvement.
- Used `SAVAGEWIND_LAUNCHER_SHOT=20` to capture the launcher internally.
- The resulting `launcher-test.png` was successfully generated at 1280×720, but the image itself is also completely black.
- Alpha 2 displays the launcher normally on the same hardware.

**System information**

- CPU: Intel Core i7-12700
- GPU: AMD Radeon RX 9070 XT
- Secondary GPU: Intel UHD Gra...

Developer Debate & Comments

BluetufieBugado • Oct 25, 2026
The same thing happened to me when I downloaded the new version. Since this didn't occur in the old version, I think it's worth testing it here to see what happens. If it works with the previous version, I'll come back to share the update. And in my case, it was with an Intel Celeron 6305, using Vulkan 1.4.323.
giting100 • Oct 25, 2026
try reset shader cache on amd adrenaline. it work at rog ally z1 extreme
Revivedx • Oct 25, 2026
Thanks for the very complete report, and to everyone confirming! We can't reproduce this on NVIDIA (also not with the Vulkan validation layer, which reports nothing), so it looks specific to the AMD and Intel drivers on Windows. Alpha 3 turned on three things that Alpha 2 didn't use on these GPUs: a new render-target path (feedback loops through a special image layout), graphics pipeline libraries, and `maintenance5`. Could you try these, one at a time, and tell us which one (if any) brings the launcher back? Open a command prompt in the Savage Wind folder, run the `set` line, then start `savagewind.exe` from that same window (close it between tries; a new window starts clean): 1. `set SAVAGEWIND_VK_NO_FEEDBACK_LOOP=1` 2. `set SAVAGEWIND_VK_NO_GPL=1` 3. Both at once. Also worth a try, as @giting100 suggested for the ROG Ally: AMD Software (Adrenalin) > Gaming > Graphics > Reset Shader Cache, then start Savage Wind again. Please attach the `savagewind.log` from the attempt that works ...
BluetufieBugado • Oct 25, 2026
> Thanks for the very complete report, and to everyone confirming! We can't reproduce this on NVIDIA (also not with the Vulkan validation layer, which reports nothing), so it looks specific to the AMD and Intel drivers on Windows. Alpha 3 turned on three things that Alpha 2 didn't use on these GPUs: a new render-target path (feedback loops through a special image layout), graphics pipeline libraries, and `maintenance5`. > > Could you try these, one at a time, and tell us which one (if any) brings the launcher back? Open a command prompt in the Savage Wind folder, run the `set` line, then start `savagewind.exe` from that same window (close it between tries; a new window starts clean): > > 1. `set SAVAGEWIND_VK_NO_FEEDBACK_LOOP=1` > 2. `set SAVAGEWIND_VK_NO_GPL=1` > 3. Both at once. > > Also worth a try, as [@giting100](https://github.com/giting100) suggested for the ROG Ally: AMD Software (Adrenalin) > Gaming > Graphics > Reset Shader Cache, then start Savage Wind again. Please attac...
Revivedx • Oct 25, 2026
Thanks for testing, @BluetufieBugado. A freeze and screen flicker with the first one is useful: it means your driver behaves differently on that path. An update from our side: we still can't reproduce the black launcher. It draws fine on NVIDIA and on Mesa's software Vulkan driver (lavapipe), with every combination of those settings, including the exact Alpha 3 build and the same "feedback loop layout" path the RX 9070 XT log shows. So it really looks like something the AMD and Intel Windows drivers do differently, and we need a bit more from your machines to find it: 1. **@BluetufieBugado:** please attach the `savagewind.log` from the `SAVAGEWIND_VK_NO_GPL=1` try (the one that showed the "Vulkan 1.3" message), and the one from a normal start. The log is in the Savage Wind folder, or in `Documents\...\Savage Wind` if you chose a data folder there. The message is generic, but the line above it in the log says which Vulkan call failed. 2. **@gabrielsem16-bot (RX 9070 XT):** could you t...

Adjacent Repository Pain Points

Other highly discussed features and pain points extracted from Revivedx/SavageWindRecomp.

Extracted Positioning
Game UI rendering and performance on Linux (Cachy OS) with AMD graphics, specifically a broken UI (black background in menus) and general performance on lower-end AMD hardware.
High-fidelity, performant game execution with accurate UI rendering across Windows and Linux, including AMD GPUs. The goal is a visually correct and playable experience.
Top Replies
NOOBTW00 • Oct 25, 2026
This ss is on windowed but It is happening on FS too or i wouldn't even report it lol
Revivedx • Oct 25, 2026
Hi @NOOBTW00 Would you mind Sharing your log for me to look further into?
NOOBTW00 • Oct 25, 2026
[savagewind.log](https://github.com/user-attachments/files/33919102/savagewind.log) here It is, sorry the wait and keep up with this amazing work!
Extracted Positioning
Game rendering, specifically texture handling on AMD RX 7600 GPUs, manifesting as visual corruption (pink/violet textures) in random areas.
High-fidelity, artifact-free game rendering across various hardware, including modern AMD GPUs. The goal is accurate texture display and visual integrity.
Top Replies
jeffin88 • Oct 24, 2026
the streamable video expires in 2 days
Revivedx • Oct 24, 2026
Thanks for the video! It shows magenta, blocky patches on the mossy tops of the stone ruins, the "error" colour of Savage Wind's texture decoder. We don't see it on NVIDIA or on the Steam Deck (AMD...
jeffin88 • Oct 24, 2026
> 5\. Thanks for the video! It shows magenta, blocky patches on the mossy tops of the stone ruins, the "error" colour of Savage Wind's texture decoder. We don't see it on NVIDIA or on the Steam Dec...
Extracted Positioning
Game configuration and file processing, specifically disk space management, where the configuration process fails due to a reported 'lack of disk space' despite sufficient storage.
Reliable and efficient game configuration, including accurate disk space checks. The goal is a smooth setup process without false-positive resource errors.
Top Replies
StonedEdge • Oct 25, 2026
What game version are you using? Users are reporting the compilation step fails on update 1.9.0 in various threads.
Lucone81 • Oct 25, 2026
version 1.8.2, but i was trying to find the 1.9.0 update, without success. But if it faild even with 1.9.0 it is useless to search for it, isn't it?
Lucone81 • Oct 25, 2026
I managed to get it work. I've created a new folder called "Zelda", inside it i put 2 new folders "exefs" and "romfs" where i've extracted the game's files. Then i've started the configuration and ...
Extracted Positioning
Game rendering, specifically depth buffer precision and Z-fighting artifacts on distant surfaces, exacerbated by fast camera movement.
High-fidelity, artifact-free game rendering, maintaining visual integrity even under dynamic camera conditions. The goal is accurate depth perception and rendering.
Top Replies
fgabe • Oct 25, 2026
Hey ! Did you fully pre-compile shaders before launching the new release ? If yes, please attach below your savagewind.log If not on the Alpha 3, please try it.
Sandbowl • Oct 25, 2026
Hello. Yes this was running with pre-compiled shaders. Here's the log file (I made a typo when renaming the directory, it is alpha 3 😅): [savagewind.log](https://github.com/user-attachments/files/...
Revivedx • Oct 25, 2026
Thanks for the video and the log, @Sandbowl. We tried to reproduce this on the current test build (game 1.9.0, Shadow resolution Extreme), turning the camera fast on the Great Plateau toward the di...
Extracted Positioning
Game code static recompilation process, specifically the failure of the game code to build despite sufficient disk space.
Reliable static recompilation of Switch game code for Windows/Linux, enabling users to run the game on PC. The goal is a robust build process.

Frequently Asked Questions

Market intelligence mapped to Game launcher and initial UI rendering on Windows with AMD/Intel integrated graphics, specifically a completely black window preventing interaction, introduced in Alpha 3..

What is the technical positioning of Game launcher and initial UI rendering on Windows with AMD/Intel integrated graphics, specifically a completely black window preventing interaction, introduced in Alpha 3.?
Based on our AI analysis of the original developer request, its primary technical positioning is: Reliable and consistent UI rendering across diverse GPU hardware (NVIDIA, AMD, Intel) and operating systems. The goal is a functional and visually correct initial user experience.
How is the developer community reacting to Game launcher and initial UI rendering on Windows with AMD/Intel integrated graphics, specifically a completely black window preventing interaction, introduced in Alpha 3.?
Yes, we have tracked 14 direct responses and active debates regarding this specific topic originating from GitHub Issue.
What architecture is tied to Game launcher and initial UI rendering on Windows with AMD/Intel integrated graphics, specifically a completely black window preventing interaction, introduced in Alpha 3.?
Our proprietary extraction maps Game launcher and initial UI rendering on Windows with AMD/Intel integrated graphics, specifically a completely black window preventing interaction, introduced in Alpha 3. to adjacent architectural concepts including Black window, AMD or Intel graphics, Alpha 3, initial configuration launcher.

Engagement Signals

14
Replies
open
Issue Status

Cross-Market Term Frequency

Counts stored text matches for foundational terms like NVIDIA and Alpha 3 in analysed public discussions. These counts do not measure adoption.

Stored text matches, not adoption or market-share measurements.

  • NVIDIA: 22 records
  • Alpha 3: 2 records
  • SAVAGEWIND_VK_NO_FEEDBACK_LOOP=1: 2 records
  • Black window: 1 records
  • AMD or Intel graphics: 1 records
  • initial configuration launcher: 1 records
  • savagewind.exe: 1 records
  • Savage Wind Configuration.exe: 1 records
  • AMD Radeon RX 9070 XT: 1 records
  • Intel Celeron 6305: 1 records
  • Vulkan 1.4.323: 1 records
  • FIFO presentation mode: 1 records
  • independent Vulkan presentation thread: 1 records
  • display refresh settings: 1 records
  • SAVAGEWIND_LAUNCHER_SHOT=20: 1 records
  • launcher-test.png: 1 records
  • shader cache: 1 records
  • AMD Software (Adrenalin): 1 records
  • render-target path (feedback loops through a special image layout): 1 records
  • graphics pipeline libraries: 1 records
  • maintenance5: 1 records
  • SAVAGEWIND_VK_NO_GPL=1: 1 records
  • Vulkan validation layer: 1 records
  • Mesa's software Vulkan driver (lavapipe): 1 records
  • feedback loop layout: 1 records