Nagev

Nevermind, managed to reproduce and fix it. Fix will be available in Vortex 1.13.6 early next week

Hey @HaVeNII7 - do you perhaps have these mods exported as a collection? would make it easier for me to start debugging this issue.

Hi there @metalheadhr First of all, thanks for bringing this to our attention, your tests are appreciated and did indeed highlight a bug. After running some tests on my end, this appears to be a visual bug in the plugins page. As you can see in the snippet above, although the plugins page is defining the LOOSE version as the source, the deployment manifest itself is using the correct source. You can double check this yourself on your end - open up your "vortex.deployment.json" file and look for the ".esp replacer" source. (Searching by "SofiaFollower.esp" will match too many entries from the original mod) This will be fixed in Vortex 1.13.4 which will be released sometime in the new year. P.S. In the future please report any such issues on our issue tracker as it offers better visibility: https://github.com/nexus-mods/vortex/issues

Hi guys, Just spent a good 60 minutes trying to reproduce this while managing SSE and VR alongside each other, switching between them, installing mods, intentionally changing the target gamemode for the downloads, etc. Each operation was reversible and at no point were the mods assigned the wrong primary gamemode. The only thing that could potentially cause something like this would be if the VR extension gets loaded before SSE but that's impossible as they're loaded alphabetically. Can you try to set all the downloads to SSE and then disable the bundled Skyrim VR extension in the extensions page and let me know if the downloads are still set to skyrimvr. Edit: My assumption is that you're all using Vortex 1.13.3 - if you're not, please update.

Hi guys, Please do report these type of issues on our bug tracker "https://github.com/nexus-mods/vortex/issues" so we can look into them. It's hard to keep track of 5 different platforms for bug reports and some may slip through the net like this one almost did! A beta version of Vortex has been generated which is solely meant to fix this issue. https://github.com/Nexus-Mods/Vortex-Staging/releases/download/v1.13.4-beta.1/vortex-setup-1.13.4-beta.1.exe This version is not distributed through regular channels as we did not want to affect any working environments during the holidays, but if you find yourself in a situation where Vortex reset your LO; use this beta version to fix it.

Ok so just re-iterating what we discussed on Discord + responding to other points you raised in your original post. - The error you were getting was down to a corrupt MergeInventory.xml file which is generated by the script merger itself. The Script Merger does not write files atomically like Vortex does, which means that if interrupted during writing it can potentially corrupt the file. - The Load Order issue has been noted and fixed https://github.com/Nexus-Mods/Vortex/pull/16857 we were reluctant to release it so close to the holiday period and potentially shuffling a working environment. We've also only received 2 confirmed reports of this issue which said it only happens intermittently. Are you able to reproduce this constantly? > Edit: a beta version with the fix has been generated and can be found here: https://github.com/Nexus-Mods/Vortex-Staging/releases/download/v1.13.4-beta.1/vortex-setup-1.13.4-beta.1.exe - About the mods disappearing from the staging folder - Vortex will absolutely never remove its own mods unless instructed to do so or if an external application interferes with its functionality. A potential culprit could be that Vortex 1.13.2 was using an older version of 7zip which had a known vulnerability causing anti-virus software to go haywire. This was patched in 1.13.3 Alternatively I guess it's possible for the mods to be removed when using a cloud based service provider. Please also note that nothing in that dialog says that the mods were removed - it simply states that Vortex found and added a new folder it did not know about; (that is indeed a bug as that folder is generated by Vortex) but the mods should still be in the staging folder.

Thanks for bringing this to our attention - I'll investigate.

@7531Leonidas - that's actually intended behaviour; the conflict resolution system will wait for you to finish installing and deploying your mods before re-checking if any conflicts exist. It's an optimisation which made collection installations quicker. I can look at making the optimisation optional if it's indeed a hinderance. At the very least I think I'm going to hide that notification while installations are running.

@vortexposer I'm afraid state backups are the only method of backing up categories currently. But it shouldn't be too hard to write a quick extension that exports/imports category information. I'll add it to my work list but can't say when I'd be able to implement it.

Hey @Razor671 - judging by the snippet you sent, you're potentially using a very old version of Vortex, you can confirm the version by looking next to the window buttons at the top right. If the version is not visible, it's a clear indication of a very old Vortex version. Stable is currently 1.13.2

1.13.2 has been rolled out and will fix both categories and the inability to manage FalloutNV on machines that can't connect to Github

Thank you for the heads up - noticed this a bit too late and didn't get to add it to todays patch release; but will make sure we take care of this for the next one.

Hello all, @vortexposer the categories have not disappeared, the category list component is having issues displaying them (I'm investigating why) please do not hit the retrieve categories button as that will indeed erase any custom categories you may have created. Stick with 1.12.6 for now - 1.13.2 will fix this issue. @MrYaiba the New Vegas extension now requires the Sanity Checks extension to be installed (it should have downloaded it automatically) but if it's not installed - please download and install it manually into your %appdata%/vortex/plugins folder or by drag and dropping the archive of the extension in the extensions page https://www.nexusmods.com/site/mods/945

Hi there! It's possible that some sort of connectivity issue between your machine and our servers occurred. These type of errors are usually temporary.

Hey there @bankerlmth The fact that Vortex uses the file overrides instead of regular rules means you have a mod type conflict, probably a mod that comes in direct conflict with SKSE - easiest way to fix this, would be to install SKSE manually outside Vortex. Alternatively, you can look at the file overrides to see which mod conflicts with it and delete the SKSE file in Vortex's staging folder (the mod will replace that file). Before making any sort of changes - please make sure to purge your mods first! and only deploy once you've fixed it. Oh P.S. - please use Vortex 1.13.1 going forward as that includes some fixes to the override editor which are a must to properly debug the environment.