Nightstrom Posted June 3, 2020 Author Share Posted June 3, 2020 No changes... If a clean Windows and game install, along with the latest drivers doesn't fix this I don't know what will. I'm using IMPACT by the way, tweaked the INI files as told. Link to comment Share on other sites More sharing options...
dubiousintent Posted June 4, 2020 Share Posted June 4, 2020 (edited) Suspect this, like Z-fighting, is something you will just have to live with until the correct underlying terminology is identified so it can be researched for a solution. Otherwise, Radioactivelad's comment seems like your only clue to date. Let us know if you do manage to resolve it. -Dubious- Edited June 4, 2020 by dubiousintent Link to comment Share on other sites More sharing options...
Nightstrom Posted June 4, 2020 Author Share Posted June 4, 2020 Was reading old threads and someone suggest disabling in game AA and force it through Nvidia/AMD apps. I couldn't get it done though, even if I set it to "override game settings" AA wasn't active. Link to comment Share on other sites More sharing options...
Radioactivelad Posted June 4, 2020 Share Posted June 4, 2020 Forcing AA through the CP in FO3/NV isn't really recommended anyway, since it doesn't work properly with certain elements, notably the pip-boy interface. You might try changing Anti-aliasing Compatibility settings with Nvidia Inspector, though it might cause more problems than it potentially solves. NV by default does not use the same flag as FO3 and Oblivion for whatever reason, so you could try changing it to that and see if it fixes it. I know AA compatibility settings resolved a possibly related issue with anti-aliasing in Morrowind. Link to comment Share on other sites More sharing options...
Nightstrom Posted June 5, 2020 Author Share Posted June 5, 2020 I'm using an AMD card unfortunately. I guess I'll have to play without bullet wounds from now on. Link to comment Share on other sites More sharing options...
Recommended Posts