Jump to content

capella6707

Premium Member
  • Posts

    168
  • Joined

  • Last visited

Everything posted by capella6707

  1. I'll echo this. I'm getting a new computer and am hoping to be able to just copy everything over from my old computer. I'm really not looking forward to reinstalling 270+ mods! Unless I hear anything different, my plan is to install Steam, Skyrim, and Vortex and then copy to the new computer the SSE My Docs folder, the entire Vortex App Data folder, the Vortex staging folder, fire SSE up and pray that it works! More likely I'll have to completely redo everything, but I'm going to try.
  2. Vortex has made modding my games so much easier than previous mod managers. Thank you for all of your time and effort Tannin and team!
  3. From what I've read on these Vortex forums, it seems that die-hard MO users are the least willing to actually take the time to learn how Vortex works before they make any judgments. "Vortex doesn't work", "Vortex messed up my mods", "Vortex is too difficult". It's a new, different program; if they'd approach it with an open mind and the understanding that it won't work the same as MO or NMM, maybe they'd be more successful at using Vortex to mod their games. Glad to see someone has a mind of their own!
  4. Ditto here, sopmac45. I have never had an issue installing any game or Steam - and therefore Steam games - in Window's default program installation folders.
  5. I won't comment on individual points you've made. What I will say, though is I have used MO, MO2 and NMM, and after taking the time to learn Vortex - it most definitely requires you to rethink how to manage categories, groups and conflicts - I won't go back. Vortex is so much easier to manage mods, in my opinion. I am using over 270 mods on Skyrim SE and the game is rock solid. Take the time to watch the videos, ask questions here, and there's a Wiki, as well.
  6. 300+ ?!! Sheesh! You've got your work cut out for you! :laugh: I'm running 276 mods (246 plugins) and the game (SE, also) is rock solid. I've never had a game running as stable as this when managed by MO/MO2 or NMM. If this is your first time using Vortex, though, give yourself time to learn it - there's an adjustment to how you think about how and when mods are loaded, and how conflicts are resolved. You'll find great help right here.
  7. BigBizkit & Grestorn, Thanks, both, for the explanations. And thanks, BigBizkit, for the link - I wasn't aware that there was a wiki for Vortex yet.
  8. I have three plugins with the "Light" flag. What exactly is that indicating?
  9. Okay - totally weird: I just fired up Vortex today with the intention of figuring this issue out and whaddya know, all of the disabled plugins were enabled again (as I said in my original post, none of the plugins were enabled after re-deploying). Not sure what to make of that, but at least I don't have to figure out what plugins to enable... (HadToRegister, the mods were enabled, but all of the plugins, except the bashed patch, were disabled - that's what was confusing me.)
  10. Just what the title says - I used the Purge button for my SSE install. After re-deploying them, now all of the plugins, except the bashed patch, are disabled. All of the mods are enabled, but all of the plugins are disabled. I know that many plugins are supposed to be disabled due to being in the bashed patch, and I think there were others disabled as well, but I have well over 250 mods, so that's a lot of plugins and I have no idea what which ones were or were not enabled prior to purging. Any suggestions on how I can resolve this?
  11. In this particular case, it's not just an "update", per se. Steam thinks SSE isn't installed at all, so instead of the button on the SSE page in my Steam Library saying "Play", it says "Install". It started showing up that way about a month ago - no idea why - nothing about my games changed between when the button said "Play" and when it started saying "Install". Perhaps a Steam update broke the connection. That's why I'm wary about what will happen when I hit the Install button in Steam.
  12. It's been a couple of weeks since I've played SSE - let alone keep the 270+ mods I've been playing with updated. I've been kind of putting off playing partially because Steam decided to show SSE as NOT installed - the Library page for SSE in Steam says "Install", not "Play". Although the last time I played the game it was like that and the game ran fine. It's just that the game somehow got "disconnected" from Steam. Anyway, so today, with the intention of checking what mods need to be updated and then playing for a while, I fire up Vortex and start downloading and updating mods. It wasn't until about the third SKSE-based mod that I realized that SKSE updated. And while looking into that, I found that SSE itself was updated as well. Well crap... Now I need to update SSE since I've installed mods that are for the latest version of SSE and SKSE. So I need to figure out a plan to update SSE without wiping and reinstalling everything. I believe that's where Vortex's Purge Mods will come into play if I understand it correctly (I've never used that feature before). I'm thinking my plan of attack needs to be: In Vortex, purge the mods, which brings SSE back to a vanilla state, correct? That will still leave non-Vortex, manually-installed mods, correct? Copy the remaining contents of the entire Steam SSE folder to a safe location (re)Install SSE via Steam, which will install the latest version Overwrite that with the backup that I did in step 2 In Vortex "unpurge" the mods I should be good to go, then, right?A couple of questions: To purge the mods, do I need to select all of them first, or does clicking the Purge mods button automatically purge all currently installed mods? To restore the mods that have been purged, do I click the Deploy button next to it, or does the Purge mods button toggle to say "Restore mods" when the button's been clicked?Does this look to you guys like a sound plan to restore Skyrim to a playable state with minimal work? Are there any additional steps I may want to take to ensure everything is restored correctly?
  13. Thanks for the explanation, Tannin! An option to backup the state is a great idea, I think.
  14. I just updated Vortex (I don't know what version from/to, but I had it opened on 10/2 with the latest stable version, and today on 10/4 it said there's an update available). Now, when I try to start Vortex I get a message saying "Application state is invalid. I can try to repair it but you may lose data" with the options to Quit, Ignore and Repair. Needless to say the "Repair" warning scared me off that without knowing exactly what data I could lose. I've put a lot of work into a stable modded install of Skyrim SE and I don't want to do anything to compromise that. So, should I just download and reinstall it, or Repair it?
  15. Reading "The Problem" section on the mod page, it seems that something very similar happens when I have Vortex download and install a mod's update by clicking the "cloud" icon. I always get duplicated entries when I update via that method. If if it's not been reported/detailed yet in a feedback, the next time that I update a mod that way, I'll put together a step-by-step and submit it via the feedback. To be honest, I would've sworn I already submitted a detailed feedback about duplicates being created when updating, but it's not listed in Your Issues on my Vortex Dashboard.
  16. From the sounds of it, it sounds like you had every folder path for every game you had installed pointing at the SAME folder. What is the path to your Fallout 4, and Skyrim installation that Vortex is having such a hard time with? Let's see what your Fallout 4 and Skyrim directory paths looks like Agreed, HadToRegister. Kifyi, it sounds like there's a path setting that needs to be fixed for one or both of your games.
  17. @ Tannin - It's been quite a while since I've added a Nexus mod manually, but I'll keep that in mind.
  18. That's a great place to start! We can help. It sounds like you're not understanding how Vortex works with the files from the download process to actually getting the game to "see" the mod. I'll go through the basics of getting a mod and making it so it works in-game. Vortex Setup (this is only in terms of downloading and deploying a mod): This is all in the tabs you see when you click the Settings tab on the left side bar On the Interface tab find "Deploy mods immediately when they get enabled" First, mouse over the "i" information icon and make sure you understand what that says. It explains why that option is there and how installing and deploying are different in Vortex. That "separate directory" will be explained in the next step This comes down to personal preference, but I've found I prefer it off, as I have mods installed that I'm not ready to use yet (i.e. deploy). I started out with it enabled, so you may want to as well, as right now it's one less thing to think about until you need to or are ready to take more control over mod installation and deployment On the Mods tab, the Install Path MUST be on the same drive that the game you intend to mod is installed on. This is only for Gamebryo/Bethesda games, but you said you want to mod FO4, so make sure you understand that. On the Download tab make sure you have "Handle" set to on (green) next to "Download with Manager". The Download Path can be anywhere on your computer or a network-connected drive. Just make sure that Vortex can read it when the program is running. That's the basics of setting up Vortex to retrieve, install, and deploy a mod. (Never forget, those are three separate steps and it isn't until you deploy/enable a mod that it will actually be used by the game) Now we'll get the mod set up to work in the game. So in the Mods tab on the left side bar find the mod you want to deploy and it will say in a blue box/button "Never Installed" (assuming you have, in fact, never installed it - otherwise it'll be gray and say "Disabled") Click on the Never Installed button and you'll see a blue box in the upper right saying it's installing the mod and will stay there for a time, depending on the size of the mod archive If there's a FOMOD installation, that will pop up and you'll go through any available options The blue Installing message will go away and a green message box will saying the mod is installed, with an Enable and Dismiss button Assuming you set Vortex to deploy mods when they get enabled (In step 1 above in Vortex Setup), when you click the Enable button, the mod's status indicator will turn green and say Enabled If you chose not to deploy when mods get enabled, the mod's status will be gray and say "Disabled" You must then click that button to enable it (obviously) The mod is now active and its effects should be seen in the game (depending on whatever the mod does)If you get a message that there is a conflict. I'd recommend posting for help in a new thread. I hope this helps!
  19. Sometimes entering "Nexus Mods" from the drop down will give you the option to click "GUESS" for the Mod ID, which works. Great tip. missed this function. Works like a charm. Ty. :smile: Be aware that from time to time the Guess feature guesses wrong! I'd give it about a 95% accuracy rating. Double-check that the ID it assigns it is correct.
  20. But now I don't where the actual MODS are. The archives will be where you set the new downloads folder to, and the actual, unzipped mod files would be in the install folder, which is set in the Mods tab in Vortex, but I'm assuming you'd know that, so I'm not sure why you're saying you don't know where they're at! :-)
  21. Ugh...GREAT. After reading about the new structure, in order to prepare, I set up my Vortex folders that way, so now the new Vortex will choke on the structure and refuse to work because the Download folder already has my mods in it. I just upgraded from 0.15.9 to today's release of 0.16.5. Believe me, I was a bit nervous about the whole "moving the downloads folder" process, but it went very smoothly for me! Previously I had my downloads folder in {network_drive}\folder\folder\Vortext\{GAME}. For the upgrade, I just set it to a different folder on the same drive ({network_drive}\Vortex) and it moved everything over just fine!
×
×
  • Create New...