Sunday, January 27, 2019

PCSX2 [DX11]

3D Vision feature for PCSX2, the PlayStation 2 emulator (DX11 hardware renderer). It uses a manual shader stereoization method without using physical shader files, for better future compatibility.

UPDATE (2019-01-27): updated fix with 3Dmigoto 1.3.14 and new features to make perfect fixes possible. "pcsx2-v1.5.0-dev-2907-gb9df1e643-windows-x86" is the minimum emulator version to use now. See the "OSD and depth hunting" section. Also, you don't need to know the hash of the main vertex shaders anymore. Improved regexes for more fixed games by default.

UPDATE (2018-09-09): added another preset for the black frame insertion "n" hotkey, so you can choose what frame to turn black (because what the fix detects as the "first frame" is random).

UPDATE (2018-09-08): added the "u" hotkey.

UPDATE (2018-09-04): added one more shader regex to the black frame insertion feature. It's needed for some games, and after a lot of testing I saw that Ratchet & Clank 3 displays a black image with this. Added 3D Vision to anaglyph feature. I have removed manual shaders from the ShaderFixes folder and put them in GameFixes under individual folders, because they were affecting unrelated games. Move those txt files to ShaderFixes if you want to play those specific games, and remove them when you're done.

UPDATE (2018-09-01): added a black frame insertion feature ("n" hotkey), inspired by my RetroArch fix.

IMPORTANT UPDATE (2018-08-28): fix updated with 3Dmigoto 1.3.11. There is now a new folder called "GameFixes", where there are multiple ".ini" files (one per game) with ShaderOverride sections. Now at line 38 of "d3dx.ini" you can load them individually. With this, making fixes for individual games is a lot more easier, and also easier to switch to a different game. Old version here.

ANOTHER IMPORTANT UPDATE (2018-03-16): updated for 3Dmigoto 1.3.6, now compatible with ReShade without needing extra steps unrelated to ReShade (I've tested it as dxgi.dll. Its ingame interface, shaders and hotkeys were working fine). Also, at some point in time it started triggering 3D without SpecialK (the old "d3d9.dll" and "d3d9.ini"). That means no more booting games in a weird manner! It isn't caused by the new 3Dmigoto. It may have been drivers or Windows updates, I'm not sure.
SBS, TAB and other 3D modes now run flawlessly. Check the updated instructions and delete all you had from the previous fix, except for the workaround to make 3Dmigoto load in Windows 10. Old version here.

IMPORTANT UPDATE (2018-01-19): fix updated. the new 3Dmigoto 1.2.70 allows me to stereoize render targets automatically. It means that custom resolution tweaks or "Large Framebuffer" aren't needed anymore.

Warning number 1: this isn't as "plug and play" as PC games fixes. It will need user involvement depending on how much you want a perfect experience, because it's impossible to have all games fixed at the same time. It also requires games to be booted a certain way.

- Get a recent PCSX2 build, equal or newer than "pcsx2-v1.5.0-dev-2907-gb9df1e643-windows-x86". Download links are here.
- Configure the graphics plugin (GSdx) to use the DX11 hardware renderer.
- For PCSX2 to be able to see the "d3d11.dll" of the fix on Windows 8.1 or higher, you need to apply this patch for the moment. If the bat file doesn't work, using the "sdbinst d3d11_fix.sdb" in CMD with admin rights may work.
- Download the fix here and unzip its contents in your PCSX2 folder.
- Download the latest GameFixes folder here. Overwrite the folder that comes from the previous link.
- If you have Windows 7, chances are that PCSX2 won't trigger 3D Vision. If that's the case, unzip this there too and follow the old instructions to boot games.
- Open "d3dx.ini" and go to line 41, where it says "List of game fixes.". Uncomment the line for the game you want to play. Don't uncomment more than one at the same time. If you want to create your own overrides, create a new ".ini" file in the "GameFixes" folder and load it the same way as the existing files.

Booting games
Nothing special is needed now. Just make sure you're using DX11 hardware mode and double click the window if you didn't configure PCSX2 to boot games in fullscreen directly. It will automatically use your full resolution and trigger 3D. Switching to other renderers won't crash the emulator anymore. They just won't be 3D.

If you notice strange frame drops to 40fps, try disabling vsync in the drivers. 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.

Old instructions, not needed anymore:

This needs a special procedure. After installing all the needed files, if you try to open the GSdx configuration, the emulator will crash. Follow these steps:

- Open the emulator.
- Choose a game (choosing the ISO from the recent list, or searching one manually...) and boot it.
- 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. It doesn't matter if you apply changes or not. This action will unlock esclusive fullscreen, needed for the next steps.
- Double click on the game window so it's resized to borderless fullscreen.
- Press alt+enter, and the game should trigger exclusive fullscreen and 3D Vision.
- If it doesn't work at first try, double click again until it's borderless fullscreen and try pressing alt+ enter again.

GSdx configuration requirements and recommendations

1- Interlacing: games that shake when the option is set at "None" will most likely be perfect with the "Bob tff" option, and in some rare cases, "Bob bff". Knowing is a game is interlaced (half vertical resolution, which most of these shaky games have) is important for the next steps.

2- Large Framebuffer: it's needed for 3D when you play at 3x native resolution or higher IF the game doesn't have a "progressive scan" mode or cheat code. Warning number 2: this option increases VRAM usage A LOT at 5x-6x native resolutions and higher. Unneeded after the 2018-01-19 fix.

3- Custom resolution: it's needed for 3D IF you are playing an interlaced game (unless you play at native or 2x native) OR IF you really don't want to use "Large Framebuffer". Interlaced games need a higher than normal vertical resolution. Example: Devil May Cry only works in 3D with 3840 horizontal resolution if the vertical resolution is 2879 or higher.
Note: there are ways of forcing 3D via "TextureOverride" in "d3dx.ini". Read the shader overrides explanation. Unneeded after the 2018-01-19 fix.

4- Enable HW Hacks: some games need some of these to render right, especially "Align Sprite" (some Namco games like Soul Calibur 3 or Tekken 5), which demands native resolution multipliers, and "Half-pixel Offset", to have some bloom effects at their correct position. Things not related to 3D.

Warning: use 16:9 or stretched aspect ratio in the emulator. If you use 4:3 while your desktop resolution is 16:9, the emulator won't trigger 3D Vision.

Use of regex toggles
This fix was done without using physical shader files, for better future compatibility. Instead, it uses a real time "find and replace" function for exactly three shaders that control all geometry in all 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...). 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 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. They are "j", "k" and "l", and I'll refer to them as "regex 1", "regex 2" and "regex 3". And that's also their order of importance, as you'll almost never have to disable the first one. 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. In the "PCSX2_3D_game_database.txt" file I include I made a compilation of results of games I have and when you need to disable regex 2 and/or 3 or none.

Use of shader overrides. Warning number 3: for advanced users and perfectionists
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. Or maybe the HUD is related to regex 1. In these cases, you need to tell the regex to not stereoize a specific pixel shader. This is where things get more complicated, for these reasons:

1- Future PCSX2 (specifically GSdx) builds may change the hash of the generated shaders, rendering all game specific fixes useless. Still, games don't usually need a lot of these. Most of the affected games need between 1 and 3 in my experience.
2- Fixing something in one game can break something else in another game, or even in the same game in some cases. So fixing all games at the same time is impossible. Even with a small library of 30 something games I found a little more than 10 conflicts between games.

Now about how to do a shader override. The fix includes working examples for games I own, inside the "GameFixes" folder.

Those are the three vertex shaders I stereoize with regexes, and their default values for stereoization. "x3" for regex 1, "y3" for regex 2, and "z3" for regex 3. "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).

The values after "Hash=" may change with future GSdx versions, but I will be able to recognize them and update the fix.

In the ".ini" files inside "GameFixes" there are shader overrides with comments saying what they fix (sometimes). They contain the hash of the pixel shader, and the value they pass to their parent vertex shader. If you write for example "z3=1", it means that regex 3 won't stereoize that specific pixel shader. If it's "y3=0", it means it will stereoize it, the same as not writing the shader override at all. Useful if you want to enable/disable game fixes break effects in other games.

New: setting them to "=1" now assumes that they are HUD shaders, so they'll be affected by the HUD hotkeys. Set them to "=2" to not stereoize them but not making them count as HUD.

How to get the pixel shader hashes? Search the "hunting=0" line and change it to "hunting=2".

Warning number 4: this will make games less stable when switching out of fullscreen, and VRAM usage will be higher.

After that, run the emulator and play the game you want. Press "0" in the numpad and you will see a green overlay. Numpad keys 1 and 2 will cycle through the available pixel shaders, disabling the current one. Numpad key 3 will dump the shader inside the "ShaderFixes" folder. Get the hash (filename part before "-ps_replace.txt"), open the "ShaderUsage.txt" file that will appear in the emulator folder and search that hash. Example of a random pixel shader:

<PixelShader hash="07ee058e5bed1e6b">
  <ParentVertexShaders>6d64bfd710f98b05 </ParentVertexShaders>

The pixel shader "07ee058e5bed1e6b" is related to vertex shader "6d64bfd710f98b05". If you look a few paragraphs above in this post, you will see that it's regex 1. If you want to not stereoize that effect, write this in the appropriate ".ini" game file (you can create new empty files and then include them in "d3dx.ini" like the existing examples), below other shader overrides if there are any:


Then you can go back ingame without closing it, make the game 3D with the explained method, and press F10. Changes should be applied instantly (it will also reset the state of all hotkeys).

When you are done, close the game and set "hunting" to 0 again. And you can delete your dumped shaders that are inside "ShaderFixes".

OSD and depth hunting (advanced users mostly)
You can enable an OSD that shows information about the current value of hotkeys and other useful information. By default this is disabled, because it makes F10 reloads longer and you could use the depth hunting hotkeys accidentally. With this, you can do a much better kind of fixes than shader overrides. They should be universal.

Uncomment the ";include = ShaderFixes\help.ini" line, in line 38.

When you are ingame, press "c" (maybe a few times) and the OSD will appear near the bottom left corner. This screenshot shows the default state:

Warning: all the following hotkeys can be used even if the OSD is turned off with its hotkey. Be careful of using them accidentally.

Most fixable game effects and HUD that are broken in 3D usually have a specific depth value assigned to them. Under "Depth hunting Regex0", you will see the navigation speed multiplier, "greater or equal than" value and "lower than" value. Depth values between them will become 2D

To select which regex you want to affect, use the "x" and "z" keys. Then it will say "Depth hunting Regex1" and so on.

Use the left and right arrow keys to modify the ">=" value.
Use the up and down arrow keys to modify the "<" value.
Use the ctrl key to change the amount each of the previous case navigate. By default, one press equals +1 or -1. The highest multiplier is x100000.
Hold the shift key and then hold the arrow keys to navigate the depth values a lot faster.

If you press "a", the "Value to save" will be saved in the first free (non 0) variable it will find.
If you press "q", the current depth range will be saved in two variables if they are free (non 0).

A message will appear in the bottom left corner when you press them.

After saving at least one value, if you press F10, the "d3dx_user.ini" will appear in the emulator folder. Inside you will see a "[Constants]" section. Variables go:

- From "$a0" to "$a39": 40 possible depth values that won't be stereoized for Regex 1.
- From "$ar1" to "$ar8": 4 possible depth range pairs that won't be stereoized for Regex 1. The first one in a pair is ">=", and the second is "<".
- From "$b0" to "$b39": 40 possible depth values that won't be stereoized for Regex 2.
- From "$br1" to "$br8": 4 possible depth range pairs that won't be stereoized for Regex 2. The first one in a pair is ">=", and the second is "<".
- From "$c0" to "$c39": 40 possible depth values that won't be stereoized for Regex 3.
- From "$cr1" to "$cr8": 4 possible depth range pairs that won't be stereoized for Regex 3. The first one in a pair is ">=", and the second is "<".

Further F10 presses will keep adding new values you save into free variables.

Pressing ctrl+alt+F10 will delete this file so you can start over saving values.

Now to do a game fix with these values, you need to create a ".ini" for the game in the "GameFixes" folder. Make a copy of "template.ini" with the name of the game and include it in "d3dx.ini" as you see in the existing examples (like "include = GameFixes\Dark_Cloud_2.ini").

In your new game ini file you will see variables corresponding for each regex (40 values and 4 pairs of ranges for each one). The comments in the text let you know what they're for intuitively.

Copy the depth values from "d3dx_user.ini" in the corresponding variables (the order doesn't matter as long as you are in the correct regex), save the changes to the file, and press F10 ingame if the emulator is running. The fixes should take place immediately.

Of course, you can skip the usage of "d3dx_user.ini" to write the values in the game ini directly, if you remember them or alt+tab a few times, because you will see the numbers onscreen.

You will probably need at least some of these hotkeys (which you can configure in "d3dx.ini") when playing. Hotkeys with more than one preset use "shift" as a modifier to cycle backwards.

- v: it changes the type of stereoscopic cameras. By default, both eyes get a modified view for 3D. With one click, the right eye will have the same camera angle as 2D and the left eye will do all the 3D work. One more click, and the opposite will happen. And the last preset returns it to normal. It can be useful for games that stereoize the HUD, making it invisible at normal convergence modes. With the dominant eye you will see all game effects normally.

- b: toggle to unstretch 4:3 games from 16:9. It will be buggy depending on the game, and the sides will flicker. Avoid using this if possible.

- j: regex 1 stereoization toggle.

- k: regex 2 stereoization toggle.

- l: regex 3 stereoization toggle.

- h: convergence presets. Different games may need wildly different convergence levels. I tried to cover as many cases as I could.

- g: multiple God of War 1 and 2 separation and convergence combination presets, from higher to lower. These games present geometry with very compressed depth. This is a workaround that makes them normal. Each preset was carefully crafted, so don't touch your Nvidia convergence hotkey or convergence presets. The Nvidia separation hotkey or wheel is OK to use. Don't use this hotkey with other games unless you find another like them.

- f: toggle for moderately higher max separation. Some games like Soul Calibur 3, Tekken 5, Ys IV and Ys V use a lower separation than the rest of games. 5.6cm instead of 7cm in my monitor. This hotkey makes them have the same depth as the other games. Don't use it with unaffected games unless you know you want it.

- o: HUD depth, for elements that have 0 depth or have a "=1" shader override. Regex 2 excluded for image quality reasons. Buggy, consider not using it.

- p: HUD toggle or its aspect ratio. Same as above for the conditions. The first press changes the aspect ratio of the HUD from 4:3 stretched to 16:9. The second press disables the HUD. The third press restores it. Buggy, consider not using it.

- n: black frame insertion, intended for 30fps games. Three presets (disable one frame, the other, and disabled), and it's disabled by default. This is possible because PCSX2 outputs 60fps no matter the internal fps. Don't use in 60fps games. And beware of the nasty 30Hz flickering, if you are sensitive to it.

This black frame insertion mode doesn't know what frame is the original and what frame is the duplicate, so input lag may vary because it's chosen at random (loading savestates may change it too).

And that's why there are two presets that choose a different frame to turn black. If you care enough about it, run from side to side and choose the preset that shows you the frame that is is more ahead in time. For example, if buildings are moving to the left, choose the frame that moves them clearly more to the left.

If you are crazy and want 20Hz flickering (is there any PS2 game that runs at constant 20fps?), go to the bottom of "d3dx.ini" and change "y4 = (y4 + 1) % 2" to "y4 = (y4 + 1) % 3".

An alternative this hotkey is using ReShade with this shader, if you find games that don't work correctly with mine.

- i: 3D Vision to anaglyph conversion presets (normal, reversed, disabled). Disabled by default. Why use this when you have 3D Vision Discover for anaglyph? Two reasons. One: it allows two or more people to use 3D Vision and anaglyph glasses at the same time, at the cost of some color quality for the 3D Vision glasses users compared to not using anaglyph. Two: for this emulator, it's better to get 60Hz + 60fps per eye than 120Hz + 60fps per eye. Better vsync, low motion blur, etc.

- u: black frame insertion in 2D, made for 60fps at 120Hz. It's mandatory to have 3D Vision enabled. This hotkey is a quick toggle that disables stereoization for all regexes and blacks out the image of the right eye. The result is that at 120Hz you receive 60 games frames and 60 black frames. It can be combined with the "n" hotkey for 30fps games. This doesn't reduce GPU usage in any way. It's the same as if you were playing in 3D. Unless you comment or delete the "[TextureOverride3DRenderTarget]" block in "d3dx.ini", which is necessary to be there for 3D. That way, you'll get 2D performance with black frame insertion.

- t: reverse 3D Vision.

Fix updates
I will update the fix when PCSX2 changes the regex shaders, which can make older emulator versions incompatible. Also, exclusive fullscreen may be an official feature in the future, which will make the included "d3d9.dll" and "d3d9.ini" unnecessary. And it will also make the game booting process simpler and more stable.

I also keep the "d3dx.ini" file in my github account. If the date of that file is newer on github, use it instead of the one that comes with the fix, because it may contain small fixes. Outdated.

User contributions for shader overrides are welcome. Just know the risk of them becoming obsolete in future PCSX2 updates. Depth fixes should be universal.

Side By Side / Top And Bottom / Interlaced compatibility
Uncomment the ";run = CustomShader3DVision2SBS" line in "d3dx.ini" and then press F11 ingame (once it triggers 3D) until you have your desired mode.

This below was for the old version of the fix and it's unneeded now (I'm keeping it just in case):

Normally you would have to uncomment the ";run = CustomShader3DVision2SBS" line in "d3dx.ini" and then press F11 ingame (once it triggers 3D) until you have your desired mode. However, the game window stays black when you try to do it.

The workaround is not enabling that line, starting the booting process until after you have "unlocked" the exclusive fullscreen possibility, uncommenting the ";run = CustomShader3DVision2SBS" line, saving changes, going ingame in fullscreen mode, pressing F10 to reload the configuration, and then pressing F11 until your 3D mode is selected.

Painful, I know. I don't know a way to fix this completely. But the workaround works.

Special thanks
- All 3Dmigoto developers and contributors (bo3b, DarkStarSword, Flugan...).
- All PCSX2 developers and contributors. Without them, we wouldn't be able to even play these games in 2D.
- Kaldaien, for the specific SpecialK build I used in older fix versions to force exclusive fullscreen (0.7.0).
- RibShark, the one who made the compatibility patch to make 3Dmigoto work with PCSX2 on Windows 10.
- Kaimasta, for helping with testing and giving good ideas and inspiration, like the God of War hotkey.

If you liked this and want to contribute for more future fixes, you can donate to this PayPal account:


  1. Brilliant work Masterotaku!
    So many great game`s to try out :)
    Also thnx for all the other great work

  2. Thanks for the fix, let me know if anyone has gotten this working with Windows 7. I am using a passive 3D television display, I get the green text saying PCSX2 but no stereo.

    1. By green text, do you mean the driver profile thing? Have you followed the "Side By Side / Top And Bottom / Interlaced compatibility" section correctly (if it's correct, at the last step using F11 multiple times should be changing 3D modes. If 3D didn't trigger, F11 won't do anything)? And what game are you trying to play?

      You can post the information I need in this thread:

      Because I don't get notifications when there are new comments in the blog.

    2. masterotaku,You're really so great!a Silly question,anyone know how to enable vsync in the lastest version of the simulator ?

    3. The vsync setting that PCSX2 has is useless in my experience. But using "Vertical Sync" -> "Force on" in the drivers (PCSX2 profile or globally if you like it) works perfectly. It will apply when you are in exclusive fullscreen mode. You'll notice it because disabling the frame limiter won't let you surpass 60fps, and you won't see tearing in any case.

    4. Its ok, I was so excited about this fix went and got me a pair of 3D Vision 2 glasses and a decent display so I can enjoy this and all the other great work that has been done here!

  3. I'm sure i'm doing something silly but I am on windows 7 and cannot get anything other then a black screen. The normal green driver profile text appears as well as the game sound. Trying Final Fantasy 12, followed the "side By side...." with no luck, any help???

    Thank you so much for your hard work regardless.

    1. Never mind I was being silly, had a second display plugged in. Works perfect. Masterotaku you are the man!!! Thank you for being awesome and doing what you do (and a super cool name)

    2. Thank you. It's great that you solved that issue yourself, because I don't use more than 1 monitor and couldn't have helped about that.

  4. Thanks for the fix, followed your instructions and tried to make a fix for Forbidden Siren 2 (PAL) on Windows 10. Played through on normal difficulty and everything seems to be fine. Adding in case someone might find it helpful, although there's only one shader that really needs to be disabled and people could just do that with hunting mode...
    ------------add below lines to d3dx.ini----------------
    ;Forbidden Siren 2 (PAL)- needs shader overrides 2 and 3 disabled
    ;GSdx > Advanced Settings & Hacks- merge sprite can help a little with the vertical lines bug
    [ShaderOverrideSiren2_1] ;makes dog/memory sightjacking visible (may make some scenes darker?)
    [ShaderOverrideSiren2_2] ;removes some visual garbage when sightjacking

  5. @masterotaku

    Out of curiousity what advice can you give you give about PCSX2 [even ignoring 3d for a second]. I've put it off for years and been waiting for development to progress and I plug games and get anomalies from increasing resolution. Seems like thats just the way it is and options are go native or get anomalies.


    1. It's useful to check the wiki for specific games ( Some games need hardware hacks, and some don't. I don't have that many games to test, but in general most work fine.

      Some graphics issues are fixed in OpenGL and not in DX11, but we can't use this 3D fix with OpenGL, so sacrifices have to be made. But still, things are better than they were years ago in general.

      I don't have much else to say, other than "don't depend on savestates too much", "overclocking the EE is cool for some games that have variable internal fps", "try not to be GPU limited", etc.

  6. Dear masterotaku. You fix not working with reshade 3.1.0
    Can you check it and fix, if it possible? Reshade is absolutely necessary for pcsx2 - ambient light, fake hdr anm many more great fullscreen shaders there, that makes old games much better

    1. BTW Theese two things can work together (dxgi.dll and d3d11.dll) different dlls loadsame time. I use it both in ffx hd remake for example

      But in this game video plugin not loading

    2. Give me a few days for this. There are new versions of 3Dmigoto that added better Reshade compatibility. Getting 3D to work as it does right now was already difficult, so I won't be surprised if I encounter problems with Reshade even with a new 3Dmigoto build.

    3. Thank you. I hope this two great enchancers will work togathet with your help

    4. Done. ReShade works with this new version that I've just uploaded without problems. Also SpecialK isn't needed anymore (the "d3d9.dll" and "d3d9.ini" files).

      I have tested it in real time with the ingame interface. DoF and similar effects didn't seem to detect depth in the scene, but other effects were working fine.

  7. So i did this on thursday (before the march 16 update) and it didn't work. So ALL i have to do this time around is these instructions and it SHOULD work..?

    only doing this i mean:
    "- Get a recent PCSX2 build, equal or newer than "pcsx2-v1.5.0-dev-2324-g6aaae6970-windows-x86". Download links are here.
    - Configure the graphics plugin (GSdx) to use the DX11 hardware renderer.
    - For PCSX2 to be able to see the "d3d11.dll" of the fix on Windows 8.1 or higher, you need to apply this patch for the moment. If the bat file doesn't work, using the "sdbinst d3d11_fix.sdb" in CMD with admin rights may work.
    - Download the fix here and unzip its contents in your PCSX2 folder."

    ALL i need is these 4 steps to get sly 2 and 3 working in 3D..? or do i need anything else? i have no idea what this helix mod is btw, do i need to install this "helix mod" thing before i do the previous instructions..? and if yes, can someone please give me a link to the installation of helix mod?

    1. If you use Windows 10 with recent drivers, you just have to run that ".bat" file and unzip the contents of "PCSX2_3D_Vision_feature.7z" in the emulator folder. Then run a game using the DX11 hardware renderer. If it's Windows 7, the emulator may not trigger 3D Vision so you'll need a zip with two more files that I've included as a separate download ("d3d9.dll" and "d3d9.ini"). They complicate the game booting process, so let's hope you don't need them.

      Remember that I made the fix in the most general way possible. It's impossible to fix specific games (there could be exceptions) without breaking others, but I offer the tools and instructions to do it if you know what you have to sacrifice.

      By the way, "helixmod" is just the name of the blog, in honor to "Helix", the person that started the 3D fixing thing many years ago. If you have more problems after this, better post in this thread so I can follow comments more easily, because the blog doesn't notify me about comments:

    2. ahaa thanks a lottt man, i have windows 10 yeah. So i'll try it again on thursday and see if it works after the new update you released on 16 march. BTW, i'm playing sly 2 on it (or trying to make it work in 3D i should say)

  8. AMAZING !!! masterotaku is really a master :)

  9. Followed your instructions and got it to work with Windows 7, but couldn't get Windows 10 to work (will not switch in to 3d MOD with Win 10). Trying to play GOW 2. Have changed into full screen, I know 3d vision is working on my win10 system, but for whatever reason, it will not switch to 3d mode in Win 10. Looks awesome when it works in (win 7). Have the latest win 10 drivers. Installed the d3d11_fix_install.bat as an admin, but just can't get it to work.

  10. Greetings masterotaku! Good job!
    But! Unfortunately, I never managed to start 3D mode. Did everything according to your recommendations. Read here:

    Obviously, 3D Fix does not work in my case.
    WIN 10. is updated automatically. I use 3D TV PLAY and SONY HMZ T-3
     3D MIGOTO in other games is working!
    When the games are running in full screen mode - there is a green inscription. The pointer on the screen, also shows the included 3D mode. But! The image is absolutely flat. There is neither depth nor convergence.
    Please, Help! :-)

  11. ihunted 3 PS shader associated with HUD in Viewtiful Joe,i want to unstereoize shader,so i did this:
    all shader become 2D

  12. Hi. I'm brand new to this but I can't get this work. Do I need anything else besides the files you've provided here? I selected D3D11 Hardware renderer and the game loads but only on my normal monitor. Nothing changes in my rift at all.

  13. Also, I keep reading about something called 3D Vision. Is this something extra I need in order to get this plugin working with PCSX2? What exactly is 3D Vision?

    1. Julian, seriously? You can google about 3D Vision easily. You cannot miss it.

      You'll also note that nowhere on this page do we talk about Rift or Vive or anything having to do with VR. This is for stereoscopic 3D, not VR. You can possibly find something VR related on the pcsx2 site. IIRC they have some sort of VR mode.

    2. Thanks bo3, I wasn't sure what this website was really offering and didn't pay attention to the details so I completely missed the fact that it refers only to stereoscopic 3D. My bad.

    3. I understand how VR users are interested in this, because of the flexibility of disabling or fixing individual game effects and not needing any extra PCSX2 plugin.

      I found this ( to make the 3D Vision fix of Elder Scrolls Online work in VR. Maybe it's the method you need to make this work, Julian, because you can make my PCSX2 fix display in SBS.

  14. This is a bit of a long-shot, so before I ask anything but in any case thank you for your awesome contributions to 3D gaming and general understanding!

    I have an older laptop, with an nvs 3100m (nvidia quadro gt218 chipset 210/310M). My understanding is that somewhere in that chip is the 3D Vision functionality that I believe your pcsx2 plugin is using (and converting to sbs), as it can drive a 3D tv from hdmi using the 3DTV software. The laptop lcd however cannot handle 120hz...

    My goal is to have sbs output at 60hz on the laptop monitor while using your plugin to enable the 3D Vision 2SBS. Is this possible? When I try to use the plugin currently (win7, so I am using the specialk files as well as the dx11 dll/ini, and still configuring for DX11 in gsdx) I get the "WARNING: Profile update failed!" message in red and no 3D Mode appears to be enabled regardless of bringing up the gsdx config and then closing it and double clicking and using alt+enter (which just undoes what double clicking does to begin with) the so called "old method"... I think...

    It would be really great if I could use this instead of the 3d patched gsdx plugin I'm currently using, especially if the nvidia 3dvision2sbs is more efficient.

    Thanks in any case!

    1. It looks like it could be a decently long session of troubleshooting. Can you bring the conversation to this thread if my first suggestions don't work?:


      1- Run the emulator as administrator to apply the profile change.
      2- That GPU is very very old. I wouldn't be surprised if you need to play at native resolution most of the time.
      3- For SBS you have the instructions in this blog post, near the bottom. But first everything has to work correctly.

  15. This comment has been removed by the author.

  16. sorry to ask sir but how do you change the aspect ratio value? yours can adjust big/small but how to make it short/long. thanks again

    1. In "d3dx.ini", go to "[Key5]". See the "z = 0.75, 1, 1.333333" line? You can change those values to whatever you want.

  17. Thank you so much for this update! It is so great to be able to play PS2 games in 3D! And with the new fixes it's easier than ever! Thanks!

    I try to use this with Oculus Rift. I have no 3d Vision monitor, so I must activate "3D Vision Discover".
    I try to make it work in SBS Mode but I have a strange problem. SBS works, but the colors are all wrong. But it is not anaglyph colors.... What is causing that? Can 3d Fix manager be the problem? As there is no profile for pcsx2, maybe it interferes with the local fix? I just installed it for the first time. I tried to disable all fixes, and at some point yesterday it worked in correct colors in SBS, but today its not working again. I don't know how to fix it.

    In GTA V I have the same problem on Fullscreen with strange colors, but on "windowed Mode" it is ok.
    DO you have an idea what could be the problem? Will a screenshot help?

    1. Solution:

  18. ohh my god i can't believe this. PS2 games in 3D??? wow im so happy to be a 3d gamer and im so happy 3d communities are not giving up on 3d tech. Thank You so so much for all the hard work you guys!!