Sunday, November 11, 2018

Dead Rising 3





3D Vision fix for Dead Rising 3.


Fixed
- All haloing problems.
- Shadows and lighting at all resolutions and settings.
- Light shafts.
- Lens flares at geometry surface depth.
- Sun in the sky.
- Dynamic HUD depth, and HUD toggle. With tweakable number of samples for more or less accuracy at the cost of GPU performance.
- Automatic convergence preset, triggered for gameplay. By default cutscenes are at low (0.5) convergence with non dynamic HUD, and gameplay has 1.2 convergence and dynamic HUD. If you want to modify or disable this, open "d3dx.ini" and go to the "[PresetGameplay]" block.
- Optional windows reflections at more depth with the "n" key. They may not always look right.


Known issues
- There is some lighting clipping at very long distances.
- There is some geometry culling that doesn't happen in 2D, especially noticeable in open areas. The "m" hotkey fixes this, but at a moderate-high CPU performance cost.


Installation
- Download this file and extract its contents in the "deadrising3" folder, where "deadrising3.exe" is.
- Right click "deadrising3.exe", go to the "Compatibility" tab and check the "Disable fullscreen optimizations" and "Run as administrator" options.
- Launch the game and let it overwrite the profile.
- If you ever see strange issues in the title screen or after loading your save (elements at screen depth that shouldn't be there), reboot the game or maybe consider going to the "C:\Users\XXXX\AppData\Local\Temp\NVIDIA Corporation\NV_Cache" folder and deleting everything inside.


Hotkeys
p: convergence presets (0, 0.5, 0.8, 1, 1.20, 1.5, 2, 2.5, 3).
h: HUD toggle. Not disabled by default.
k: dynamic HUD depth toggle. Disabled by default, but the automatic convergence preset enables it when needed. Unfortunately, this is triggered in the skills menu screen, which will look bad until you press this key.
j: dynamic HUD samples presets (70, 100, 200, 300, 400, 500). More samples mean more accuracy and smoother steps, but also more GPU usage. By default it's 200. Crosshair textures always use double than the set value.
m: this fixes the culling issue but at a high CPU performance cost. An Intel 7700K at 4.9GHz gets 22-32fps in very crowded areas, while it gets 32-40fps without this hotkey. Not used by default.
- n: this puts windows reflections at more depth, giving them a more realistic look. But it can be a bit buggy in some situations, so that's why it isn't used by default.
b: screen depth blood effect toggle (disabling the HUD also disables this). Not disabled by default.


If you liked the fix and want to contribute for more future fixes, you can donate to this PayPal account: masterotakusuko@gmail.com

17 comments:

  1. Awesome work Masterotaku :)
    Always liked the Dead Rising serie`s
    Again can`t say enough thanks for all the hard work

    ReplyDelete
  2. This comment has been removed by the author.

    ReplyDelete
    Replies
    1. This is an amazingly solid fix and I use it to play the game on my custom VR Headset. Outstanding work !

      Delete
  3. This comment has been removed by the author.

    ReplyDelete

  4. Thanks for your hard work. Sadly no resolution in this game for my projector. 1024*768
    :

    ReplyDelete
    Replies
    1. Just tried a few possible workarounds, like forcing the resolution with 3Dmigoto, but it seems like the game won't run at anything less than 720p. Resolution is right, but game gets into a strange stutter mode, not playable.

      Experiment with your projector, and see if you can enable a higher resolution of some form.

      Also, try creating a custom resolution for your projector using NVidia Control Panel under Change Resolution. You can set a custom resolution that the game sees, but winds up being the 1024x768 your projector wants. You Create Custom Resolution by setting the timing to Manual, then set the Display Mode at the top to something that DeadRising3 can produce. Keep same aspect ratio, so maybe 1280x960 would be good.

      I do that all the time for my 720p projector, having made a custom resolution of 1600x900 that runs at 120Hz. Games think they are drawing to 1600x900, but the video card puts out the normal 720p@120Hz.

      Delete
    2. Also, you should be able to use DSR feature to create an in-game resolution that is higher than the projector, so game won't freak out, and you still get 1024x768 that the projector wants to see. (Under Manage 3D Settings)

      Delete
  5. Bo3b. Thanks for your detailed response.
    I will try the DSR option... custom resolution prevent enabling 3d.. only 1024*768. The projector can do better but i had to use edid overide to make 3d vision work.. with Acer driver.

    ReplyDelete
  6. Hmm, weird. When the fix is installed, the game doesn't see my controllers, ps4, nor 360 wired. No issue in 2D. Any Ideas? Steam version.

    ReplyDelete
    Replies
    1. As a datapoint, I just tried the XBox One wireless controller, and it was working fine in this game. 360 wired should be simpler and easier setup.

      Might try updating the 3Dmigoto files to latest version, because there is added support for Steam controllers. Might or might not be related, but latest version allows better Steam overlay compatibility.

      Delete
    2. Also have a strange MadCatz wired controller here, and I plugged that in (USB), and it also worked here in DR3. Not exactly the same, but there can't be too much difference between this one and real 360 wired.

      Delete
    3. Thank you for your response and testing. You are above and beyond the call. I'd tried this six ways from Sunday (new/old versions of 3DMigoto, installing the fix with Fix Manager and installing without, DS4 controller, 360 wired, xbone wireless etc etc). What finally worked in this case was force disabling all controllers for this game via Steam Big Picture and allowing DS4Windows to handle the PS4 controller. I presume x360ce or similar would work too. No idea why it's happening here and not there, or why it's only when the fix is installed. I don't have DS4Windows set to run automatically, so there shouldn't be any conflicts there. Ah well, it's working.

      Delete
    4. This comment has been removed by the author.

      Delete
    5. This comment has been removed by the author.

      Delete
    6. This comment has been removed by the author.

      Delete
  7. OK I finally tracked down the culprit; I should have suspected sooner...I had to disable Steam overlay for this game. I rarely have any issue with it these days, but it caused a conflict with my controllers. Maybe it's the version I'm playing, I dunno. Got it in the last few months.

    ReplyDelete
  8. Hey! Thank you very much for hudtoggle. I faced with the flickering screen issue, is it possible to fix?

    ReplyDelete