[Devil May Cry 5 Error D3dcompiler 43.dll

0 views
Skip to first unread message

Oludare Padilla

unread,
Jun 7, 2024, 4:01:45 AM6/7/24
to kancandryhe

I got error "Information not available, no symbols loaded for d3dcompiler_47.dll" from D3DCompile function.But dependency walker show d3dcompiler_47.dll is loaded and D3DCompile function is also loaded.I can't find how to fix this.

Devil may cry 5 error d3dcompiler 43.dll


Download →→→ https://t.co/KG8KEB7mpr



Since mesa was just updated to 10.4 and the news told me it now comes with the DX9 state tracker from gallium-nine incorporated in it (!!!) I decided to give it a try in wine with some games to see if the performance is really that much better.
So, I compiled the needed patched version of wine from , without enabling native Direct3D 9 it worked fine, when I enabled it, it didn't work since it was looking for the 32 bit d3d libs in /usr/lib instead of in /usr/lib32 (!!) , since I din't really wan't to mess with too much stuff right then I just did a temporary copy paste of the 32bit libs into /usr/lib.
After "fixing" that the red error message was gone, promising, but I still only got a black screen instead of glorious native DX9 on linux (kinda)... :C

It looks like I'm missing something... no idea what, isn't mesa supposed to contain everything that's needed now ?, I haven't tried the AUR packages, which seem a little outdated anyway, I was only trying this since it's now in the official mesa release.
Well, since I don't know what is it that I'm missing and the internet did nothing but confuse me when I searched for it I require your assistance, any help will be appreciated.

In the description text it says that you have to create a specific registry key(!) to enable it (or use winecfg and tick a checkbox).
Of course this information is about the Ubuntu version, so it may be irrelevant to Arch Linux, but anyway.

Just grab the PKGBUILD from official repo, git clone the patched version, tar it, change the md5sum and add --with-d3dadapter to ./configure, makepkg. I already made these tests which you want to try and I'm not satisfied. But that was expected, since this is new stuff and it's not expected to be perfect. The flaws were artifacts and broken textures in some games. Yes, there's a big step in FPS and performance, but there's more to be done. Also, it's just a wine/crossover benefiting feature. Nothing else benefits from this as far as I know.

@ackalker I already have that enabled, I kind of said it in the first post , I might end up in the IRC channel if I can't get it working, but I thought looking here first was a better starting point, since I'm looking to get the thing to work on arch anyway.
About the IRC log, I already checked that out, the thing is, that is about gallium-nine and some patching around quite some time before it was integrated into mainstream mesa, I could look into getting the unofficial version to run, but since d3d9 support is now in mesa I thought it wouldn't be necessary.

@smirky I don't know how that would be that much different from just making it without installing and running it from that same folder which is what I did, I tried it anyway, compilation took like 10 times as long for some reason, I still get the same messages after that.
I've gotta say that I'm rather impressed, getting d3d9 to work natively on linux is no easy feat, for what is essentially an initial release this is quite promising, even if there still are a lot of bugs in it and performance is still not as good as on windows and if it is realistically only useful for wine, we are likely going to be stuck with crappy ports (the fact that the first release of this is already surpassing a lot of "native" ports in performance is just telling of how much work really goes into linux ports) and tons of windows-exclusive releases for a while, that's without mentioning legacy support for thousands of d3dx9 games and applications in general.

Anyway, thank you both again for your help, but I'm kid of back to square one, I don't think this is an issue with wine, but rather with mesa, apparently I should install xf86-video-ati with d3dx9 patches (it also mentions ati-dri, isn't that discontinued ?), the aur script isn't working, it fails to compile, so I assume the source has changed a bit since it was updated back in august.

That's pretty much it. Mesa is compiled with the state tracker as is. You have to go into regedit of course and enable Direct 3D9.
Please do keep in mind things said here:
They will guide you through for the things I said above and also tips for debug what went wrong.

That did it, I was missing xf86-video-ati-git, then x wouldn't start because of a version mismatch so I replaced it with xorg-server-git and now it works!
You have been very helpful, thanks again. Now I'm in for some testing.

I'll just add that I don't really recommend this to anyone, I don't know if it's the mix and match of packages, like xf86-video-ati unofficial from last month with mainstream mesa, or xorg-server-git with all of that or if it's just the way this is right now, but it is ridiculously unstable, X crashes very frequently and seemingly at random, there are tons of graphical glitches in kde, chromium's window occasionally freezes while the browser if actually still running, etc... I'll have to try and find out what's actually causing all this instability, right now it's just a mess.

I don't experience any crashes, but what you say about chromium, yes. I thought this was because of my fluxbox, but turns out it might not be. When chromium gets minimized, there's a random chance the window freezes. No other app seems to have this behavior, which is also weird.

I don't think the drivers should be doing any of this, I expect the d3d9 part to be unstable and maybe burn my computer but everything else should be acting pretty much the same as ever, I feel I should blame X for all of these crashes...
I' ll try checking some stuff, recompiling again and what now, but for now I have removed all the patched drivers, since this is the only computer I have and I actually need to use it now .

No idea about nouveau, as I understand it should work right away, no need for patched packages or anything like that, only patched wine. Have you tried the recommended dll overrides ? d3dx9_24 d3dx9_43 and d3dcompiler_43 ? (I found d3dx9_36 to be useful as well) I found them to either make a lot of games work when using nine or to make their overall performance a lot better than wine's built-in libraries.
However since you are using nvidia, at least right now you'll probably get just as good performance, and likely better compatibility just with wine csmt.

On another note, I can say that after compiling mesa and xorg-server once again most of the crashes are gone, I'm also using all git packages instead of only xf86-video-ati-git.
Performance in most games seems to be at least twice that of wined3d, with almost no glitches, except for a very annoying one, that is only present in some games, like Resident Evil 4 or Devil May Cry 4 (both CAPCOM games btw), a white layer seems to be covering the geometry in some areas, with 2D gui elements rendered fine on top of it, in re4 it happens in most of the game, in dmc4 only in some areas, as far as I can tell geometry is "rendered properly" only that this white thing is covering it. (as evidenced by gpu usage and by the areas that actually render properly), Probably a nine bug.
Other stuff I tested, like Darksouls 1&2, C&C 3, etc. all work perfectly with windows like performance. (I actually get better performance in DarkSouls with nine than in windows).

I tried to go back to testing this now that quite a few changes have been made to mesa-nine but I have so far failed to do so.
When I run KDE 5 with xorg-server-git and xf86-video-ati-git it get's stuck in the logging screen after the greeter, the progress bar stops close to the end and then the cursor appears but kde stops loading, as soon as I switch back to default xorg-server and xf86-video-ati everything is working again.
The odd parts is that it doesn't work even if I use the older version of xorg-server-git that I built the last time I tested this, which obviously worked before.
I also tried some downgrades to stuff like plasma-workspace but that didn't go anywhere.
Has anyone else experienced something like this. ?

795a8134c1
Reply all
Reply to author
Forward
0 new messages