← Back to AI Insights
Gemini Executive Synthesis

macOS launch crash, Metal shader version compatibility, legacy GPU support.

Technical Positioning
Broad macOS hardware compatibility, robust graphics API handling.
SaaS Insight & Market Implications
This issue details a critical launch crash on macOS, specifically affecting systems using OpenCore Legacy Patcher due to Metal shader version incompatibility. The application attempts to use Metal 3.2, which is unsupported by legacy GPUs limited to Metal 3.1. This directly impacts a segment of macOS users who extend the life of older hardware. The crash, stemming from the `wgpu/eframe` stack, suggests a fundamental graphics rendering dependency issue. While a workaround exists, the need for manual intervention creates significant user friction. Addressing this by dynamically selecting or falling back on Metal versions is crucial for broader macOS compatibility and user retention.
Proprietary Technical Taxonomy
macOS OpenCore Legacy Patcher Metal shader language version Metal 3.2 legacy GPU drivers Metal 3.1 shader compilation fails device is lost

Raw Developer Origin & Technical Request

Source Icon GitHub Issue Oct 10, 2026
Repo: storytold/craft-launcher
[macOS] Crashes on launch with OpenCore Legacy Patcher: "invalid value 'metal3.2'" (workaround inside)

**What happens**
On macOS, the launcher window flashes for a moment and then the app quits immediately.

**System**
- ArtCraft Launcher v0.1.0 (macos-universal.dmg)
- macOS Sequoia 15.7.4, installed with OpenCore Legacy Patcher
- Mac: MacBook Pro 15" mid-2015

**Error (running the binary from Terminal)**
```
ERROR wgpu_core::indirect_validation] indirect-validation error: ComputePipeline(Internal("Metal: error: invalid value 'metal3.2' in '-std=metal3.2' ... note: use 'metal3.1' for 'Metal 3.1' standard"))
ERROR eframe::native::run] Exiting because of error: WGPU error: Parent device is lost
ERROR artcraft_launcher] WGPU error: Parent device is lost
```

**Likely cause**
The app picks the Metal shader language version from the macOS version (15 → Metal 3.2). On OpenCore-patched Macs, the legacy GPU drivers only support up to Metal 3.1, so shader compilation fails and the device is lost. Choosing the version based on what the GPU/driver actually supports, or falling back when 3.2 fails, would fix it.

**Workaround**
Launching with the system version compatibility flag works:
```
SYSTEM_VERSION_COMPAT=1 /Applications/ArtCraft\ Launcher.app/Contents/MacOS/*
```
The individual Craft apps may hit the same issue, since they use the same wgpu/eframe stack.

Developer Debate & Comments

No active discussions extracted for this entry yet.

Adjacent Repository Pain Points

Other highly discussed features and pain points extracted from storytold/craft-launcher.

Extracted Positioning
Windows launch failure, graphics driver dependency.
Reliable application launch, broad hardware compatibility.
Top Replies
KartavyaY • Oct 10, 2026
Same issue for me too. The x64 launcher is not working Tried using the dmg for mac work without any issues.
SauloHS • Oct 10, 2026
It just randomly opened now, wtf?
SauloHS • Oct 10, 2026
Update: seems like it opens sometimes; samething happens with FilmCraft. Found it: Failed application name: artcraft-launcher.exe, version: 0.1.3.0, timestamp: 0x6aca57f4 Failed module name: igvk64...
Extracted Positioning
Windows 11 launch failure, graphics driver compatibility.
Reliable application launch, broad hardware compatibility.
Top Replies
Hachdog • Oct 11, 2026
Check what the Event Viewer says in the Windows Log/Application section after a failed launch. If you have an error related to igvk64.dll try updating your Intel Graphics Driver. Worked for me.
catmuf • Oct 11, 2026
> 1. Check what the Event Viewer says in the Windows Log/Application section after a failed launch. > If you have an error related to igvk64.dll try updating your Intel Graphics Driver. Worked for ...
Hachdog • Oct 11, 2026
Same issue with the .msi install version?
Extracted Positioning
Portable app installation, flexible deployment options.
User choice, simplified deployment for specific use cases (e.g., USB drives, restricted environments).
Extracted Positioning
Microsoft Store distribution.
Increased discoverability, simplified installation, trusted distribution channel.
Extracted Positioning
Linux app launching mechanism, AppImage integration.
Consistent cross-platform user experience, reliable application execution.

Frequently Asked Questions

Market intelligence mapped to macOS launch crash, Metal shader version compatibility, legacy GPU support..

What problem does macOS launch crash, Metal shader version compatibility, legacy GPU support. solve?
Based on our AI analysis of the original developer request, its primary technical positioning is: Broad macOS hardware compatibility, robust graphics API handling.
How is the developer community reacting to macOS launch crash, Metal shader version compatibility, legacy GPU support.?
Yes, we have tracked 3 direct responses and active debates regarding this specific topic originating from GitHub Issue.
Which technical concepts are associated with macOS launch crash, Metal shader version compatibility, legacy GPU support.?
Our proprietary extraction maps macOS launch crash, Metal shader version compatibility, legacy GPU support. to adjacent architectural concepts including macOS, OpenCore Legacy Patcher, Metal shader language version, Metal 3.2.

Engagement Signals

3
Replies
open
Issue Status

Cross-Market Term Frequency

Quantifies the cross-market adoption of foundational terms like macOS and OpenCore Legacy Patcher by tracking occurrence frequency across active SaaS architectures and enterprise developer debates.