Pcsx2 directx error drivers#
Pcsx2 directx error update#
Pcsx2 directx error driver#
Pcsx2 directx error iso#

They contain the hash of the pixel shader, and the value they pass to their parent vertex shader. In the '.ini' files inside 'GameFixes' there are shader overrides with comments saying what they fix (sometimes).

Pcsx2 directx error update#

The values after 'Hash=' may change with future GSdx versions, but I will be able to recognize them and update the fix. 'w3' is an extra option about the fix I made for the skybox in the Ratchet & Clank saga (it forces the skybox to max depth without breaking other things in those games). 'x3' for regex 1, 'ењ“' for regex 2, and 'z3' for regex 3. Those are the three vertex shaders I stereoize with regexes, and their default values for stereoization. The fix includes working examples for games I own, inside the 'GameFixes' folder. Even with a small library of 30 something games I found a little more than 10 conflicts between games. So fixing all games at the same time is impossible. Most of the affected games need between 1 and 3 in my experience.Дў- Fixing something in one game can break something else in another game, or even in the same game in some cases. Still, games don't usually need a lot of these. This is where things get more complicated, for these reasons:ДЎ- Future PCSX2 (specifically GSdx) builds may change the hash of the generated shaders, rendering all game specific fixes useless. In these cases, you need to tell the regex to not stereoize a specific pixel shader. Sometimes, or usually, disabling some of the regex isn't enough to make a game perfect or almost perfect, because you will be disabling more things than needed. Warning number 3: for advanced users and perfectionists A lot of times a mix of regex 3 and regex 2 will fix HUD issues, but regex 2 is usually related to other effects. And that's also their order of importance, as you'll almost never have to disable the first one. They are 'j', 'k' and 'l', and I'll refer to them as 'regex 1', 'regex 2' and 'regex 3'. The first and most simple solution, which may be partial or fix some things and break others but it's useful many times, is using three hotkeys I offer to disable stereoization in each of the three shaders that control geometry. The regex function tries to not stereoize things that have a depth value of 0 or 1, and in some games it works (most of the HUD of the Kingdom Hearts games). The problem is that some effects of those shaders need to not be stereoized, like the HUD or some double stereoized effects (sometimes bloom, blur filters, shadows.). Instead, it uses a real time 'find and replace' function for exactly three shaders that control all geometry in all games. This fix was done without using physical shader files, for better future compatibility. GSdx configuration requirements and recommendations If it doesn't work at first try, double click again until it's borderless fullscreen and try pressing alt+ enter again. Press alt+enter, and the game should trigger exclusive fullscreen and 3D Vision. Double click on the game window so it's resized to borderless fullscreen. This action will unlock esclusive fullscreen, needed for the next steps. It doesn't matter if you apply changes or not. After graphics of the game start to appear, or at any moment after that, open the GSdx configuration (you can press escape to close the game or just open the configuration directly), change settings if you want, and then close it.

Pcsx2 directx error iso#

Choose a game (choosing the ISO from the recent list, or searching one manually.) and boot it. After installing all the needed files, if you try to open the GSdx configuration, the emulator will crash. Make sure it's configured like this before: Copy the 'SpecialK32.dll' to your PCSX2 folder and rename it to 'dxgi.dll'. The depth hunting OSD works fine with this method. If not, once should be enough.ДЄlt+tabbing out of the game can be safe, but not pressing scape to minimize the window. If your default PCSX2 option is opening games in fullscreen, then press it twice. Run a game and press alt+enter as soon as you can until it triggers 3D. Option 1 (recommended and easiest): using this specific Special K version as it is (dxgi.dll and dxgi.ini). At the time of writing this post, I have tried a few options:

Pcsx2 directx error drivers#

If you use drivers newer than 391.35 and you're not using that specific PCSX2 build, need Special K.

Pcsx2 directx error driver#

If you want vsync, let the driver decide and enable it in the emulator, so you can still use F4 to unlock the fps limiter. If you notice strange frame drops to 40fps, try disabling vsync in the drivers.