Longcrossing

With absolutely no disrespect or snarky-ness intended to any poster on this sub issue: The idea is interesting but... I, for one, hope the Developers do not put any time or energy into it for the time being. Many of us are just holding on for 64 bit NMM/MO+ for all the previously stated reasons. Coding algorithms that could cope with an export/import process of what every single Nexus user could potentially put together for all Nexus mods for all the games Nexus handles, install them in the correct sequence and then in some cases move the mod to a different position in the load order and then deal correctly with all the error conditions that result sounds something like playing chess with a stadium full of opponents and covering every single possibility with each of them 512 chess moves out. That isn't even taking into account users with mod merges in their setup and mods that were on Nexus but have since been removed and every potential version of a given mod in the user's mod list. Please, don't get sidetracked, and just give us the new NMM/MO for now?

I too have much respect for Tannin and his work and, in fact, am still overjoyed that he is working on this new version of nexus mod managing software. BUT, the name option NMO was vetoed by the site owner a long time ago. I personally like Vortex (suggested some time back). The alliterative nature of Nexus Vortex works. Someone also suggested NUMI a while back. It's good too. Some other suggestions (truly very plain but they would get the job done): NMT - Nexus Mod Tool NMH - Nexus Mod Handler NMC - Nexus Mod Coordinator NMW - Nexus Mod Wrangler (yes it's dopey but gets across the "herding cats" nature of trying to get mods to play nice together.) Admittedly, these are all just synonyms But this IS Nexus, it DOES work with Mods and IS meant to manage. Clearly, this project is an altogether new product and therefore keeping the name NMM would only cause confusion as some users will stay with the old NMM and not update...

Thanks @Darth Ligerius ! You gave me the right clue to fix this on my setup. I recently tested out 20 or so different ENB / Reshaders for FO4, part of this testing involved upgrading the ENBoost setup on one of the contenders from ENB .283 to ENB .291. I just changed it back from newer to older and voila! my texture detail has returned! Cheers <update> oops, I was hasty in my conclusion. It was the change that fixed the textures but I focused on the wrong aspect. It was NOT due to the ENB version but the settings within my enblocal.ini file. I previously raised the setting VideoMemorySizeMb too high (after apparently being mislead by the VRAM test process). Anyway, when I dropped my VideoMemorySizeMb setting back to the original value I'd manually calculated, textures looked great again. NOTE that the bad LOD, for me was in most metals, like the details on the power armor frame for example. Also, while my rig is not astounding, it is reasonably good. Recent 2GB nVidia card, etc... That did it for me (after hours of searching/testing), hopefully the info will be of help others...

Thank You, Thank You, Thank You! I was having the same exact problem right at the end of Lonesome Road. Very frustrating (my first play through). I used Nexus Mod Manager to deactivate Nevada Skies, ran LOOT and Voila! LR completed perfectly! Best Regards, Longcrossing