Resolved-Workaround: initialization Error!

[CK1]

I tried replacing the method. It helps only exchange GS plugin on version of the 511 for example. As I think the problem is in the new version of the GS plugin

GSDx wasn't changed though. I now agree that it has something to do with the First TIME Wizard. Maybe Import vs Overwrite, and how the files are being used?

[willkuer]

All updates are installed several times, everything is checked, but the plugin still wants something

And it would be interesting to know what it wants. That's why I suggested to use dependency walker.

[AlexVS]

And it would be interesting to know what it wants. That's why I suggested to use dependency walker.

[jesalvein]

and you don't have any error when installing this ?

[AlexVS]

and you don't have any error when installing this ?

I installed it all a hundred times already. error in the GS plugin, and not in the system

[refraction]

I installed it all a hundred times already. error in the GS plugin, and not in the system

well it's not, because it works fine for Bositman on Windows 7

[jesalvein]

I don't have any problem in win7 X64 Sp1 either.
Tried on win 8.1 X64 to day, it works fine too.
that's why I asked the OP.

That said, Willkuer's suggestion would be a good idea

[Blyss Sarania]

I just checked on my secondary Windows 7 x64 partition and it works for me.

[turtleli]

Well, it probably is a system error since most Windows 7 people aren't having trouble and I also tested on both a Windows 7 32-bit and 64-bit VM without experiencing that error.

What's changed from 518/521 is that d3dcompiler_{43,47}.dll is used instead of d3dx{9,11}_43.dll.

So the behaviour from 518/521 onwards is:
Windows Vista and 7
Will attempt to load D3DCompiler_47.dll (folder with pcsx2.exe, then system32/syswow64 depending on 32-bit/64-bit though it shouldn't be present there on Windows Vista/7).
If that fails, it will attempt to load D3DCompiler_43.dll (system32/syswow64 only).
If one of the previous steps succeeds, it will attempt to find the D3DCompile function.
If it fails to find/load either dll or function - the update DirectX message appears.

Windows 8.1 and 10
Will only attempt to load D3DCompiler_47.dll and find the D3DCompile symbol. The rationale is it's distributed with the system, and if it fails, the system is likely broken in some way. There's no message if it fails (I suppose adding a "Your system is screwed" message might be a good idea).


So maybe there's a fault with d3dcompiler_43.dll on any affected systems. I suppose it might be helpful to have the error code printed out.

Interesting fact: If you don't use Internet Explorer to browse the internet, you probably already have a copy of d3dcompiler_47.dll on your system. Just saying this for no reason.

[CK1]

I profiled pcsx2.exe in Dependency Walker. Here's my GSDx portion of the log (I can also paste the entire log if necessary)