If this is the same issue as in New Vegas then it is technically a game bug that i have also reproduced on native Windows AMD in the past. Nvidia works around it with a game profile.

@K0bin As a reminder https://github.com/doitsujin/dxvk/issues/2319#issuecomment-1283072644

I've been noticing this issue as well.

I fixed the decal issue talked about here, some time ago, as it was occurring in D3D9 on Intel and AMD.

This one however is new and seems to stem from normal object shaders.

Still getting a very similar issue with bright, blurry dots / bright lines in distant LOD (in Nuclear Sunset modlist for TTW mind you-- in Capital Wasteland) on DXVK 3.0.1. Issue isn't present in 2.7.1.

AMD Radeon RX 6600
Driver Version: 26.6.2

If it's somewhat easy to reproduce can you make a apitrace of where it usually occurs?

I have made the apitrace. Whatever is happening with LOD should be present later in. I loaded into the game save from the first screenshot, used TCL to go towards and away from the LOD issue shown in that screenshot, and then ALT + F4'd out of the game after about 15 seconds of doing that. The issue wasn't present during the apitrace (which I read is normal when trying to reproduce the issue with the new d3d9, etc). Here is the apitrace:

https://mega.nz/file/lv01iBTI#tKAigDjKByUdWaBbFN6pIvLplm7AEI7zHDM-m68kuic

For further information, I am using the Nuclear Sunset modlist for TTW with the Hikikomori Performance preset. This also seems to be occurring with only a few structures in the game, and only in their distant LOD form, this is one of those structures:

I have told the developers of the modlist about the issue as well. It does not occur on DXVK 2.7.1 and before, and so does not appear to be a problem with the mods themselves.

Can't even debug this properly because AMD's driver just crashes as soon as I try to look into this further.

Just throw d3d9.floatEmulation=Strict at it and move on I guess.

I've had d3d9.floatEmulation set to Strict for some time, because of another interesting bug in Nuclear Sunset with rain looking like this:

But this issue with some distant LOD being really bright spots still happens with that set to Strict.

Please also make an apitrace of the rain.

I haven't personally been able to get this to happen again since when I first set floatEmulation to Strict, and even when floatEmulation had been set to Auto, I only saw this once across maybe ~20+ hours IGT on the modlist. I'll try to the next time it crops up though.

I've had d3d9.floatEmulation set to Strict for some time, because of another interesting bug in Nuclear Sunset with rain looking like this:

Please post a log to confirm that it actually applies, because it just doesn't reproduce with Strict here (but does with True even on RADV, so I guess that makes it more debuggable).

I swear to god 90% of the post-3.0 work has been wasting time on broken Windows drivers.

If you can point me to what sort of log I need to produce, I can do that now. Sorry, not at all knowledgeable with this stuff.

There should be a FalloutNV_d3d9.log (or whatever the game exe is called) somewhere (usually next to the game exe itself).

I checked the effective configuration in there and realised that the freaking d3d9.floatEmulation = Strict has been commented out the entire goddamn time in dxvk.conf... Everything normal in game with that now active. Apologies for wasting your time here.

Yeah I'm thinking I'm probably gonna stay away from AMD for my next PC upgrade...