Preemhelio
-
Posts
39 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Preemhelio
-
-
So, I wanted to try out a few mods in this game. So I looked up a tutorial. Several of the tutorials that are recommended are now out of date and it is incredibly confusing as to what I should actually be doing.
I installed several mods via nexus which I had prior experience with. I used vortex (previously known as nmm). I then enabled these mods in the mods section. I was then told that I need to enable all the plugins, which there are none for some reason. I will provide a picture of the mods I want to use. I then tried launching it through steam, none of the mods work. I then tried launching it through f4se which I installed just to see if it would work, no mods worked. I then launched it through Vortex, no mods worked. I then took the files from vortex and copied them into both the mods and data files of my fallout 4 installation just to see if that would work and launched fallout 4 through all three of the different programs I stated before AND NONE OF THEM WORKED. How the hell is this supposed to work? Someone please help me
Vortex is not NMM though. Vortex should automatically prompt you in deploying mods after you install one and when it's done on deploying mods, plugins should be enabled if not then it needs to be double checked for enabling. I wonder if you've invalidated your files for modding. I find it weird since I've been using Vortex for awhile now without a single issue and works perfectly fine with heavy load of mods.
-
Well I'm sure that's a device error, might be an issue in your HDD that prevents your windows or system from reading/writing contents on it.
Here's some reasons:
- The HDD is damaged physically or logically
- Drivers Outdated
- The file system of the HDD is incompatible with the PC
-
If you haven't read this, here's how: https://wiki.nexusmods.com/index.php/How_to_create_mod_installers Hopefully this'll solve your problem.
-
It seems that you haven't invalidated your files for modding purposes. Read more here: http://wiki.tesnexus.com/index.php/Fallout_4_Mod_Installation and here: https://wiki.nexusmods.com/index.php/Installing_your_first_mod_with_vortex I suggest to read them thoroughly as they should solve your issue.
-
Might be the game engine rendering textures and stuffs, it's kinda normal though.
-
Try using the Scan for Games button on the lower right side of the GAMES tab and just put your game directory in there.
-
Go to the GAMES tab on the left side of General section and just choose your game or use the search bar on the upper left side and search for the game that you'll be managing.
-
I think you're in the wrong thread, you shoud've posted this in Feedback, suggestions, and questions. But if you've been reading the news regarding the upcoming changes that Nexus will implement, you're in luck. Kindly read this whole article regarding the Mod Collections: https://www.nexusmods.com/news/14538 Secondly, if a mod doesn't work on the first try, It's clearly that you're missing a requirement for the said mod or you haven't been sorting your load order or it's conflicting with another mod. Searching for mods doesn't hurt to try, it's just a few clicks away and of course it'll take a lot of time but it'll be worth it after tho.
-
Well I think it's a known issue in Vortex regarding with the old mods. Though it doesn't hurt to enable and try to always double check your plugins.
-
Weird because it works completely fine to me with the latest Win 10 update. Might be on your end or perhaps with your drivers.
-
Purge all of your mods before transferring to your another pc. Then make sure the game and the mod folder (staging folder) should be on the same drive. Run the Vortex to detect the new game location. Restart Vortex again just to be sure. When you're in Vortex, click settings then go to the MODS tab above to set your staging folder. Finally just deploy your mods after that. Here's more info regarding the topic: https://forums.nexusmods.com/index.php?/topic/7745623-move-vortex-mod-folder-to-another-drive/
-
FOMOD is the file used by fallout mod programs, you basically need a mod manager such as MO2/NMM/Vortex to install a fomod safely otherwise there's another file intended for manual installation of the mod (drag and drops most commonly).
-
thanks again...boy talk about a real pucker factor LOL yeah it all functioned correctly whew that's relief
Happy to help, enjoy!
-
thanks for responding , I just wanted to be sure ...I heard that CBBE used the same folder for each and that starting/loading one would corrupt the other due to the shared location or file or something to that effect
Nope, you're safe. Just make sure they're from their own respective games and don't, I repeat, don't put CBBE Body from Skyrim to FO4. FO4 has his own CBBE Body mod likewise to Skyrim. Now, have fun!
-
You do know that FO4 and Skyrim are two both different games right? Those two games have different directories. You're using Vortex which then sets up two different staging folders for each games. Just because they're the same mod doesn't mean they'll be sharing the same directory or drop off point. A game wouldn't mess with another game's directory. I play with different modded games from time to time including FO4 and Skyrim without any issues over a decade of modding as they would never ever conflict/overwrite each other files. Should be fine as long as you know what you're doing. There's a lot of tutorials out there if you're looking for one to help you understand things you still don't know.
-
Needs more info plus those screenshots are too small to be viewed. Ever tried disabling your mods one by one? If not, you should do that and report back otherwise provide a load order and a bigger screenshot or a GIF which is better.
-
Start Vortex. Go to the settings then just click the MODS tab above. The staging folder location should be there.
-
No, sorry, this didn't solve the glitch. As you said, I tried every possible tweak. Maybe some future driver updates will fix it. I need to learn to live with it until then. Thank you for trying to help me. I really appreciate it :smile:
I'm sorry to hear that. Yeah perhaps it's the game itself, hopefully those future driver updates would solve it. and you're welcome anytime.
-
And you did try putting SMM's holotape? Then clicked Settlement Menu Rescue and waited for a moment until a note confirmation appears? If yes then I've got no idea what's causing it atm, perhaps disabling your mods one by one is your best bet to find the culprit that's causing it. Goodluck!
-
You've got too many mods that alters the workshop menu, try downloading Workshop Framework or Settlement Menu Manager (SMM) more info on their descriptions.
-
Hmmm suppose you've also tried tinkering with VideoMemorySizeMb in enblocal? If yes, I'm literally not sure what causing it this time. Seems you've already tried every possible tweaks. Hopefully you'll figure what causing it, goodluck!
-
The mod was hidden by the Author for a reason, might be because of the new policy but idk and everyone should respect that they've made their decision regardless if it's permanent or temporarily. He might move it somewhere else in the future, best way is to get in touch with the Author himself for this.
-
Choppa The Gulper. I tried :sweat:
-
I used to run FO4 on an HDD before my rig upgrade and haven't got that issue, texture pop-ins sure but low texture rendering seems also a part of the game engine itself. You know, Bethesda and their left over stuffs.
Please for the love of god somebody help me with modding
in Discussion
Posted
Dunno bout you keep popping out of nowhere when I'm trying to help people politely based on my knowledge in adding support for mods. Also read here since you've got an issue: http://wiki.tesnexus.com/index.php/Fallout_4_Mod_Installation