Saturday, January 6, 2018

Dead Rising

3D Vision fix for Dead Rising.

Update (2018-01-06): new version with 3Dmigoto 1.2.67. Fixed lights that were in 2D before, new hotkey, and changed the default state of some effects to leave the game in the original state by default.

- Fire heatwave effect that can be seen at least near the start of the game.
- Stereoized and fixed mirror reflections that were flat.
- Stereoized lamp lights that were 2D.
- Stereoized some HUD elements that were flat.
- Lens flares are now at a fixed depth.

Known issues
- The game can be unstable and crash randomly because of the stereoization of some elements (render targets, like the 3D HUD, some mirror reflections, and lamp lights), at least in my experience. To disable that, remove or comment (using ";") all sections and content below that start with "[TextureOverride".

- Download this file and extract its contents in the root folder of the game, using 7-zip.
- Launch the game, but on Windows 10 you may need to quickly press alt+enter right after the game window appears, to avoid a crash. The game will be then in windowed mode. Press alt+enter again to enable fullscreen and 3D will start working. The game will probably crash if you alt+tab after that.
- On Windows 7, you may need to open "d3dx.ini" and change "allow_platform_update=0" to "allow_platform_update=1".

- F2 or left stick click: convergence presets.
- F3 or right stick click: HUD depth presets. Screen depth by default.
- F3: bloom toggle. Not disabled by default.
- F4: depth of field and vignette toggle. Not disabled by default.
- F5:lamp lights toggle. Not disabled by default.
- Q or right trigger: 90% HUD depth at the center of the screen, meant for crosshairs and the camera objective.
- Tab or d-pad left (holding): low convergence to see the wrist watch.

- I haven't finished the game yet. If I play it to the end and find more fixable issues, I'll update the fix.

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


  1. Does this fix work when playing in 2D only? Depth of field toggle is appealing to me. Can hotkeys also be changed?

    1. Yes, it works for 2D too and you can also change the hotkeys. First of all, open the "d3dx.ini" file.

      Go to the "[Constants]" section and in this case you will see the "x", "y", "z" and "w" variables and their default value. To enable by default the lights I disabled, use "z=0" instead of "z=1". In this case it will make the F5 hotkey useless.

      If you want to change the hotkeys, go to line 133, where "[Key1]" starts. There you can change keys and values, and also what variables they change (in this fix I didn't comment what everything does in that file). You shouldn't need to change hotkeys other than F4 and F5. The others only change things visually if you play in 3D.

  2. how do you find these post process effects and disable them?

    1. It's usually easy. When I hunt shaders with the numpad keys ("hunting=1" or "hunting=2" in the "d3dx.ini" file), the effect that the program selects gets disabled. I just cycle through the available pixel shaders until the depth of field effect disappears (or any other effect I want to remove). After that, I dump the shader and make a condition to disable/enable it with a hotkey.

      Sometimes, if the shader code is easy enough to understand I make extra options inside it, like the depth of field strength in Yooka-Laylee, or the FXAA edge detection value in Dark Souls 2 SOTFS (which was too blurry by default).

      It would be better if developers offered all of that as ingame options, but when they don't, I try to do it myself. A cool example is The Evil Within, where a shader mod I made is the only known way to disable depth of field (you can find my files in the forums (, because I didn't do the fix).

  3. This comment has been removed by the author.

  4. Just tried this again, and it seems to be working pretty well. Win7, Driver 385.69. I used 3D Fix Manager to install fix, and update to 1.3.8 version of 3Dmigoto. No crashes in about 30m of play.

  5. Didn't work. All it did was crash the game on startup.

    1. Just tested this again, and it was working fine here. Win10 21H1, Driver 516.59, using geo-11 with nvidia_dx9 output mode. Steam version of game.

    2. maybe it has something to do with my resolution? It's 4k