Used Dependencies crawler to look deeper at each DLL and compared between laptop (Supremacy working) and desktop (crashing)ĩ. CAB file in \Program Files (x86)\Microsoft XNA\XNA Game Studio\v3.1\Redist\DX Redist\ and put directly into Supremacy folderĨ. Replaced X3DAudio1_6.dll from corresponding. Found an issue with X3DAudio1_6.dll -> not recognized as valid DLL by multiple programs (CFF Explorer, Dependencies)Ħ. Checked if all DLLs and dependencies were x86 (32-bit) versions -> yesĥ. Ran DISM restore and sfc again, didn't restartĤ.
NET yet again but actually search for the culprit DLL file(s). So what I did today was NOT trying to repair/reinstall XNA or. Shows the problem in various games with various XNA and/or. "Could not load file or assembly '' or one of its dependencies. some kind of missing, faulty, or wrong x86/圆4 DLL. I am aware that it's most likely a general XNA or. Since the issue kept bugging me, I tried fixing it again today. Are there different XNA 3.1 versions? Mine says 7.0 The other civs seem to be doing fine judging by the log file, also attached.ĭon't know what to do. I could even terraform a planet, but then it crashed after colonizing, see second error log. Or as I just found out, it also crashes when trying to build a ship in Omarion, see different error log attached.Īnd after trying some more, for some reason the latest Dominion start didn't crash when visiting another star (but there are no stars or planets visible). Crash when starting the game or when playing Dominion it crashes upon visiting an actual star.
D3DX9_31 DLL WINDOWS
Installed 3.1 fresh again, also restarted Windows just to make sure, and the error persists.
D3DX9_31 DLL INSTALL
I also uninstalled 3.1, then the game wouldn't start with a prompt to install it. Could you try uninstalling 4.0 and see if that works? The game requires 3.1, not 4.0 - the latter may be overriding 3.1. My guess is your issue is having both XNA versions installed. Apparently the problem is with stars, as the nebula start works but as soon as I fly to a normal star system it appears empty and crashes on the next turn. While testing various DLL versions, I noticed that I can actually start a game as Dominion. I'd love to play the game again, especially as it seems a lot more playable than last time I checked. Also not putting them into the Supremacy folder.ĭoes anyone have any ideas which DLL might be the culprit? And which version would work with Supremacy? There are also multiple version of those DLLs in WinSxS, but none of them seem to work. Now the Visual Studio/C++ 2008 runtimes msvc?90.dll don't show up in Windows/SysWOW64 or system32, unless manually copied there. So, as usual with older games/frameworks the likely culprit is a Windows DLL. So keep this solution in mind, if you ever encounter directX problems with older games again, even if the error message might not point to it, it is worth a try.Currently installed "classic". None of my searches for solutions brought this solution up, but it was a solution i found years ago for something else, and it clearly worked even tho it was for newer directX files. However the Origin error didn't remind me of this problem based on the error message and the old dll file i have was d3dx9_38 not 31. My bet is that this will be the solution to A LOT of directX problems in the future, when it comes to old games. Since this seems like a problem that is going to happen more as stuff get's older, considering i had to do this with another game that i dont even remember. So you have to use this method of reinstalling and not just an installer. Once that's done, you can now finally play your game.Ĭlearly even if you have older direcX files installed it wont use/find them. Now you can then go into the Mass Effect folder - search for "DXSETUP.exe" and run that installer. old at the end of the file so that it will be called "d3dx9_31.dll.old"ĭO THIS FOR BOTH FILES, the one in System32 AND the one in SysWOW64. Now go into these locations and locate the file.Įither copy and save the file to another folder, then delete it OR as I did, simply rename the file and add a. It will find and show you 2, each one located in different folders called System32 and SysWOW64.
Search on you computer for the file called "d3dx9_31.dll". So i searched for the dll file on my computer and went into the folders it was located in and saw the old files i edited for the other game, tried out what i did then and it worked. I remembered that when i tried to play an old game a couple of years ago, don't even remember which one, that i had directX problems as well.