DXVK is a game changer in FNV

[Mak10z]

If you have a newer Videocard that supports Vulkan, I highly recommend installing the DXVK wrapper in to FNV. I went from 40-50fps in a heavy modded TTW + ENB install to a fully stable locked 60fps in all locations (that I have tested so far)


download the archive from here https://github.com/doitsujin/dxvk/releases
pull out the d3d9.dll and DXGI.dll and drop it in the root directory of Fallout New Vegas.
and go from there.

if you use enb, rename the new DLL to DXVK_d3d9.dll and edit your proxy settings as such

[PROXY]

EnableProxyLibrary=true
InitProxyFunctions=true
ProxyLibrary=dxvk_d3d9.dll

Edit: adding, found a fork of DXVK that uses async shader compiling, so its even better than before! :) https://github.com/Sporif/dxvk-async

[Lucifer69]

It's not more consistent. At all. It's actually less consistent due to all the micro stutter from converting shaders. Again, this depends on the CPU. My Ryzen/ Navi 2/ NVMe rig has no problems playing NV without any noticeable stutter on a vanilla setup. No need for this nonsense.

This biggest issue is anyone with a CPU or GPU that doesn't support Vulkan.

Finally, the author no longer maintains it so it will eventually become useless anyways if not already.

[Salamand3r-]

Originally posted by Lucifer69:

It's not more consistent. At all. It's actually less consistent due to all the micro stutter from converting shaders. Again, this depends on the CPU. My Ryzen/ Navi 2/ NVMe rig has no problems playing NV without any noticeable stutter on a vanilla setup. No need for this nonsense.

This biggest issue is anyone with a CPU or GPU that doesn't support Vulkan.

Finally, the author no longer maintains it so it will eventually become useless anyways if not already.

Eh? DXVK is an ongoing project, the author very much supports it - plus it's open source.

[Lucifer69]

The problem with open source is exactly that. It's open. Not that it's a bad thing, but the authors stands to gain nothing from it other than experience.

The original author has stated he no longer maintains it two years ago. This is confirmed by his orginal project being last updated two years ago. I think he released an async fork, but it hasn't received any subsequent updates, it's effectively the same thing even if it's "newer". There's a fork or two of it that apparently gets updates though there's also plenty of authors who just repackage the thing so... meh. The link above is one such repackage/ fork.

If it works for you cool, but because of the hardware limitations and the low probability of fixes, it really shouldn't be recommended to the average joe. This is because so few people have a basic understanding of hardware, let alone how software works. It also doesn't fix anything, it just seems to help some people get more stable frame rates (or so they claim).

Anyone on high end hardware doesn't need it at all nor will it yield any meaningful performance boost.

[Salamand3r-]

Originally posted by Lucifer69:

The problem with open source is exactly that. It's open. Not that it's a bad thing, but the authors stands to gain nothing from it other than experience.

The original author has stated he no longer maintains it two years ago. This is confirmed by his orginal project being last updated two years ago. I think he released an async fork, but it hasn't received any subsequent updates, it's effectively the same thing even if it's "newer". There's a fork or two of it that apparently gets updates though there's also plenty of authors who just repackage the thing so... meh. The link above is one such repackage/ fork.

If it works for you cool, but because of the hardware limitations and the low probability of fixes, it really shouldn't be recommended to the average joe. This is because so few people have a basic understanding of hardware, let alone how software works.

Anyone on high end hardware doesn't need it at all.

What? DXVK's development branch was updated hours ago, and usually a few times a day. The release version 1.9.2 was released in late September. Development is constant.

It's also a critical part of Steam's Linux initiative and a cornerstone of the upcoming Steam Deck. It's development is literally a very high priority for Valve - the entire success of the Steam Deck relies on it.

DXVK isn't going anywhere. I am not sure where you are getting your information from. If DXVK dies, Steamplay, the Steam Deck, and a whole bunch of Valve's nascent ecosystem dies with it. That's not going to happen with that kind of financial incentive behind it.

As to it's use on high end hardware - check my profile. Not running a potato. And I have a good understanding of hardware limitations and performance.

DXVK's FPS boost may not really be needed on higher end hardware, but the improvement to frame pacing is truly startling. Frametime consistency is a critical factor for perceived smoothness, and DXVK offers a very measurable improvement in that aspect.

Edit: You mentioned hardware support - that's another reason that DXVK will continue. DX9 is no longer actively supported - it's basically a legacy feature in drivers at this point, and it's not always well optimized. It's only a matter of time before DX9 joins earlier versions in purely emulated support on modern hardware. We've seen with older DX versions how that often totally breaks games or degrades performance. That's why wrappers like dgVoodoo2 even exist, and why DXVK is great for older games now, and will become critical in the future.

[Egil841]

Last time I used this I got glitchy-ass textures for my water resources, any work arounds?