Extremely frustrating experience

[AreeSoothsayer]

Ah, you're afraid that working with a different version will also be broken and when you redownload the console mod it won't install. Correct?

 

 

Edit: That bit about uploading, that's for people making a weapon/armor mod of their own using that system. Normal players don't need to worry about it.

Edited June 30, 2016 by AreeSoothsayer

[Gilibran]

Glad to see you are on the right track.

 

To answer the manual instal question, NMM will see the esp files you installed manually and list them, but you cannot do anything with them in NMM. They are listed the same as the original game files without the option to activate or de-activate.

 

The problems with manual installation are mainly uninstalling them, you have to keep track of the exact filepaths if you do not want the mod anymore and delete them manually. Another problem is you cannot easily adjust loadorder, if you get a new mod that needs to be loaded before an already installed mod in order to work, you have to manually install the old mod again after the new mod. Yet another problem could be textures. You might want the item of mod A but with the textures from mod B. You install mod A and then search the files of mod B for the texture folder and only install that one overwritting the texture folder of mod A. There is alot to keep track of when manually installing mods and it can, and will be at some point, a royal pia.

 

You do have more freedom when manually installing because in the above example with NMM or MO you would have to choose either mod A or B. On the other hand you can make your own esp containing only the texture folder and easily activate and deactivate it with NMM.

 

Good luck

[iSagan]

Aree, will manually installing mods make mod loading impossible?

Gunna give it a quick go in the morning but if it ends up destroying my game I'm gunna go nuclear, so I need to know whether or not I can use a mod loader on manual installations first. Also, the AWKCR mod is required for another mod I want, based on fixing the armor issues the base game never patched. And yes, I don't want the console mod to stop working. I just can't risk it, I've enjoyed and loved this survival playthrough and if I trash that for another version of NMM that gives me the exact same problems I'm gunna end up drop kicking a heated water tank.

You're still not helping at all Gilibran.

Edited June 30, 2016 by iSagan

[AreeSoothsayer]

Manually installing just means manually uninstalling. Gilbert was actually on the ball there, I prefer the keep the zip file approach. If I want it gone I open the zip and find everything in there in my fallout folder to delete them. These days it's usually not loose files and such but a single file with everything in a format that FO4 reads.

 

As for destroying your game, it would only do that if you Save the game 3 times with the stuff going. To be 100% safe go into yuur save folder, make a copy of your saves and place them in another location.

 

Now it's past midnight for me so gonna head to bed myself. I'll check here in the morning.

[iSagan]

Yeah sure, maybe he's right about manual installation but that moves me absolutely no where. I still have the problem with NMM, I'm not interested in spending ~2 weeks of my time learning how all this works and there is no sign of an issue that could be fixed.

I'm talking about risking the console mod, Aree. If it goes with the NMM after I remove it to get an older version (which might not work and have the same problem) then its only hours till the game encounters a fatal bug only the console could fix and I would be forced into starting a new game. Making all that time and effort disappear. That's what I mean.

Lets keep in mind, while all these work arounds work great as a bandaid for 1 mod or another, I won't be able to have the Nexus experience until we find the issue and the product becomes nearly irrelevant. In the case for the Full Dialogue and Console mod, I didnt even need Nexus, which makes these work arounds increasingly irrelevant. I just want to fix the NMM, I don't want to learn about manual installation, I want to play Fallout 4.

Edited June 30, 2016 by iSagan

[Gilibran]

I see a few more replies were posted while i was typing

I was replying to your question about manual installation.

 

About instaling a older NMM version and your savegame. Normally it should not be a problem as long as you make sure the exact same mods are active again, your savegame will work.

 

However because you are having problems activating them there is a chance activating mods will not work on a older NMM version to. Most mods though can be de-activated and uninstalled without affecting the savegame.

 

I have been searching the forum and beyond but i could not find anyone else with your exact same problem. All answers to mods not activating lead back to something gone wrong during installation of NMM or wrong (old) version of FO4, NMM and or mods.

 

I believe you when you say you did everything correctly, but you still have problems, and as said earlier, for tons of people it is working fine should he jo reason you cannot get it to work.

 

The only advice i have left is to go back to start and go all over it again step by step or wait for someone else to jump in who encountered the exact same problem which seems to be a very rare one which also explains the lack of working solutions presented.

[iSagan]

I can't do that. I can't risk the console mod on the reliability of NMM. Also, Aree found references to other people having the same issue I have, and that the development team is looking for people to help with the bug.

Mods not activating is not the primary issue either; its not why I'm here. The NMM activates most mods but they never do anything to the game.

To recap so you don't ask me all these things from scratch again:
Yes, I editted the .ini
Yes, I followed every instruction, ticking them off 1 by 1 as I successfully followed them
Yes, I checked for plugins and activated the mods

After that I open the game and no difference. The discussion about AWKCR not activating was separate, and used purely as an example of additional problems I've had with NMM.

I either have to wait for the patch that resolves my issue, or hope someone has an answer to the problem, or can hop on team viewer and walk me through mod installation so they can see it themselves and join me in trying to work it out.

There is no problem with Fallout 4, I have done the verification and reinstallation several times which wasted literally a full week of game time. There was no problem with NMM initially; it allowed me to download the console mod without issue doing it the same as anyone else would experienced or not. And the mods are commonly used; if there were issues it would be well known. Since the time I successfully modified my game to support Survival Mode Consoles I have only played Fallout 4, I haven't downloaded anything or updated my system. And so, here we are. Caught up again. So lets try and narrow it down till I get to the issue rather than talking about preferred ways to download mods. Like I said in my last post, I want the NMM fixed so it's usable again. I DO NOT care enough to study on mods and further my frustration with computers, and the main reason I'm using NMM is because its user friendly and seemingly wasn't overly complicated for someone who hasn't modded before.

Edited June 30, 2016 by iSagan

[Gilibran]

It should.not be complicated, your right it should be plug and play after following the instructions.

 

The problem Aree is referring to with symlinks is when NMM and FO 4 are installed on different drives which is where the Multi HDD mode he mentioned is for.

 

If you have installed on different drives, that's the most likely cause of your apparently very rare and specific problem. If not then we are approaching a dead end quickly.

[iSagan]

In that case we can scratch that one off the list; they are both in the same drive.

I tested with the Dialogue mod...

Download through the Nexus, activate it, no change

Manually download it, place the files in the folder, works perfectly fine

For some reason its the interaction with the Mod Manager that is the issue. And it only started a couple of days after I had no problem using it. This is why its so frustrating, usually with computers, at least you can knock one problem at a time till there's nothing left it can throw at you and you finally get it up and running. I haven't found a single thing I can fix, tinker with or adjust. It worked fine, reinstalling isn't needed. So what now?

My head feels like its going to explode in a white hot rage. No matter how hard I try to figure this out I'm taking the long complicated roads to no where.

The offer still stands, if you wanna take me up on it. A walk through with team viewer/skype screen viewer could earn you a few bucks. I've wasted more than a week trying to wrap my head around all this BS drama and right now I can't even start up the game after seeing all the amazing mods. So you'll be helping me make the money I spent on this game worth it. Just consider it, at least to watch my process in case I'm in fact doing something incorrectly. Or if an option is off in the Nexus or w/e w/e w/e... I just need a way to make this simple now its been a literal constant head ache and my eyes feel like 20kg weights.

[Gilibran]

Well then we hit the dead end. There is only one more thing i can think of and you have to hope someone else jumps in here with a solution, i do not have any more tips where to look for you i'm afraid.

 

It could somehow be a communication error between Steam and the NMM launcher, perhaps NMM is not able to verify the game on steam, looking at or using the wrong steam executable or something. It is somehow not syncing/registering and in that case NMM blocks mods from loading. That's why manuall install works but through NMM install it does not. It could simply be thinking your game is not legit, all issues you have are very similar to that.