Jump to content

tesoblivor

Premium Member
  • Posts

    24
  • Joined

  • Last visited

Nexus Mods Profile

About tesoblivor

tesoblivor's Achievements

Apprentice

Apprentice (3/14)

  • First Post
  • Collaborator Rare
  • Conversation Starter
  • Week One Done
  • One Month Later

Recent Badges

0

Reputation

1

Community Answers

  1. UPDATE: Figured out how to rename the mod as listed in Vortex
  2. Try deploying again and see if that resolves?
  3. Possibly, but I have checked the logs and it picked up nothing. Running on Windows 8.1 and have found that the recent update all seem to follow the same pattern; Allow vortex to update. Vortex complains about the file. The file VORTEX.EXE exists .... but does not execute. Reboot PC and the file VORTEX.EXE is missing. I then download the latest version and install that and it works first time .... The problem appears to be when the files in the executable installation folder are changed or updated.
  4. tesoblivor

    CTD

    Cleaning your save file might cause issues so make sure you keep copies that have not been cleaned. As for whats causing it .... not sure. From what you have said it sounds like ASLAL (guessing this mod https://www.nexusmods.com/skyrimspecialedition/mods/272?tab=posts) is perhaps the issue. Or rather there are some files in your installation folder that either is from ASLAL or needs ASLAL to work. Uninstalling Skyrim and manually removing any remaining files left after the uninstall might resolve it. Just be careful in what files you remove and be sure to back anything up before you remove them. At the least I would recommend backing up any personal files (documents etc) and making sure you can restore the PC should anything critical go missing. If in doubt keep a backup. Hope that helps, but it sounds like there may be some files (or mods) somewhen in your data folder that depend on ASLAL to work and not everything it needs is there to work.
  5. This explains why I am getting it now then.
  6. Still getting the update notification myself, checked and on the stable channel. Will this take a while to resolve and is it worth disabling auto updates for the moment? EDIT: The update being offered always fails. The VORTEX.EXE literally disappears and I have to manually reinstall. Checked the AV and no notifications or anything in quarantine.
  7. Weirdly it's now started working. Had to reboot the PC and uninstall, then reinstall. Not sure what went on.
  8. Just installed the latest version and getting the message that Vortex is correct and suggest reinstalling. Have uninstalled several times and reinstalled, but it is still giving me the same message. Any suggestions please? It was working ok before the update.
  9. It's a bug in the newest version of Vortex, as seen in many threads that have been started It's being worked on Thanks for the reply, much appreciated.
  10. You can get the latestest and previous versions of Vortex here: https://www.nexusmods.com/site/mods/1?tab=files But word of caution; if there has been database changes going to an earlier version might cause problems, especially when you update the database. At the moment I would say it's best to do nothing until we know more about the cause and implications.
  11. UPDATE: Skyrim Special Edition is also reporting that the file ""...\steamapps\common\skyrim special edition\data\fomod\info.xml" is also conflicting with several mods. What is this file and why is it a problem? This isn't a file I've seen in any mod I've installed?
  12. This happened twice now and appears to occur when there is a Vortex update available, but you exit the program without updating. The scenario seems to happen this way: 1. On exiting Vortex you are asked to allow Vortex to make changes to your computer. I've said yes each time, not sure what would happen if I said no. 2. You cannot go back into the program as it says you don't have permission. 3. If you check the file properties for Vortex.exe and try to take ownership you cannot. You are told by Windows that you have no permissions. 4. Eventually Vortex.exe disappears. Installing Vortex again seems to resolve the issue, except this second time my Fallout 4 mod section is telling me I have a ton of files that are conflicting. Some of the those files should not be conflicting at all. For example these two mods have a conflict: "A bundle of tape" and "Ak5c". The file in question is "...\steamapps\common\fallout 4\data\fomod\info.xml". What is that file and why is it conflcting? That's not even the strangest. Hopefully that's enough to shed light on whats happening and I really hope it can be resolved. But more than that can anyone suggest something to get my database back on track and not messed up please?
  13. Did you select any of the disabled mod and pick "ENABLE", because Deploy won't do anything until you ENABLE the mod. I didn't sadly. I probably should have to see what would happen. If it had linked the file to mod entry again it would have saved me some work. If it happens again I'll try that first. Thanks for the reply, appreciated :)
  14. Don't worry. Purging and deploying are different processes from uninstalling and installing. Purging does not uninstall your mods. It simply removes the mod hardlinks from the game data folder. These hardlinks are established when you first install, enable, and deploy a mod. When you re-deploy, the hardlinks are re-established. Re-deploying does not reinstall your mods. For further information, please consult the Knowledge Base that can be accessed from your Vortex dashboard. The "Purge" and "Deploy" buttons are on the mods page taskbar. If you dont't see them there, then go to Vortex settings and turn on "Enable Advanced Mode" and "Deploy Mods when Enabled." Edit: I incorrectly labelled a Vortex setting. "Deploy Mods when Enabled" is the correct label. Hi Augusta just wanted to say thank you for your assistance, it really helped a lot. I did the purge as you suggested, which basically reset the Skyrim SE folder back to a relatively clear state. The Deploy button sadly did not do anything. But, with the disabled files listed alongside their mod entry, it was simply a matter of going through the list to remove the disabled file and then install the mod again. I'm going to keep a backup of the "\AppData\Roaming\Vortex" directory, so if it happens again hopefully I should simply be able to restore that directory.
  15. Don't worry. Purging and deploying are different processes from uninstalling and installing. Purging does not uninstall your mods. It simply removes the mod hardlinks from the game data folder. These hardlinks are established when you first install, enable, and deploy a mod. When you re-deploy, the hardlinks are re-established. Re-deploying does not reinstall your mods. For further information, please consult the Knowledge Base that can be accessed from your Vortex dashboard. The "Purge" and "Deploy" buttons are on the mods page taskbar. If you dont't see them there, then go to Vortex settings and turn on "Enable Advanced Mode" and "Deploy Mods when Finished." Thanks Augusta, I will give that a go as soon as I am able :)
×
×
  • Create New...