rmm200

For me to make this forum usable for me, I need to understand how some things work. How do I mark all current topics read? How do I know when there are new topics? How do I know when existing topics have new responses? Change is fun. Mostly. Thanks!

I will say Vortex should never, ever default to putting Downloads under AppData on the C: drive. That completely hides how much space Downloads takes. That is the first thing I recommend users change in Settings.

Mods can always be reinstalled from mod downloads. As long as you have that, and have Vortex point to it - you should be good. Just reinstall Vortex and point it to the right place after fixing your boot drive. No point in worrying about cleanup since you are nuking both your boot drive and the game.

I think you need more help than we can give you here.

Love the FNIS implementation. Every Profile has it's own dedicated FNIS output folder which can be enabled and deployed just like a real mod. If Nemesis does not give you that - complain to Nemesis.

Primary source of help for in-games has to be the game support forum. That includes developing mods for that game. Here we mostly try to help with Vortex related problems. I will say, in your case, start a new fallout 4 profile that includes only your mod. See if you can reproduce your error there. If no, add back half your mod list. Keep going, half at a time, until you isolate your problem.

I could sure use some guidelines on how to install BG3 mods with Vortex. I got the mod HighlightEverything, and Vortex prompted me to install LSLIB/Devine Tool and Full Release Mod Fixer. After Deploy, is there anything I need to do? Do I ever need to run those tools myself? My game still runs with no error messages, but I have no idea if HighlightEverything is working.

@Zanderat, my regard for you just increased. We are known by the enemies we keep.

On Skyrim, I run a mod set of about 200 mods. 80 or so active on any given profile. Fallout 4 similar. None of the authors of the mods I use say don't use Vortex. Choose your mods more carefully.

Counter-point. I am quite happy with the current layout. It is both flexible and effective. Everything I need is conveniently at hand. Well done.

Ever since Vortex came out, the upper left corner has had the game icon and a big launch button. I was one of the folks asking for the profile name, and that was added. Nexusmods has an ad box, which is fair, since they are giving us the manager. The dashboard is customizable. "Recently managed" is very useful and the way I switch regular games. I would never launch the game from there. It also shows current tools and a way to add new ones. In short, I can't even see what you are asking for. Can you post a full screen shot? Just the tools section shows nothing.

Also - how did you install F4SE? When these games give you an error message - usually believe it. Don't try playing until you fix this F4SE error.

Vortex is 90% library routines. When all of those libraries are supported on Linux - then it becomes feasible. Note: I suspect most already have a Linux version.

In the future, try to indicate which version of the game you are using. Steam, GOG, or GamePass. As I recall, the GamePass version is most problematic, running in a sandbox.

I don't think you replied to the post you think you replied to...

I finally replaced the last HDDs in both my gaming computer and laptop with SSDs. I never expect to buy another spining HDD. Could not be happier. 2TB is my largest.

VFS is not part of Windows. It is a virtual file system coded into MO 2. MO 2 has to be running when you play for this reason. Hard links are a facility built into Windows that Vortex uses. Use a Windows facility - play by Windows rules. Vortex has to play by Windows rules. Because Hard Links are a Windows facility, Vortex does not need to be running when you play your game.

Thank you!

If you come here for help - you kind of owe us an explanation of how you fixed it. It will help us help the next person with the same problem.

1) Zip up the loose files as if they were a mod (including textures directory) and drag it to Vortex. 2) Vortex will flag the conflicts 3) Disable and delete your temporary mod.

You could always unpack the BSA and install that as a mod for testing. Once you find out what is conflicting, delete the temporary unpacked bsa mod. Some mods require a bsa to function.

Programmer approach to mod debugging (Vortex or MO 2): 1) Pick one specific mod that is not working. Install only it and any required mods. 2) If this does not work, ask for help on that mod page. 3) If it does work, add back half the remaining mods. 4) If this works, add back half the remainder. 5) If it does not work, remove half the last batch. 6) Iterate until the smallest incompatible set is found. 7) Return to the mod specific site, report your findings, and ask for help.

I have several hundred mods installed using Vortex with Fallout 4. I have never experienced a problem like yours. Glad you got it working - but your problem was not Vortex.

Out of thousands of users - I have never seen Vortex install a Bethesda mod incorrectly if it was packaged correctly. Lots of bad mods though. A Skyrim LE mod will seldom work on SE.

If it has been a few years, a refresher might help. Start here: