haguerepairguy

That'd be awesome!

In response to post #58053771. #58062616 is also a reply to the same post. I use vortex with fallout 4, and yes, fo4edit, and bodyslide are incorporated. Also FNIS. Just make sure it's installed properly before trying to tell vortex where to look to use it and you're all good. :) If you need more help with that, let me know.

Ok guys, so I have to admit, I haven't used Vortex as extensively for multiple games yet as I planned. However, there is one huge thing I've noticed with Fallout 4. As an NMM user, my mods aren't crapping out on my save games. 104 mods thus far, and it's smoother than silk with all of my texture packs playing nicely together. Likely I had an install order screwed up in NMM, but even if I did, I didn't do anything different with Vortex for that, and it's running like silk. I've been a part of beta's that were put together more conflicting than this. I get some people are saying some features are missing from MO, but what I'm seeing is that it's going to make it easier for modders to make their mods work together. To me, now that I've played with it a bit, it's more comprehensive. I admit, I uninstalled Fallout 4 just to clear out any old issues, and erased all traces of it from my machine then reinstalled it without any backup data from my steam cloud a few days ago, but I did so because I was having CTD prior to Vortex, and clearing my mods didn't fix it. There were a lot of messed up files, and not even verifying the catch helped. A full wipe of it, and reinstall and it was playing perfectly without mods again. Vortex proceeded to install mods without errors after that, and now I get 0 CTD except in areas that were already common and annoying as hell. I really wish they'd have optimized a few more things so that boston downtown didn't lag so much. From 71.9 fps to 17 is a huge drop. lol Still, it's a far cry better than dropping to 3, and then CTD every time I stepped near some quests in that area. >.> And it's loading my 2k, and 4k textures during all that without much issue (aside from the fps drop I mentioned). I've also had 0 trouble uninstalling mods completely. A save game clean run, loading and saving, then reloading after uninstalling it is all I need, as compared to the save breaking entirely at times. I've wiped out every mod and reinstalled (with a backup of the save just to be safe) just to test it fully, and never had any problems at all with missing textures etc. where as with NMM, just trying a few mods uninstalled would leave empty textures etc. Beautiful work!

In response to post #57736771. I read in one of the articles here on Nexus that eventually they will be adding features and the like to the way the layout sits with Vortex giving us more control over that but at the moment, visually it's as good as it will get, and they are focused strictly on making everything work without giving everyone a headache. Once the biggest chunk of bugs is worked out with the currently supported game list, they'll move through the other games I"m sure, and from there begin adding the painful changes to make the look and feel much more user friendly. Until then, this is just to get us used to it and give us a way to tell them how it's working. Don't give up on it yet, but I see your point, and feel that if you're a hardcore NMM fan this is how it's going to be for others too. Me, I loved NMM, but I was always looking for more, but MO just bugged out too much for me. I had a real problem with it. Vortex however...... I'm finding it to be quite simple in the end. :)

In response to post #57785636. #57788366 is also a reply to the same post. From what I've read this is a known issue and is with steam, but I may be wrong, adamcatfish is right, that's the best way at the moment (unless an expert or developer comments, that's what I'd go with)

In response to post #57801491. Most of the mods you install, if you didn't rename them, will have the version number first, then the second set of numbers is the actual Nexus ID, and the 3rd set is a repeat of the version. V1.2-2345-1.2 something like that.

In response to post #57804721. Best way to get past it is to uninstall that mod from NMM, then import, and redownload that mod from nexus using vortex, that should fix the problem. Just remember the install order and what it conflicts with first so you can easily set those rules up without breaking your game trying to figure it out. Honestly though, I found the best way to do things is to completely start from a fresh install of the game, then download the mods, but that's only because I'm extremely picky and already had issues with save games breaking thanks to bad install order etc. with Fallout 4. Right now I'm looking at the most realistic version of Fallout 4 I've ever seen, with almost no frame drops or issues and I'm looking at nearing 100 mods. Again, that was my doing that caused the issues before though, so it's not a requirement you do it that way.

In response to post #57676981. #57705396, #57706276 are all replies on the same post. Better yet, just refer to the expert, lmao. Thanks Tannin!

In response to post #57690726. #57703451, #57703491, #57705326, #57706291 are all replies on the same post. Sounds like a possible driver issue like peterdw said, just in case, I'd check that first, but also use the submit feedback button inside vortex, and take a screenshot if you can if it happens again and pass it along so they can see exactly what's happening, any errors that are generated, etc. It's very possible it's a bug.

In response to post #57667701. When installing mods they install to the data folder, like what NMM does. This is a feature that likely won't be changing from what I've seen, and I've read that it's being done because it's the most effective way to avoid errors. They may change it as time goes on, or add an option to make that not happen.

In response to post #57676166. Perhaps try redownloading it, but before you do, click the symbol on the right, next to both mods. You may need to make a rule for jtbryants foundations to load first.

In response to post #57676981. Sounds like your antivirus is causing you problems actually. Try disabling it to install it, then white-list the program before starting the antivirus back up.

In response to post #57690726. #57703451, #57703491 are all replies on the same post. If it's during deploy mods, that's one thing, but if it's after, when you try to load the game you just set up mods for, then you have a mod conflicting that's causing game issues. Could use a little more info as to what you were doing, with what mod, so maybe we can help you diagnose it. :)

In response to post #57637336. #57642081, #57653221 are all replies on the same post. From what I'm seeing, it's partly to do with the names of the files. So if 2 texture packs have files named the same, that's where the issue is. Somehow you're supposed to be able to rename a file in Vortex, I haven't had the need yet so haven't discovered it but I'm sure in Fallout New Vegas, with my 100+ mods I will be needing it. lol. I have a few texture packs for Fallout 4 that have a similar problem, but they are loading the combined textures, certain ones are loading from the one mod, others from the other, as it did with NMM. I was expecting to load up my game and find that some textures had red triangles, or simply didn't change, and am pleasantly surprised.

In response to post #57664826. I had that happen, and found out partly that I had fallout 4.exe running. I ended the task, and it worked like a charm after.