Preemhelio
-
Posts
39 -
Joined
-
Last visited
Everything posted by Preemhelio
-
I'm curious as to WHY you keep saying this? This is NOT a step involved in modding, at all 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
-
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.
-
Fallout 4 randomly freezing
Preemhelio replied to leotheEliteMajor117's topic in Fallout 4's Discussion
Might be the game engine rendering textures and stuffs, it's kinda normal though. -
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.
-
Weird because it works completely fine to me with the latest Win 10 update. Might be on your end or perhaps with your drivers.
-
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).
-
Happy to help, enjoy!
-
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.
-
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.
-
Well if you installed something new on a mid-game save/playthrough. Things might get chaotic as the game loads the mods after leaving vault 111.
-
One thing I noticed is that you only have 1 active VIS Plugin. There's different modules in that mod and for each module you need to choose a single option. As I use Vortex our method of putting a mod to work differs.
-
Looks like it's a slow texture rendering, it's been there since it's a part of the vanilla FO4 and it's engine. Try setting your iTexMipMapSkip to -1 on your Fallout4Prefs. See if it fixes that.
-
Retextures of Sanctuary bridge are so worth it I tell ya.
-
The most common way to identify the culprit is to retrack your mods, especially the new ones and disabling your mods one by one. This method might induce headache if you have a lot of mods.
-
Just a tip: You literally can role play every RPG and Survival games with open world so that it'll last longer <3
-
I believe those textures in the screenshot provided for the sanctuary bridge are the vanilla ones, it's been there a long time now I'm afraid.