Skip to main content
Intel

Intel claims Crimson Desert developers repeatedly ignore its outreach on Arc GPUs

Published by
SectorHQ Editorial
Intel claims Crimson Desert developers repeatedly ignore its outreach on Arc GPUs

Photo by Pauli Nie (unsplash.com/@paulify) on Unsplash

Intel says it flooded Crimson Desert’s studio with early Arc GPUs, drivers and engineering help, yet the developers never responded—Tomshardware reports the chipmaker reached out “many times” only to be ignored.

Key Facts

  • Key company: Intel

Intel’s developer relations team says it has been trying to get Crimson Desert, Pearl Abyss’s new fantasy‑RPG, to run on Intel Arc GPUs for years, but the studio never answered its outreach. In an email to Tom’s Hardware, Intel detailed a “multi‑year” effort that included shipping early‑access Arc silicon—spanning the Alchemist, Battlemage, Meteor Lake and Lunar Lake families—to Pearl Abyss, along with custom driver builds and direct engineering assistance (“We’re aware that Crimson Desert currently doesn’t launch on systems with Intel GPUs… Over the past several years, we’ve reached out to Pearl Abyss many times to help test, validate, and optimize support for Intel graphics, providing early hardware, drivers, and engineering resources…”). The chipmaker claims the studio never engaged, leaving Arc users with a launch‑day error that reads, “the graphics device is currently not supported,” and a recommendation to seek a refund.

The lack of Arc support is now visible to consumers on Steam, where more than 100 discussion‑board posts reference the same error message. While some users report the message on AMD or Nvidia cards, the consensus is that the game simply refuses to initialize on Intel hardware. Pearl Abyss’s official FAQ advises Arc owners to consult the platform’s return policy rather than promising a future patch, effectively confirming that no driver update or compatibility work is planned in the near term. Intel’s response pushes the responsibility back onto the developer, urging players to “reach out directly to Pearl Abyss” for details on the decision not to enable Intel support at launch.

From a market perspective, the dispute touches a tiny slice of the discrete GPU arena. According to the latest JPR AIB report cited by Intel, Arc GPUs command roughly 1 % of the global desktop graphics market, dwarfed by AMD and Nvidia’s combined dominance. Nonetheless, Intel’s graphics strategy extends beyond high‑end desktops; Arc GPUs are integrated into Meteor Lake, Lunar Lake and Panther Lake laptops, giving the company a broader installed base across consumer PCs. Intel argues that its “open tools, documentation, and direct engineering support” are designed to help any studio deliver a “best experience possible,” regardless of market share (“Our teams are deeply committed to helping all studios deliver the best experience possible…”).

The technical root of the incompatibility appears to be a missing validation path in the game’s rendering pipeline for Intel’s graphics architecture. Intel’s Alchemist and Battlemage GPUs use a distinct set of shader models and memory‑management heuristics compared to AMD’s RDNA or Nvidia’s Ampere families. Without coordinated testing, the game’s engine may fall back to a generic “unsupported device” branch, triggering the error seen by users. Pearl Abyss has not publicly disclosed whether internal resource constraints, licensing issues, or performance concerns drove the omission, leaving the community to speculate. The developer’s silence, despite Intel’s documented provision of early hardware and driver builds, fuels frustration among Arc owners who expected at least a baseline level of compatibility from a high‑profile launch title.

If Intel’s claim holds, the episode underscores a broader challenge for the company’s GPU push: convincing midsize studios to allocate engineering effort toward a platform that currently represents a marginal share of the market. Pearl Abyss, best known for the long‑running Black Desert Online, may prioritize platforms with larger user bases to meet launch deadlines. Conversely, Intel’s willingness to supply pre‑silicon and custom driver support suggests it is attempting to lower the barrier for developers, but the effectiveness of that approach hinges on reciprocal engagement. As of now, Arc users are left with a non‑functional launch experience for Crimson Desert, and the dispute remains unresolved pending any future dialogue between Intel and Pearl Abyss.

Sources

Primary source

Reporting based on verified sources and public filings. Sector HQ editorial standards require multi-source attribution.

More from SectorHQ:📊Intelligence📝Blog

🏢Companies in This Story

Related Stories