Friday, March 20th 2026

Intel Offered Hardware Optimization Help to Crimson Desert Developer for Years, Company Says

The controversy where open-world fantasy game "Crimson Desert" isn't supported on Intel Arc GPUs to the point of the game refusing to even launch on systems with Arc GPUs, drew its first response from Intel. Gamers with Intel Arc graphics cards got a rude shock earlier this week, as the game flat-out refused to start on their systems, with a dialog box simply saying "the graphics device is currently not supported." In its FAQ, "Crimson Desert" developer Pearl Abyss said that the game doesn't currently support Arc GPUs, and gamers who bought the game expecting it should seek refunds.

In its statement to the press, Intel says that it reached out to Pearl Abyss over the past several years to help optimize the game for its hardware. "Crimson Desert" has been in development for over 6 years prior to its launch earlier this week. "We've reached out to Pearl Abyss many time to help test, validate, and optimize support for Intel graphics, providing early hardware, drivers, and engineering resources across multiple generations, including "Alchemist," "Battlemage," "Meteor Lake" (Xe-LPG), and "Lunar Lake" (Xe2-LPG)," the statement goes. The company says that it "remains ready to assist Pearl Abyss."
The complete statement by Intel follows.

"We're aware that Crimson Desert currently doesn't launch on systems with Intel GPUs and we're hugely disappointed that players using Intel graphics hardware can't jump into the world of Pywel at launch.

Getting games running smoothly is always a partnership between developers and hardware makers. 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 across multiple generations, including Alchemist, Battlemage, Meteor Lake, and Lunar Lake.

Our teams are deeply committed to helping all studios deliver the best experience possible, providing open tools, documentation, and direct engineering support to make sure their games run well for everyone, including the tens of millions of players using Intel GPUs. We remain ready to assist Pearl Abyss however we can.

For details on the choice not to enable Intel support at launch, please reach out directly to Pearl Abyss."
Add your own comment

71 Comments on Intel Offered Hardware Optimization Help to Crimson Desert Developer for Years, Company Says

#1
Ripcord
The problem isn't that they chose not to support Intel Arc its that they are actively blocking it. the game isn't supported on Linux either but you can run it on that OS if you want.
Posted on Reply
#2
DeltaHawk001
This is BS. The game should have worked at launch. Intel gamers should save the money.
Posted on Reply
#3
Youseethis
Many eyes are turning towards denuvo as the culprit.

In any case, this goes against the concept of direct3d.
Posted on Reply
#4
FatherOBlivion
YouseethisMany eyes are turning towards denuvo as the culprit.

In any case, this goes against the concept of direct3d.
Why Denuvo? Because of the general hate toward the anti-piracy company, or something more?
Posted on Reply
#5
mechtech
Does it work on Intel integrated?? ;)
Posted on Reply
#6
zenlessyank
Is someone reaching out to these guys like they said? Maybe get it from the horses mouth instead of the horses ass?
Posted on Reply
#7
Dr. Dro
I am so incredibly frustrated with Asian game developers and their culture of treating the PC like a complete afterthought. It's never been easier to get a game on PC than it is today, yet they consistently screw up and continue to ship slop, just on the top of my head:

Crimson Desert explicitly blocking Intel graphics
Monster Hunter Wilds' PC version being biblical garbage
Wuthering Waves disabling 120 FPS support unless your hardware is whitelisted (leading to hilarious situations like @Pasi123 being denied this with a Core i9-9980XE)
Genshin Impact and its 60 FPS lock/half-resolution textures
Honkai Star Rail hiding 120 FPS mode behind a registry key, massively outdated DLSS DLL, because of course why would they maintain the game client
Zenless Zone Zero's DX12 mode broken for over a year, forcibly disabling Ray Tracing on AMD hardware, forced 71% scale on its DLSS 4 implementation - that when it actually works at all, current version of the game just ignores the command line switch to boot the game in DX12
YouseethisMany eyes are turning towards denuvo as the culprit.

In any case, this goes against the concept of direct3d.
Yes, it does go against the concept of DirectX - unless this was a deliberate, intentional choice by the developer to prevent the game from starting on Intel hardware by either blacklisting the 8086 vendor ID or only allowing it to run if it detects 10DE (Nvidia) and 1002 (AMD)

Denuvo has nothing to do with this
mechtechDoes it work on Intel integrated?? ;)
No
Posted on Reply
#8
Solaris17
Super Dainty Moderator
Dr. Drodeliberate, intentional choice by the developer
I actually think it was this, but not the way people think.

This was a thing for some games and even software way back when Alchemist was released.

I am willing to bet given the base complexity of the games graphics they black listed intel GPUs, but I am willing to bet like Adobe and CoD before them (best effort at remembering a few of the games/software affected back in the day) they did this in an attempt to blacklist iGPUs. The 8086 vendor string is too broad to just block for a graphics device though, and I am willing to bet given there "literally just refund it" they did not code this in a modular way. I am wondering if they just straight up:


#include <windows.h>
#include <dxgi.h>
#include <iostream>

#pragma comment(lib, "dxgi.lib")

bool HasIntelGpu()
{
IDXGIFactory* factory = nullptr;
if (FAILED(CreateDXGIFactory(__uuidof(IDXGIFactory), (void**)&factory)))
return false;

bool foundIntel = false;
IDXGIAdapter* adapter = nullptr;

for (UINT i = 0; factory->EnumAdapters(i, &adapter) != DXGI_ERROR_NOT_FOUND; ++i)
{
DXGI_ADAPTER_DESC desc = {};
if (SUCCEEDED(adapter->GetDesc(&desc)))
{
if (desc.VendorId == 0x8086) // Intel
{
foundIntel = true;
adapter->Release();
break;
}
}

adapter->Release();
}

factory->Release();
return foundIntel;
}

int main()
{
if (HasIntelGpu())
{
std::cerr << "Intel graphics device detected. Exiting.\n";
return 1; // or ExitProcess(1);
}

std::cout << "No Intel GPU detected.\n";
// Continue app startup...
return 0;
}

declared it intel gpu = no instead of doing an array of device IDs and now they are too lazy to go back and unfuck it.
Posted on Reply
#9
Darmok N Jalad
As much as this sucks as a practice, I guess Intel now knows how it feels to be shut out or artificially kneecapped at the software level for reasons. AMD ate the genuineIntel sandwich for a long time.
Posted on Reply
#10
Dr. Dro
Solaris17I actually think it was this, but not the way people think.

This was a thing for some games and even software way back when Alchemist was released.

I am willing to bet given the base complexity of the games graphics they black listed intel GPUs, but I am willing to bet like Adobe and CoD before them (best effort at remembering a few of the games/software affected back in the day) they did this in an attempt to blacklist iGPUs. The 8086 vendor string is too broad to just block for a graphics device though, and I am willing to bet given there "literally just refund it" they did not code this in a modular way. I am wondering if they just straight up:


#include <windows.h>
#include <dxgi.h>
#include <iostream>

#pragma comment(lib, "dxgi.lib")

bool HasIntelGpu()
{
IDXGIFactory* factory = nullptr;
if (FAILED(CreateDXGIFactory(__uuidof(IDXGIFactory), (void**)&factory)))
return false;

bool foundIntel = false;
IDXGIAdapter* adapter = nullptr;

for (UINT i = 0; factory->EnumAdapters(i, &adapter) != DXGI_ERROR_NOT_FOUND; ++i)
{
DXGI_ADAPTER_DESC desc = {};
if (SUCCEEDED(adapter->GetDesc(&desc)))
{
if (desc.VendorId == 0x8086) // Intel
{
foundIntel = true;
adapter->Release();
break;
}
}

adapter->Release();
}

factory->Release();
return foundIntel;
}

int main()
{
if (HasIntelGpu())
{
std::cerr << "Intel graphics device detected. Exiting.\n";
return 1; // or ExitProcess(1);
}

std::cout << "No Intel GPU detected.\n";
// Continue app startup...
return 0;
}

declared it intel gpu = no instead of doing an array of device IDs and now they are too lazy to go back and unfuck it.
Yeah, something like that. It reminds me of Fallout 3 somehow. That game came with different shader packages that loaded depending on whether you had ATI or NV hardware at the time, and Intel GMAs were simply unsupported. Someone came up with a DLL that causes the game to pick it up as an Nvidia 7900GS, its funny that even many many years later Intel's official advice is to just download this mod

www.intel.com/content/www/us/en/support/articles/000093745/graphics.html

I wonder if something similar could be done to Crimson Desert, like a custom dll (dxgi perhaps?) that causes the Arc B580 to be detected as say, a 7700 XT or 4070?
Posted on Reply
#11
Youseethis
Dr. DroYes, it does go against the concept of DirectX - unless this was a deliberate, intentional choice by the developer to prevent the game from starting on Intel hardware by either blacklisting the 8086 vendor ID or only allowing it to run if it detects 10DE (Nvidia) and 1002 (AMD)

Denuvo has nothing to do with this
That would be condemable.
Posted on Reply
#12
Solaris17
Super Dainty Moderator
Dr. DroYeah, something like that. It reminds me of Fallout 3 somehow. That game came with different shader packages that loaded depending on whether you had ATI or NV hardware at the time, and Intel GMAs were simply unsupported. Someone came up with a DLL that causes the game to pick it up as an Nvidia 7900GS, its funny that even many many years later Intel's official advice is to just download this mod

www.intel.com/content/www/us/en/support/articles/000093745/graphics.html

I wonder if something similar could be done to Crimson Desert, like a custom dll (dxgi perhaps?) that causes the Arc B580 to be detected as say, a 7700 XT or 4070?
Not sure, I could setup my lab and wait for it to DL and try, for those more enterprising and at the ready though I did a quick test.

This is the DLL you need to replace.



I backedup the original and renamed the attached d3d9 dll.

You can find this under:

wherever_tf_you_installed_it/Crimson Desert/bin64/d3d12/

It does break some things, but the game actually loads, albiet for sure with dx9 quality.

Main menu:



random videos inside the game:



The game itself:




Unfortunately the game itself does not list GPU used like some games, so I could not confirm if it saw it as a "7900GS". I attempted to pull up the original authors thread to see what part of the DLL he modified as no strings for "7900" exist in my hex editor, but unfortunately it 404'd.
Posted on Reply
#13
Post Nut Clairvoyance
Apparently the game is badly optimised anyways, a friend tried to play it and would keep crashing on his 4070 rig
Posted on Reply
#14
esserpain
Dr. DroI am so incredibly frustrated with Asian game developers and their culture of treating the PC like a complete afterthought. It's never been easier to get a game on PC than it is today, yet they consistently screw up and continue to ship slop, just on the top of my head:

Crimson Desert explicitly blocking Intel graphics
Monster Hunter Wilds' PC version being biblical garbage
Wuthering Waves disabling 120 FPS support unless your hardware is whitelisted (leading to hilarious situations like @Pasi123 being denied this with a Core i9-9980XE)
Genshin Impact and its 60 FPS lock/half-resolution textures
Honkai Star Rail hiding 120 FPS mode behind a registry key, massively outdated DLSS DLL, because of course why would they maintain the game client
Zenless Zone Zero's DX12 mode broken for over a year, forcibly disabling Ray Tracing on AMD hardware, forced 71% scale on its DLSS 4 implementation - that when it actually works at all, current version of the game just ignores the command line switch to boot the game in DX12
I’m next to certain that most of the PC limitations for miHoYo’s games (especially the 60 FPS lock in Genshin and HSR) have more to do with backroom deals with Apple than anything else. Hell, none of miHoYo’s mobile games even support more than 60 FPS on Android. Save for HI3 getting 90 FPS on some devices, but that’s still not nearly as robust as the 120 FPS you’ll get on the latest Apple stuff. Not to mention there being no equivalent to MetalFX for miHoYo’s games on Android.

None of this excuses the incompetence displayed with things like ZZZ’s DX12 mode being broken for so long, OFC. But IMO, that’s more indicative of the Chinese and Japanese playerbases playing almost exclusively on mobile than anything else.

IMO, WuWa trying to force people to get a 40-series GPU just to unlock 120 FPS is more intentionally malicious, but maybe that’s just me having a bone to pick with Kuro. IDK. :laugh:
Dr. DroYes, it does go against the concept of DirectX - unless this was a deliberate, intentional choice by the developer to prevent the game from starting on Intel hardware by either blacklisting the 8086 vendor ID or only allowing it to run if it detects 10DE (Nvidia) and 1002 (AMD)

Denuvo has nothing to do with this
I really feel that something far worse is going on with Pearl Abyss blacklisting Intel GPUs than any of us currently know. Maybe it’s just a hunch, but their vehement blocking of Arc GPUs and Intel’s response indicates to me that there’s much more happening behind the scenes than just typical Asian developer incompetence with the PC platform.
Posted on Reply
#15
Dr. Dro
Solaris17Not sure, I could setup my lab and wait for it to DL and try, for those more enterprising and at the ready though I did a quick test.

This is the DLL you need to replace.



I backedup the original and renamed the attached d3d9 dll.

You can find this under:

wherever_tf_you_installed_it/Crimson Desert/bin64/d3d12/

It does break some things, but the game actually loads, albiet for sure with dx9 quality.

Main menu:



random videos inside the game:



The game itself:




Unfortunately the game itself does not list GPU used like some games, so I could not confirm if it saw it as a "7900GS". I attempted to pull up the original authors thread to see what part of the DLL he modified as no strings for "7900" exist in my hex editor, but unfortunately it 404'd.
It has been a very long time (probably over 10 years) since I last used that bypass mod for anything, but the Fallout 3 launcher reports it as a 7900 GS, and you will find the string if you open that DLL with HxD. Renaming this on the hex editor and saving also changes the GPU's name in the launcher - but all of this seems, at least from what I can tell entirely DX9-related. That it still bypassed the vendor thing though is quite interesting

esserpainI’m next to certain that most of the PC limitations for miHoYo’s games (especially the 60 FPS lock in Genshin and HSR) have more to do with backroom deals with Apple than anything else. Hell, none of miHoYo’s mobile games even support more than 60 FPS on Android. Save for HI3 getting 90 FPS on some devices, but that’s still not nearly as robust as the 120 FPS you’ll get on the latest Apple stuff. Not to mention there being no equivalent to MetalFX for miHoYo’s games on Android.

None of this excuses the incompetence displayed with things like ZZZ’s DX12 mode being broken for so long, OFC. But IMO, that’s more indicative of the Chinese and Japanese playerbases playing almost exclusively on mobile than anything else.

IMO, WuWa trying to force people to get a 40-series GPU just to unlock 120 FPS is more intentionally malicious, but maybe that’s just me having a bone to pick with Kuro. IDK. :laugh:

I really feel that something far worse is going on with Pearl Abyss blacklisting Intel GPUs than any of us currently know. Maybe it’s just a hunch, but their vehement blocking of Arc GPUs and Intel’s response indicates to me that there’s much more happening behind the scenes than just typical Asian developer incompetence with the PC platform.
Funny part - HSR doesn't support 120fps on iOS either. It's just... I have no idea, it doesn't seem like it's backroom deals, it's probably just sheer... incompetence? Or laziness? Who even knows at this point :(
Posted on Reply
#16
Solaris17
Super Dainty Moderator
Dr. DroIt has been a very long time (probably over 10 years) since I last used that bypass mod for anything, but the Fallout 3 launcher reports it as a 7900 GS, and you will find the string if you open that DLL with HxD. Renaming this on the hex editor and saving also changes the GPU's name in the launcher - but all of this seems, at least from what I can tell entirely DX9-related. That it still bypassed the vendor thing though is quite interesting





Funny part - HSR doesn't support 120fps on iOS either. It's just... I have no idea, it doesn't seem like it's backroom deals, it's probably just sheer... incompetence? Or laziness? Who even knows at this point :(
ah you got me, forgot to change it to text string.

Posted on Reply
#17
Rulumi
Solaris17I actually think it was this, but not the way people think.

This was a thing for some games and even software way back when Alchemist was released.

I am willing to bet given the base complexity of the games graphics they black listed intel GPUs, but I am willing to bet like Adobe and CoD before them (best effort at remembering a few of the games/software affected back in the day) they did this in an attempt to blacklist iGPUs. The 8086 vendor string is too broad to just block for a graphics device though, and I am willing to bet given there "literally just refund it" they did not code this in a modular way. I am wondering if they just straight up:


#include <windows.h>
#include <dxgi.h>
#include <iostream>

#pragma comment(lib, "dxgi.lib")

bool HasIntelGpu()
{
IDXGIFactory* factory = nullptr;
if (FAILED(CreateDXGIFactory(__uuidof(IDXGIFactory), (void**)&factory)))
return false;

bool foundIntel = false;
IDXGIAdapter* adapter = nullptr;

for (UINT i = 0; factory->EnumAdapters(i, &adapter) != DXGI_ERROR_NOT_FOUND; ++i)
{
DXGI_ADAPTER_DESC desc = {};
if (SUCCEEDED(adapter->GetDesc(&desc)))
{
if (desc.VendorId == 0x8086) // Intel
{
foundIntel = true;
adapter->Release();
break;
}
}

adapter->Release();
}

factory->Release();
return foundIntel;
}

int main()
{
if (HasIntelGpu())
{
std::cerr << "Intel graphics device detected. Exiting.\n";
return 1; // or ExitProcess(1);
}

std::cout << "No Intel GPU detected.\n";
// Continue app startup...
return 0;
}

declared it intel gpu = no instead of doing an array of device IDs and now they are too lazy to go back and unfuck it.
I can't understand why this would be necessary, a warning to accept instead of blocking would be better, also when they allow AMD APUs and since the minimum they list is Pascal one can get it to boot and run in a GT 1030 with the very low performance one would expect, maybe even a GT 1010 could boot it? This is a very lazy way to deal with this from their part.

I think even Polaris isn't blocked, but Polaris does error out without being able to load because actual missing instructions and extensions, at least on Windows.
Dr. DroYeah, something like that. It reminds me of Fallout 3 somehow. That game came with different shader packages that loaded depending on whether you had ATI or NV hardware at the time, and Intel GMAs were simply unsupported. Someone came up with a DLL that causes the game to pick it up as an Nvidia 7900GS, its funny that even many many years later Intel's official advice is to just download this mod

www.intel.com/content/www/us/en/support/articles/000093745/graphics.html

I wonder if something similar could be done to Crimson Desert, like a custom dll (dxgi perhaps?) that causes the Arc B580 to be detected as say, a 7700 XT or 4070?
May be possible, but this using Denuvo will difficult doing so a bit.

I wonder if a custom DXVK configiration on Linux to make the game think it is allowed GPU would be enough or not?
Posted on Reply
#18
lightning70
My concern is this: if they're selective today, tomorrow they might say about another game, "I'm forcing this processor, for example, it must have x3D memory."
I've never seen such nonsense. This GPU supports all APIs and hardware features.😏
Posted on Reply
#19
Dr. Dro
Solaris17ah you got me, forgot to change it to text string.

Yeah, wonder if changing this to "NVIDIA GeForce RTX 4070" or some other similar 12 GB GPU and then the other references like nv4disp to the current nvlddmkm name or something similar, no idea about modernizing or adapting any of the other functions in this DLL though. You're wayyy smarter than me here :)
RulumiMay be possible, but this using Denuvo will difficult doing so a bit.

I wonder if a custom DXVK configiration on Linux to make the game think it is allowed GPU would be enough or not?
Denuvo is an anti-tamper, it won't stop you from loading DLLs onto a protected executable, it's designed to counter debuggers and disassemblers that can be used to crack the game. That's why this, or DXVK/Special K, etc. all work on Denuvo protected games
Posted on Reply
#20
esserpain
Dr. DroFunny part - HSR doesn't support 120fps on iOS either. It's just... I have no idea, it doesn't seem like it's backroom deals, it's probably just sheer... incompetence? Or laziness? Who even knows at this point :(
It’s available on my iPad Pro M5. IIRC, it’s there on my iPhone 17 Pro, too. So I think it’s only the very newest of Apple devices that have access to it.

Posted on Reply
#21
Solaris17
Super Dainty Moderator
Dr. DroYeah, wonder if changing this to "NVIDIA GeForce RTX 4070" or some other similar 12 GB GPU and then the other references like nv4disp to the current nvlddmkm name or something similar, no idea about modernizing or adapting any of the other functions in this DLL though. You're wayyy smarter than me here :)



Denuvo is an anti-tamper, it won't stop you from loading DLLs onto a protected executable, it's designed to counter debuggers and disassemblers that can be used to crack the game. That's why this, or DXVK/Special K, etc. all work on Denuvo protected games
mm im not on windows and too lazy to look in proton but I found:

- QueryAdapterInfo
- OpenAdapter12
- SelectAdapter
- IDXGIAdapter
- KMTQAITYPE_PHYSICALADAPTERDEVICEIDS

so this is probably using a layer like dxgi.dll which is atleast usually, more visible to the user on windows, that is likely what needs to be modified. These calls suggest that it is calling adapter info through dxgi. It doesnt enumerate on its own like the d3d9.dll did.

edit: shit that almost makes me wonder if a replacement dxgi.dll from another game either in that directory or symlinked would work, now I wonder if the black list is in there dxgi.dll. Simply swapping it with another game might be enough.
Posted on Reply
#22
Rulumi
Dr. DroDenuvo is an anti-tamper, it won't stop you from loading DLLs onto a protected executable, it's designed to counter debuggers and disassemblers that can be used to crack the game. That's why this, or DXVK/Special K, etc. all work on Denuvo protected games
Right, I was confusing with different crashes that can occur with OptiScaler spoofings in this game, my error.
Posted on Reply
#23
Dr. Dro
esserpainIt’s available on my iPad Pro M5. IIRC, it’s there on my iPhone 17 Pro, too. So I think it’s only the very newest of Apple devices that have access to it.

I wonder if it's iPad only... or maybe another bad case of device whitelisting. It's unavailable on my iPhone Air despite the A19 Pro chip :(

Guess it's time I add another complaint to my list of complaints I hurl at every single survey they run. I'm painfully aware I shout at the void, but at least I get to shout. 反正miHoYo里也没人会读英语*

*Nobody can read English at miHoYo anyways
Solaris17mm im not on windows and too lazy to look in proton but I found:

- QueryAdapterInfo
- OpenAdapter12
- SelectAdapter
- IDXGIAdapter
- KMTQAITYPE_PHYSICALADAPTERDEVICEIDS

so this is probably using a layer like dxgi.dll which is atleast usually, more visible to the user on windows, that is likely what needs to be modified. These calls suggest that it is calling adapter info through dxgi. It doesnt enumerate on its own like the d3d9.dll did.

edit: shit that almost makes me wonder if a replacement dxgi.dll from another game either in that directory or symlinked would work, now I wonder if the black list is in there dxgi.dll. Simply swapping it with another game might be enough.
Well, it stands to reason if you're going to block a vendor or at least specific hardware, that you'd at least query for it, and that'd be part of the D3D init process, at least from my understanding. So it's entirely possible that if you dig in there you'll find whatever makes the detection mechanism tick... you managed to get the game to render somehow, so it clearly at least more or less works
Posted on Reply
#24
Solaris17
Super Dainty Moderator
Dr. DroI wonder if it's iPad only... or maybe another bad case of device whitelisting. It's unavailable on my iPhone Air despite the A19 Pro chip :(

Guess it's time I add another complaint to my list of complaints I hurl at every single survey they run. I'm painfully aware I shout at the void, but at least I get to shout. 反正miHoYo里也没人会读英语*

*Nobody can read English at miHoYo anyways



Well, it stands to reason if you're going to block a vendor or at least specific hardware, that you'd at least query for it, and that'd be part of the D3D init process, at least from my understanding. So it's entirely possible that if you dig in there you'll find whatever makes the detection mechanism tick... you managed to get the game to render somehow, so it clearly at least more or less works
Unfortunately the questers of pywel will need to wait, I went back to my regularly scheduled programming.

Posted on Reply
#25
N3utro
Intel are acting like kids to blame it on Pearl Abyss.

It costs money to make a game like this fully compatible with another GPU architecture. If Pearl Abyss didn't chose to do so it's probably because there are too few people using Intel GPUs to make it profitable.

I wouldn't be surprised if they actually asked Intel to cover this cost and that they refused.
Posted on Reply
Add your own comment
Nov 20th, 2026 08:36 PST change timezone

New Forum Posts

Popular Reviews

TPU on YouTube

Controversial News Posts