Thursday, May 26, 2022

Final Fantasy XV









3D Vision fix for Final Fantasy XV. Made by DJ-RK and masterotaku equally. I have tested the game mostly with the "Assets" option enabled.

Update (2022-06-26): added geo-11 fix, which performs a lot better than in 3D Vision. It has autoconvergence, and some hotkeys differences.
Important update (2022-05-27): improved screen space reflections fixes to stereoize the fade area. Volumetric lighting fixed the correct way instead of being sticky. Lighting clipping fully fixed, except the one related to shift+F5 and some created by ambient occlusion (not VXAO). TAA fixed for the most part. Motion blur fixed alongside it. Some small lighting issues are fixed now. Some performance improvements. Fixed some mistakes in the fix. Changed "d3d11.dll" to one that triggers 3D in borderless mode too.

Small update (2020-04-18): fixed the blizzaga spell.


Fixed
- Skybox.
- Light shafts.
- Shadows.
- Lighting.
- Decals.
- Ambient occlusion and VXAO.
- Nvidia ShadowLibs.
- Screen space reflections and their fade affect at the sides.
- Some effects related to water that needed stereoization or the opposite.
- Volumetric lighting and fog.
- Smoke/fire/particles that were appearing only on one eye.
- Stereoized specular reflections.
- Distortion effect when hitting enemies, when explosions happen, etc (radial blur).
- The bonfire when the high quality "Assets" aren't enabled in the options.
- Lighting clipping, except the big blocky clipping that can be disabled with shift+F5 at the cost of extra GPU usage.
- Temporal anti-aliasing (TAA). For the most part (you may notice it being a bit wrong on the ground if you spin the camera very fast).
- Motion blur.


Not fixed settings
- DLSS: it doesn't work in 3D.


Known issues
- Lighting clipping in a specific compute shader isn't fixed the proper way (it happens mostly on the left eye), but the "shift+F5" hotkey can be used to fix it with a brute force solution that will increase GPU usage by a variable amount. It can be anywhere from 5% to 50% depending on the situation. Consider using this if you have a lot of GPU performance to spare.
- There is something minor about water (unrelated to the screen space reflections) that isn't handled correctly when you use Nvidia Ansel to tilt the camera. And this effect doesn't always appear. Edit: not sure if this still happens.
- Ambient occlusion (not the VXAO one) have some temporal frame blending effect that doesn't look right in 3D when you move around.


Installation
geo-11 (new, recommended, using build v0.6.6): download this file and extract its contents in the "FINAL FANTASY XV" folder, where "ffxv_s.exe" is. Remember to edit "d3dxdm.ini" to change your "direct_mode" to the output you need.
- 3D Vision (older): download this file and extract its contents in the "FINAL FANTASY XV" folder, where "ffxv_s.exe" is.
- Launch the game and let it overwrite the profile when it asks for permissions.
- Play in either fullscreen or borderless modes.


(3D Vision) Recommendations for better fps in CPU limited situations
This game is very CPU demanding. You will get around 1/3 of the fps you get in 2D in CPU limited situations. If you play at maximum settings (except for TurfEffects), you can expect being under 30fps the majority of the time with current CPUs. If you follow these recommendations (from highest to lowest importance, in this order, with VXAO and LOD being similarly demanding), you can get noticeably better fps:

- Nvidia TurfEffects: don't use it. Way too demanding for the CPU, an order of magnitude more demanding than anything else combined. I'm talking about 10fps with an i7 7700K at 4.9GHz. It's also desynchronized between the eyes when you step on grass.
- VXAO: it's the best looking ambient occlusion option in the game (don't use it at the same time as the other options), but it also increases CPU usage as well as GPU usage.
- Model LOD: don't set it to the highest option. I recommend the medium option, which has little difference in fps compared to low, but it looks considerably better.
- Lighting: in some situations, the highest setting hits the CPU a bit, compared to the high setting.


(geo-11) Recommendations for better fps in CPU limited situations
Thanks to the increased CPU performance of geo-11 compared to 3D Vision, the settings mentioned above don't have such a drastic effect. VXAO is probably the most CPU demanding setting now, but also the only good ambient occlusion option. You decide if it's worth it.


Hotkeys
- Shift+F1: this toggles the OSD that shows the available hotkeys.
- F2: convergence presets (0, 0.333333, 0.666667, 1, 1.5, 2). 2 by default. Use shift+F2 to cycle backwards. In geo-11, if autoconvergence is enabled these hotkeys won't work.
F3: HUD depth presets. 75% depth by default. The crosshair in the Prompto DLC is always at 90% depth. Use shift+F3 to cycle backwards.
Shift+F4: HUD toggle. Not disabled by default.
- (3D Vision) Shift+F5 or XB_LEFT_THUMB+XB_RIGHT_THUMB: lighting clipping toggle, for a brute force fix. Not fixed by default. Explained in the known issues section. For geo-11, copy the "clipping disabled\cf840a23ccd8a972-cs.txt" file to "ShaderFixesDM". To enable it back, copy the "clipping enabled\cf840a23ccd8a972-cs.txt" file instead.
- (3D Vision) Shift+F6: depth of field toggle. Not disabled by default.
(geo-11) Shift+F8: depth of field toggle. Not disabled by default.
F10: this saves your hotkeys state, so you don't have to press them in future sessions.
- Ctrl+alt+F10: this resets your hotkeys state file, discarding your custom settings.


Autoconvergence (geo-11)
- In the geo-11 fix, autoconvergence is enabled by default, which in my opinion handles all situations very well. If you want to disable it, open "d3dx.ini" and set "dm_auto_convergence" to 0.
- It mainly only works at 100% resolution scale, and sometimes at 50% and 75% if you launched the game with the setting already being at that value.


Notes
If you have been using an older version of the fix, uninstall it completely. Don't just overwrite the files.


Donations links
- DJ-RK: like my work and wish to show appreciation? Dontations can be sent by visiting: https://www.paypal.me/DShanz or by sending to rshannonca@gmail.com
- masterotaku: if you liked the fix and want to contribute for more future fixes, you can donate to this PayPal account: masterotakusuko@gmail.com

25 comments:

  1. If i knew you were working on this, i would have waited to play the game. Now i'm through with it :-) Thank you anyway for your great work!

    ReplyDelete
  2. Does it work also with the Windows Edition ?

    ReplyDelete
    Replies
    1. Do you mean the Windows Store? Unlikely to work well there, Microsoft Store has weird restrictions and cause some driver level workarounds to not function properly. Maybe DJ-RK has tested that version though.

      Delete
    2. The version on Steam is literally called "Final Fantasy XV: Windows Edition" so I was referring to that, but you are correct that it exists on the MS Store (and is rumored to not be plagued by the same stuttering issue that exists in the Steam version since update 1.26), which I'm not certain if that can be modified.

      Delete
  3. The download link seems to be broken. It is not a browser or firewall issue on my end. Strangely the game/mod does not show up in 3d fix manager either. I was waiting optimistically for someone to mod this for 3d before buying.

    ReplyDelete
    Replies
    1. Works fine here. Location: California, US.

      It would help if you tell us what the error actually says.

      Delete
    2. Yeah that was my fault, sorry. It was a "the page cannot be displayed thing". I had turned off my antivirus and firewall to test it on a couple of devices but didn't realize that my newest access point had activated a free trial of a firewall which blocks things without alerting me that it has done so. Every other security software I've used gives a warning or some kind so I thought the site must be down. Apparently the whole MasterOtaku website was flagged.

      Anyway FF15 and Resident Evil 3 both don't show up in 3d fix manager yet. It's hardly a hassle to add them manually but they should be listed to help people discover this excellent work.

      Delete
  4. I'd suggest that you wait on playing RE3 for a day or so. I made some additions to masterotaku's already great work, most notably I got DarkStarSword's autoconvergence shader hooked up, which makes cutscenes really pop! masterotaku already has my update, and will probably upload it later today or at his earliest convenience.

    ReplyDelete
    Replies
    1. I would but, y'know, social distancing and all. :P

      Delete
  5. Question about a recurring graphical artifact. I'm running a water and fan cooled 1080Ti and overclocked i7-8700K 3.7Ghz on a 4k LG OLED 65E6V TV. Updated windows 10. Updated Graphics card drivers but with 3d vision maintained through 3d fix manager wizardry. For passive 3d I have to display 4K. FF15's in game render resolution only allows you to go down to 50% of displayed resolution (2K). Enabling 3DMigato upscaling from within 3d fix manager prevents the game from launching successfully. I have read that 3DMigato upscaling doesn't always play nice with games that have their own upscaling setting. Looked into DSR but seemingly same issue. So I am stuck rendering 2K currently.
    Other than the recommendations about LOD and NVIDEA features in the main post, no other graphics settings significantly effect fps and fps is generally in the 30s range. It is playable to me, but what is annoying is artifacts around some reflective or light emitting objects in game, such as billboards. Rectangles within the field of view that are out of sync with/less bright that the rest of the image, flitting in and out of existence when the camera moves. Has a matrix vibe. I thought it might be from tearing due to the camera movement so I tried locking fps at 30 in the settings and playing with VSYNC settings but no go. Fullscreen vs boarder-less does not help. My GPU is being pushed to nearly 100% and if I turn up other graphics settings such as LOD or turn on VXAO, in addition to the frame rate trending a bit lower, the artifacts occur on many more in game bright moving objects especially hair and clothes. So it seems like the core problem is that the 1080ti is being pushed too hard and my experience with other games makes me think that rendering in 1080 HD would solve the problem. Control with max stats rendered in 1080 HD played in 4K 3D got pretty steady fps in the high 40s to low 50s with no artifacts with this setup. Some extra info: The connection between video card and TV is a good quality HDMI 2.0 of minimal length. I output sound through a separate cable and port on the video card to free up bandwidth on the main HDMI which actually improves my fps noticeably in Control (maybe partly because it's surround sound). CPU usage is not near being maxed out. Turning off HDR increase frame rate to 50s and gets rid of the previous artifacts but makes all shiny objects flicker. Turning hyperthreading from auto to enabled in BIOS frees up some more GPU and makes the light effects gorgeous but heavily taxes the CUP and results in everything the tiniest bit shiny flickering/twinkling. Prompto's hair is the worst culprit and flickers like glitter in a disco in this scenario. The CPU also sounds like it is trying to escape the case in this scenario and retaliates against the abuse by somehow irreversibly disabling HDR in windows whenever hyperthreading is enabled but that's it's own problem. Any ideas on how to lower the render resolution in ff15 beyond the limitations of the in game setting? Hopefully there is a simple solution that I am ignorant of as I am still learning a lot about setting up 3d 4K gaming.
    And I know that the real solution is to buy a 2080Ti and enable DLSS for a physics defying fps boost in ff15 but I don't have the funds just yet. Heh. Any short term suggestions?
    Thanks!

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

    ReplyDelete
  7. Hi there, i have strange performance issues with this game, it looks like 1 core is bottlenecking everything when i'm in 3d, so basically i get 95fps with 3d disabled and if i activate it i go to 25 fps and gpu barely reaches 40%, if i disable HUD i get around 8 fps increasek, tried shift F5 for clipping workaround but nothing changes (and also i have only 2 options, not 3 as described). I'm on win10 1809(ltsc), 7700k at 4.9Ghz, rtx2080super, drivers 441.87(first available with rtx support), tried with both 3dmigoto 1.16 and 1.16.41, no difference. Any clue please? it looks the wrapper is taking too much cpu. Tried max settings and min settings ingame, no difference at all, same bottlenech, gpu at 40% and 25/30fps. i'm using 3dfix manager, thanks

    ReplyDelete
    Replies
    1. nevermind tried on the other no-3d partition too and while it performs a bit better it's still severely bottlenecked by CPU, as i hate playing with low fps (expecilally in 3d) i'll try again after the next cpu upgrade :)

      Delete
    2. Game might work better on the new geo 11 drivers since they don't have the 3 core cpu bug.

      Delete
  8. At 1440p in 3D Vision, I went from about 11 fps without geo-11 to nearly 46fps with it. Phenomenal.

    The only problem I see is with the HUD which seems like it's convergence is messed up.

    ReplyDelete
  9. Thanks for the this fix! Does anyone know why it says 60 Herts isn't compatible with 3d on start up? I even went to the ini to out force 24 herts

    ReplyDelete
  10. is the geo-11 version not supporting Big Screen VR? the game runs fine on normal mode (with the fix inside the game folder), but in Big Screen, it crashed on startup showing: Entry Point Not Found CreateDirect3D11SurfaceFramDXGISurface could not be located in the dynamic link library C:\Windows\System32\Winodws.Mirage.dll.

    ReplyDelete
  11. update, after this warning, it went on to except access violation, then crash. Final Fantasy 7 remake also has the entry point not found error, but the game starts.

    ReplyDelete
  12. guess there's no fixing the entry point not found thing. anyway, tried the geo-11 in 3D Surround. FPS indeed improves a lot, but have to disable auto convergence (d3dxdm.ini) cause even during normal gameplay, the convergence constantly auto corrected~~

    ReplyDelete
  13. Quest 2 Bigscreen VR runs ok, HP Reverb G2 having the entry point error. guess it's fine with Oculus but not with WMR. however, just personally Quest 2 doesn't give me pleasant gaming experience. too bad~

    ReplyDelete
  14. WOW!! I just tried this on my Meta Quest 2, using Virtual Desktop and geo-11, and it looks amazing. 3D adds so much to the experience, thank you! Installing geo-11 was as easy as drag and drop.

    Two notes:
    1. Shift-F1 OSD only shows a yellow "F" onscreen, instead of the shortcuts.
    2. I had to lower the depth in the d3dxdm.ini file to half (dm_separation = 50) . Leaving it at 100 made me cross-eyed. 50 made it comfortable, but this is personal preference.

    ReplyDelete
  15. is there a way in geo-11 sbs to cycle frustrum like in 3dvision.

    This game i think has a lot of culling at the edges of the screen. GEO11 runs way better, but I can't figure out how to cycle frustrum like i used to with 3d vision monitor.

    ReplyDelete