jammerjim

Gave up trying to figure out the conflict and generated my own LOD. Annoying, but not actually that hard.

Gave up trying to figure out the conflict and generated my own LOD. Annoying, but not actually that hard.

I have confirmed it has something to do with the LOD file Borealis says to use with BNS. I disable the LOD file, and my roads return to normal. Still no idea what it is interacting with to cause this, but one thing at a time.

So, my elevated freeways look weird until I get close (see attached). I don't know if I have fighting textures (lots of texture mods, some overlap) or there is something goofy with the LOD. It's early in my playthough, I've just messed around Concord, and as far as I can tell, only the elevated roads are goofy like this. Any ideas? I've never tried creating my own LODS, but then again, I don't know if LOD is the issue. Maybe an ini setting? Load order attached, but I'm using Borealis + BNS- Trees only, and the LOD that comes for that combination, as well as Vivid Weathers. I put in FAR recently, but that didn't help.

I'm gonna necro this thread because I had pretty much the same issue as described in it, which was driving me crazy. I was lucky to find another thread that described the issue differently but also had a solution that worked for me. Also because STEP does not say a word about this possible problem if you follow it's suggested settings. This probably only affects Nvidia cards. The fix: If it's off, turn bBlurEnable back on. From the other thread: "The solution was the NVHBAO settings in Falloutprefs.ini. Although the NVHBAO settings are for distant AO, on the advice from STEP pages, I had switched off the bBlurEnable. They thought it unnecessary, freeing you to tinker with sharpness. Bad move - that is the setting that brought out the "pixel grid" effect." You can find the thread here.

With respect, I feel the need to point out that these conflicts can show up in the strangest of ways. In my case it was the interaction of Immersive Weapons, some of its patches, Bijin, and a bashed patch, which brown-faced Aela and some other of the Companions. IW carried some info on Aela into it, and the bashed patch had the info from the compatibility patches, and IT loaded after Bijin AIO. I was able to fix it by making a Vortex rule to force IW to load before Bijin AIO in the mod list (I already had Bijin next to last in the plugins). That sorted my bashed patch. I would never have thought of that combo. It took a look in SSEEdit to figure it out.

Thanks for the response. I think I would like better resolution if on a 27" screen (2560x1440 instead of my current 1920x1080), but I'd have to see it in action to say for sure. My eyes are not what they used to be, so it's possible the extra pixels would be wasted on me. You may also be right about the 660 handling F4 okay. It handled Witcher 3 way better than I thought possible (I never turned on the hair thing).

So, I'm currently running a Geoforce 660ti on a 24" monitor. I'm thinking its time to upgrade. I'm considering some flavor of the 900-series, but complicating that, I'm also considering a larger monitor (27"). I'm not as plugged in as I used to be, so I'm unsure what I to do. I'd like to keep the card under $400, especially if I want to spend to increase screen size, but something that can handle my current set-up might not handle more real-estate. Or maybe I should wait X months for the new tech to come out, either for a new generation of card or cheaper old ones. And of course, I want o be able to play Fallout 4 and some of the new games on, if not ultra, then at least high. I generally prefer single-card solutions. My CPU is an i7-3820, 3.6GHz.