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.
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."

71 Comments on Intel Offered Hardware Optimization Help to Crimson Desert Developer for Years, Company Says
Sure the game might be a wee bit dated with basic UE 4 features but at least it was relased with no real performance issues to speak of and it had all of the up to date PC hardware support and considering that it was their first non gacha full scale game that is respectable imo. 'The game also has a good Ultrawide support out of the box which can't be said for some bigger AAA titles even nowadays..'
Supposedly they are developing an open world eastern styled 'like Blade&Soul' gacha called project Spirits atm and it will be relased in 2027 according to their plans.
I've been playing Nikke for ~3.5 years and thats also pretty well managed by them for a gacha game so I'm defo keeping an eye on that new game.
As for Wuwa and its constant performance issues in the past year,yeah well I don't even want to go there as you can see my posts in the gacha topic.:laugh: 'Lovely game that is being poisoned with constant performance issues and they keep making it worse..'
@Solaris17 Did you test the DLL swap on Intel hardware or did you simply check that the swap would function in the first place using your main 5090 rig?
I have too much on my plate to handle this testing this weekend. I am also flying for several weeks in the next few. Maybe I can get to it during the week if some enterprising individual does not.
That said I assume from my testing that a few things MAY be true.
Replacing that DLL with another will load the game, given that the original calls dxgi simply replacing that DLL might work. Additionally from experience generally anything that links to dxgi will search its current directory first, now that isnt a given, just default behavior. If THAT is the case you may even be able to copy over a dxgi from another game into that dir and have a similar experience bypassing the need for straight dll replacement.
The default .dll does not indicate any kind of blocking inside of it. So all of this is educated guesses based on what I got to work, and other games and software I have done similar with. It is still totally possible they pearl abyss blocked it in the executable and not the .dlls at all.
I run linux and have a 5090 I hate trying to remove. To test this properly I need to tear down my test bench in the other room swap drives, download crimson desert, then do the testing all over via KVM.
If people care I will do it; I am also interested, just not interested enough to stop my current embedded device firmware and dedicate the man hours to this.
:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::EDIT:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
When replacing d3d12core.dll with the one I use for gshade it runs with a single thread pegged and no error. Fortunetely gshade creates a log file in the same directory. The log indicates it finished, so its likely just a bug or some kind of protection because its a hook.
Moving on, replacing the original .dll with one that is dx9 also did not work.
Further, using d3d12core.dll from the new resident evil and starwars outlaws also did not work.
Nor did running these in any combination of original/replacement dll with dxgi.dll renamed or otherwise.
This is all on an A770.
This prompted me to go with my theory from before.So I did just that and looked. the error:
Not only appears, but only appears in once place in the CrimsonDesert.exe. So the check is in the game itself.
However; like system logs, you should never care about the occrance, you should care about what came before and after. After all, you already know there is a problem.
Looking before the error almost immedietely is a gorgeous list of hand specified GPUs, now these likely are for specific game defaults or logic to impliment things like textures a specific way because of bugs. However; The absolutely lack of any Intel GPUs is reason for me to think they explicitely block them, OR they are calling maybe a framebuffer in a way that is bespoke that isn't handled gracefully on Intel.
I want to make it clear though, other then the outdates non-sense you see around the forums about software rendering, not only are the details generally not accurate that was fixed in drivers, it doesnt apply to battlemage and up, finally, this game is DX12 and as such none of that matters for a game such as this.
Now I tried to add a 770 to this list, naming convention likely matters so its important to try several, but again, these may only be listed because they are bypassing something, or otherwise have special behavior attached to them.
Its also important to understand that a ".exe" can actually be made up of several files (you can embed other exe's, dll's, images etc) and this text can belong to one of those, and it can be as arbitrary as a .txt file that just has some lines read by some other function, they can also simply be code comments.
In any case I failed and it would not boot. This can be simply because I am an idiot, piracy checks caught it, I damaged the exe in an unintended way, these entries have nothing to do with the actual restriction, there are checks elsewhere that also need to be bypassed, there simply is just an issue with how they interact with the GPU, a bunch of other things.
I've already spent several hours on this so I'm going to go back to what I was doing.
Very forward thinking game
Thanks for your service @Solaris17 that's some great investigation you got there
The bypass appears as an overwrite of the unsupported device values, and it does get past the error and attempts to load. It however does not successfully load, as many have sadly discovered on the reddit thread. Though some in that thread have gotten farther than I have in attempting to make use of this edited executable, presumably with Battlemage cards? I can't get very far with the A770.
Note that there are other small edits across earlier offsets, a half-dozen or so values.
The offending component of the .exe containing that hardware list. Not that it helps any, but it's good to know where it is.
I'm not actually skilled at any of these things, and I don't have any proper idea where to go from here. I am, at best, a spectator. We tried the obvious tricks and got nowhere.
What i did:-I downloaded an .exe file that was shared on Reddit and pasted it into the game folder.
-I also checked the compatibility settings of the .exe file:
Run this program in compatibility mode for Windows 8,
Disable fullscreen optimizations,
Run this program as administrator,
-Then I went to AppData\Local\Pearl Abyss\CD\save and edited the file "user_engine_option_save.xml." Where it said:
"OptionStringVector Name="_numFramesToGenerate" _value="2">"
I changed the 2 to 0.
-In the Intel panel, I disabled overclocking and limited the FPS to 30. Once the shaders were downloaded, I removed the FPS limit.
And that’s all, I think. I used OptiScaler for spoofing, but I removed it and the game still opens, so apparently it's not necessary.
The game opens but everything looks blue, so I don’t know what else to do haha. But if you want to try it, that’s what I did.
This is line with your:I am assuming it is trying to load that blob of voxels then losing its mind. This is likely a shader comp issue, since this is done per machine, it is probably very unhappy trying to do this. hmmmm that gives me an idea, I wonder if the gshade dll still fails, that should try to compile.
The answer is no.
Anyway, I didnt feel like re-installing drivers so instead of my ARC Pros, I decided to try and find my B580.
While I was digging through the closet the table had my MTT S80:
nope; with the standard exe you get the normal unsupported GPU error, with the modified exe you get the following:
Though it's honestly not surprising given my other tests with my S80, its good to know that maybe this just isnt an Intel issue.
Moving on.
With a straight exe replacement we get some loading after a few crashes. Though it does stop responding often.
and back, this was without any modifications other then the exe. I went made dinner, came back and it was still like this. I then tried a few mixes of directx 12 .dll's JIC. From outlaws and resident evil. Still no good. Maybe it just needs a 45min compile time like Black Myth Wukong lol.
I won't modify any other files, thats way beyond scope of what should be needed, (here we are hex editing files I know) however, given what I've seen there really isnt a reason this cant work besides perl abyss being difficult.
Kind of funny to see the S80 also fall over but that's ImgTec AXT or BXT based, which is technically fully DX12 compliant but also really awkward with software. They've got new drivers every couple of weeks though, maybe they'll shoehorn in some kind of hack to make the game "work". MooreThreads are crazy, I'd love one of those cards at some point.
Rolling back through the setup process with the GTX 1070 did not result in a different outcome, so it wasn't anything that was preventable through hot swapping devices around. I believe I will be requesting my $77.20 refund and moving on with my life, content that the A770 does run the games I have an actual interest in playing but does not run games I had no desire to.
Though having bought the game I suppose I can now leave a legitimate negative review, even though I went in knowing there was a near-zero chance of it working. Bonus.
But ultimately is what Pearl Abyss decided, and since launching is blocked, even if Intel fixes the game on Arc themselves if they want, it would still be a funny case of a game that needs patching to boot because of the checks.
Interesting results from the MTT S80, hopefully either Intel or Moore Threads can advance and offer more competition, better products and gain market in the future. With the current GPU market situation more vendors and proper competition would be good for the GPU market space.