Community Continuity of mod manager severely lacking

[springfield1191a1]

I am writing this to let the entire community know that the community continuity version of the NMM is floating dangerously into the "unusable and unstable" range. I have gotten 2 different and excessively recurring errors in the 0.63.13 version. the first is a 7zip sharp error and the second is a "used by another process" error. Both of these occur for EVERY SINGLE MOD THAT I TRY TO INSTALL. I'm sorry to the makers of the mod manager but you need to either pick the NMM back up and stop this end-of-line crap, or hustle out with your new mod manager. Common sense does dictate that when producing a new version of software, one does not stop support for the old version until AFTER they have released a stable, easily supported version of the new. As a modder that has little to no understanding of the source code for the mod manager and lots of experience in placement of mods for older games such as F3 and FNV without the use of a manager, I have become over reliant on your mod manager to the point of not really understanding Fallout 4's system of mod placement and load order. While seemingly the same there is a significant difference from previous Fallout games and not having a usable mod manager is detrimental to the modding community here on the Nexus. I hate Bethesda.net modding. It sucks. I'll be willing to Alpha test or Beta test whatever build of the new mod manager you have right now. Seriously you guys at the nexus need to provide bugfix advice or actually make bugfixes for these issues. If this continues on, chances are that the nexus mod community will probably dry up. Guys, i'm serious about this. Don't roll over and take Bethesda's crap. Fight to the last breath to preserve the illustrious community that you have built here. A perfect way to start is to pick the old nexus mod manager back up with bug fixes until you can release your new one. please don't make your community beg for bugfixes as i'm practically doing right now. thank you for your time and patience with my ranting, raving, complaining and whining.

[damanding]

I suggest either switching to a somewhat older, more stable version of NMM or switching to Mod Organizer 2 which has recently started receiving support again with a new developer.

0.61.21 is a decent stable version: https://github.com/Nexus-Mods/Nexus-Mod-Manager/releases

Mod Organizer 2: http://www.nexusmods.com/skyrimspecialedition/mods/6194/?

Mod Organizer 2 is pretty stable and works well, it's what I use. The only issues Mod Organizer has is that it is a little more prone to crash when using external apps like FO4Edit, LOOT, and the Creation Kit. Thankfully though it's more annoying than showstopping. The crashing usually happens when exiting one of those programs and thankfully the crashing seems to happen after whatever changes you made were saved. Even more thankfully, since Le Presidente took over development the exit crashing with other apps has significantly reduced.

Guide to Mod Organizer (made for an older version but generally still applicable): http://wiki.step-project.com/Guide:Mod_Organizer

[springfield1191a1]

I use windows 10 (not by choice) so MO2 is not going to be very useful. I will give the older version of NMM a try. hopefully it helps. if not i will be letting this thread know. i loved CREAtive Clutter BTW.

[damanding]

I use Windows 10 and don't have any problems with MO2. You might be thinking about a much older version? And thanks for the compliment. :)

[springfield1191a1]

the MO2 page stated that it has issues with windows 10 and i have no experience with MO at all, that's why i declined to use it. I'm very experienced with using NMM, FOMM and NVMM. I'm overcautious/paranoid/lazy when it comes to troubleshooting issues with things I'm not experienced with. I tend to mess things up. so often i prefer to acquire detailed instructions when i try to use new software. I haven't even started to use F4SE because i'm still trying to get the more advanced non-scripting aspects of fallout 4 modding down(load order organization without using LOOT, .ini editing, creation kit stuff, etc.).

[damanding]

Huh, I have no idea what the issues might be because I don't have any on my Windows 10 machine. :D

[MissingMeshTV]

FWIW I also use MO2 (most recent versions) with Win10 and have had no issues. I use NMM for my main FO4 install, but use MO2 for my test machine installs, all running Win10 and MO2 works like a champ.

[springfield1191a1]

back to the topic of fixing the mod install issues for the mod manager. The 7.zip sharp errors appear to relate to the mod manager's unzip tool being highly incompatible with windows 10 version of 8.zip and 8.zip lite. seeing as i don't know jack squat about the source code of NMM i'm currently incapable of fixing this myself. as far as the "in use by another process" error, IDFK. maybe related to the 8.zip issue, maybe not. and i also don't know any other method of telling people that there's something wrong with the mod manager other than the nexus forums. so if someone can pass on the message to the folks that are working on this freakshow of a mod manager, it would be seriously appreciated. I really don't feel like screwing about with this crappy ass thing because the guys that made it don't feel like f*#@ing with it anymore. their loss on something with nearly UP-77 Limitless Potential. as soon as i'm familiar with the source code I'll give it a try on fixing it, but until then pass the message on to the asshats that are trying to keep it working, please. Sorry for the Storyteller shooting up psycho moment but i'm quickly losing my temper with this crap.

[Rabbit1251]

One would think that you would get a better response posting your issues in the Nexus Mod Manager Forums instead of the Fallout 4 Mod Troubleshooting Forums (https://forums.nexusmods.com/index.php?/forum/439-open-beta-feedback/).

 

You should also be aware that Robin has already stated that this version of the Mod Manager is end of line and is to be replaced by a new version shortly.

 

 

The Rabbit