Resolved-Workaround: initialization Error!
#31
Is KB2533623 installed on your system? (See the dwFlags parameter section in the LoadLibraryEx  documentation)

I can always not restrict the search directory when LoadLibrary is called.

EDIT: Try https://ci.appveyor.com/api/buildjobs/o2...ppVeyor.7z

Sponsored links

#32
I experimented a bit more and I'm not sure why I didn't realize this earlier

When I download any build, I usually just drag the new files into my "installed PCSX2 folder" and go on my merry way. The problem was that I was trying to set GSDx to something other than AVX2 or SSE2, which are the only instruction sets compiled on dev builds and the old GSDx .dlls were never overwritten.

The weird thing is this never happened before 512...

Not sure if this is a legitimate issue anymore; but here's your proof that D3DCompiler does load correctly (at least on AVX2 Tongue)
Code:
LoadLibraryExA("d3dcompiler_47.dll", 0x00000000, 0x00000A00) called from "GSDX32-AVX2.DLL" at address 0x1002AD33.
LoadLibraryExA("d3dcompiler_47.dll", 0x00000000, 0x00000A00) returned NULL. Error: The parameter is incorrect (87).
LoadLibraryA("D3DCompiler_43.dll") called from "GSDX32-AVX2.DLL" at address 0x1002AD5D.
Loaded "D3DCOMPILER_43.DLL" at address 0x5A880000.  Successfully hooked module.
DllMain(0x5A880000, DLL_PROCESS_ATTACH, 0x00000000) in "D3DCOMPILER_43.DLL" called.
DllMain(0x5A880000, DLL_PROCESS_ATTACH, 0x00000000) in "D3DCOMPILER_43.DLL" returned 1 (0x1).
LoadLibraryA("D3DCompiler_43.dll") returned 0x5A880000.
GetProcAddress(0x5A880000 [D3DCOMPILER_43.DLL], "D3DCompile") called from "GSDX32-AVX2.DLL" at address 0x1002AD80 and returned 0x5A8E6C20.
DllMain(0x5A880000, DLL_PROCESS_DETACH, 0x00000000) in "D3DCOMPILER_43.DLL" called.
DllMain(0x5A880000, DLL_PROCESS_DETACH, 0x00000000) in "D3DCOMPILER_43.DLL" returned 1 (0x1).
Unloaded "D3DCOMPILER_43.DLL" at address 0x5A880000.
#33
(04-06-2016, 01:05 AM)turtleli Wrote: Is KB2533623 installed on your system? (See the dwFlags parameter section in the LoadLibraryEx  documentation)

I can always not restrict the search directory when LoadLibrary is called.

EDIT: Try https://ci.appveyor.com/api/buildjobs/o2...ppVeyor.7z

This build - working for me! Smile Thanks!
Then you have found what was the problem? Rolleyes
#34
Well, it seems LoadLibraryEx doesn't work on your systems, even though it should if all Windows updates are installed. Weird.

If either of you have a controller that supports XInput, can you check that it works properly in LilyPad? I used LoadLibraryEx there as well.
#35
(04-06-2016, 10:49 AM)turtleli Wrote: Well, it seems LoadLibraryEx doesn't work on your systems, even though it should if all Windows updates are installed. Weird.

If either of you have a controller that supports XInput, can you check that it works properly in LilyPad? I used LoadLibraryEx there as well.

Sorry. I have only a Direct-Input gamepad Blush
#36
I pushed the workaround - it's not really a code problem, but I suspect more people will likely have trouble with it so I made the changes anyway.

Please test 548 (or later).
#37
(04-06-2016, 09:27 PM)turtleli Wrote: I pushed the workaround - it's not really a code problem, but I suspect more people will likely have trouble with it so I made the changes anyway.

Please test 548 (or later).

548 - Error
549 - OK Smile
#38
Oops. Typo. I did mean 549.

@CK1 - Can you confirm too?
#39
All instruction sets are working for me. Good Job!
#40
Thank you for your report.
This bug report has now been marked as Resolved with a workaround since it has been fixed on our code base.

This thread will now be closed and moved to the resolved bug reports subforum.




Users browsing this thread: 1 Guest(s)