Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
What are your pc specs?
You can also try and run the game as an administrator afterwards(Or restart steam with opening it as administrator).
If that doesn't work you could always try and update your drivers and directX yourself.
You can also navigate to the mpq root folder and see if you can install vredist manually.
These installers can be found here : C:\Program Files (x86)\Steam\steamapps\common\Marvel Puzzle Quest\_CommonRedist
If you then go to :
C:\Program Files (x86)\Steam\steamapps\common\Marvel Puzzle Quest\Binaries\PC\Ship
and rightclick on marvelpuzzlequest.exe and open it as an administrator. See if that works.
You can also try running it in a different compatability mode, this can be done by right clicking marvelpuzzlequest.exe>properties>compatability then select a compatability for windows 7 or 8.
Afterwards you should try running it as an admin.
If nothing works, it could be that the latest game update just doesn't configure right or something of that matter. You could either wait for a new update and try again, or try and reinstall MpQ al over again(I don't know if your save files will be synched so do this at your own risk)
[06/22/17 09:36:59] module: dxupdate(Mar 30 2011), file: dxupdate.cpp, line: 6124, function: CFusion::CFusion
Failed API: LoadLibraryShim()
Error: (0x80131700)
--------------------
[06/22/17 09:36:59] module: dxupdate(Mar 30 2011), file: dxupdate.cpp, line: 2969, function: IsMDXInUse
Unable to initialize MDXCheck.
--------------------
[06/22/17 09:36:59] module: dsetup32(Mar 30 2011), file: dxupdate.cpp, line: 280, function: CSetup::InstallPlugIn
DirectXUpdateInstallPlugIn() failed.
So I think it's a problem with this PC and not MPQ. I'll try installing again with the next laptop I buy.
What you could do, is send these to the MPQ helpdesk. They might be able to look even further into it since they probably get these directX related issue's more often.
It could also mean that your computer isn't compatible with the lasest versions of directx, which would be weird.
Not the latest version of DirectX 11 or 12 (exact version depends on Windows OS), but the legacy DirectX 9, which lives side by side with it.
Not a good idea.
DirectX 9 is modular. A redistributable DirectX installer can be tailored to have optional add-on parts packed in or left out. The original design goal there was probably to slim down the installer payload for download over bad connections; limiting it only to the most-used core of DirectX 9 as a baseline.
Those parts really do need to be installated and registered correctly for software that uses them to work as expected. Luckily most games don't use obscure optional parts that wouldn't already have been installed with the first Dx9 redistributable you install, but if you come across one which does, you're likely to get a few unexplainable crashes down the road.
For Steam you would probably (hopefully?) get those type of Dx9 redistributable installations from a game-specific Redist folder, instead of from the shared CommonRedist folder.
Errors with LoadLibraryShim and CFusion usually means there are orphaned files from removed installations left behind in the WinSxS folder that are messing up the updater. Did you by any chance do any kind of over-the-top repair installation on this machine? Or an over-the-top Windows upgrade?
This computer is a refurbished tower that I bought just a couple of days ago. All I've done is let Windows 10 connect to the internet and it updated itself. So I don't know its history. I'll look for the MPQ helpdesk and see what they say about my error log.
Thanks guys for your help. Narrowing it down to a DirectX problem was very useful.