Jump to content

csabati2

Premium Member
  • Posts

    7
  • Joined

  • Last visited

Everything posted by csabati2

  1. Got the same result. I can confirm the crash on uninstall. It also does the same if I go strait to the Remove option. I my case the mod did not disappear.
  2. I guess you could say it was half way installed manually. I downloaded and installed the mod using Vortex. After installation, if the mod files were set up wrong, I go into the mod's folder using the "Open in File Manager" option. I rearrange the files to bee the way they are supposed to, and then just disable and re-enable the mod. To summarize, Vortex does the unpacking and I sort the files into their proper place in the hierarchy.
  3. JtBryant96's mods for sim settlements are the most recent: https://www.nexusmods.com/fallout4/mods/23125 https://www.nexusmods.com/fallout4/mods/24601 https://www.nexusmods.com/fallout4/mods/25010 There were a few others, but I can't remember which. I remember that in MO there was a "manual" installation option that allowed you to select which folder would act as the game's Data folder. Maybe something similar could be implemented for Vortex?
  4. Hi, I decided to post this up here to see if anyone else has experienced this and maybe found a better solution. Some of the mods I've installed using Vortex are being installed inside a Data folder located inside the REAL Data folder. For example; If I download and install Mod A and look in the Vortex mods folder, it will look something like this: C:\...\Vortex\fallout4\mods >Mod A > fomod > Data > Mod A - Main.ba2 > Mod A.esp After enabling it, the result in my Fallout 4 install directory looks something like this: C:\...\steamapps\common\Fallout 4\ > Data >Data > Mod A > Mod A - Main.ba2 > Mod A.esp This prevents Vortex from detecting the new esp and listing in in the plugins tab. So far the only solution I found is to do the following: 1. Open the mod folder in Vortex. 2. Move the needed mod files out of the data folder and into the mod's "root" directory. 3. Disable the mod in Vortex. 4. Vortex will then notify me that the mod files were changed outside of Vortex and ask if I want to make these permanent. Select Apply from the drop down menu and click Confirm. 5. Enable the mod again in Vortex. 6. Enable the plugin in Vortex. After this, the mod is installed correctly and loads in game without issue.
  5. This is pretty much my experience. I didn't like it at first, but it's not too bad after getting used to it. Not as easy as MO drag and drop, but also not as annoying as using the arrows from NMM. EDIT / P.S.: One thing I would like to see is a little automation for rule changing. As it stands, I need to remove rules in order to change them or risk errors when I try to sort. I would like to just make the new rule I want and the application to automatically remove any redundant or contradictory rules.
  6. You can add skse as a tool on the SSE section, and then make it primary, and pressing the play button in the top left will launch skse. SKSE wont launch through Vortex. Starting it manually works fine. Path is right, all files are installed correctly. Solution maybe? Try running Vortex as administrator; that's what got it working for me.
  7. I can also confirm this. Tried this at med preset quality with 720 res. Will try later at higher settings. EDIT: Got it to work in 720 full screen with max settings except for texture quality. Texture quality was set to medium.
×
×
  • Create New...