Vortex moved some SKSE64 plugins to root folder

[dtrail]

Hi @all,

 

yesterday I've discovered something weird. When I was updating a mod, I was browsing through the folders, and suddenly noticed that some of my SKSE64 plugins were moved from their actual folder (Data/SKSE/Plugins/) to the SSE root folder. There were 13 of them, to be more specific. I know absolutely for sure, that they were installed properly before, and I just cannot imagine why they were suddenly sitting in the root folder. I tried to find other reports with similar topics, but couldn't find any, so I thought I'd report it here.

I simply moved them back manually and tripple checked that everything is right in place. Vortex actually did not even notice that! It never prompted about "external changes" and if I'd like to save/restore them, like it usually does, when changing any file inside /Data/...

And while I'm writing this, I remember that I noticed a similar problem once: Some SKSE64 plugins were just missing after the installation. I just re-installed them entirely via Vortex then, and except that a lot of the pluguns suddenly sit somewhere else, I didn't have any problems. But both of the mentioned situations occured once, and I think I should ask you guys, if anyone else experienced this, or could this be - by any chance - a bug I've discovered?

 

Thx

[HadToRegister]

Where is your Mod Staging Folder and where is your downloads folder?

[dtrail]

Both in seperate directory on the same drive, also the game is on the same drive. I did a lot of reading before using Vortex to avoid issues (where it's possible). But of course I could have done something wrong.

[HadToRegister]

Both in seperate directory on the same drive, also the game is on the same drive. I did a lot of reading before using Vortex to avoid issues (where it's possible). But of course I could have done something wrong.

 

Hey, good on you, we like to hear in these forums when people spend some time reading the manual :)

 

I'm going to have to say though, this one might have me stumped, you say they were working fine one day, and the next day, they're all mysteriously in the root folder now.

That IS weird.

 

I personally have not experienced it, and it seems like such a fluke I'm wondering if you could even find a way to reproduce it again.

(If you do, please send it through the bug report form built into Vortex)

 

I don't think any AV software would do that, because if it saw any of those DLLs as a threat, it would've gotten rid of them or quarantined them, and definitely wouldn't have moved them to your game root folder

 

Hmmm, I wonder if any of the Vortex LOGS would show anything of significance.

 

Try clicking on the 3 vertical dots next to your avatar in Vortex and pick "Diagnostic FIles" from there you can pick the date range of the log, and once you open the log, you can also check off the boxes the filter out "INFO", WARNING, and ERROR text.

There's also a DEBUG text option, that might take a while to load the text

[dtrail]

 

Both in seperate directory on the same drive, also the game is on the same drive. I did a lot of reading before using Vortex to avoid issues (where it's possible). But of course I could have done something wrong.

 

Hey, good on you, we like to hear in these forums when people spend some time reading the manual :smile:

 

I'm going to have to say though, this one might have me stumped, you say they were working fine one day, and the next day, they're all mysteriously in the root folder now.

That IS weird.

 

I personally have not experienced it, and it seems like such a fluke I'm wondering if you could even find a way to reproduce it again.

(If you do, please send it through the bug report form built into Vortex)

 

I don't think any AV software would do that, because if it saw any of those DLLs as a threat, it would've gotten rid of them or quarantined them, and definitely wouldn't have moved them to your game root folder

 

Hmmm, I wonder if any of the Vortex LOGS would show anything of significance.

 

Try clicking on the 3 vertical dots next to your avatar in Vortex and pick "Diagnostic FIles" from there you can pick the date range of the log, and once you open the log, you can also check off the boxes the filter out "INFO", WARNING, and ERROR text.

There's also a DEBUG text option, that might take a while to load the text

 

Thx for the suggestions, I will do that right now.

 

Well, I figured out that the SKSE plugins were not sitting in their right place, when I started to expreicne sudden crashes on a fresh game, mostly when I tried to save my game. I'm using a mod for safer savegame creation, that relies partly on a SKSE plugin.This plugin was sitting in the root folder, together with 12 others (out of 33 alltogether), so it wasn't all of them.

But the first thing I thought, when it crashed the first time, was that something might be wrong with my setup. So I started checking my entire load order for potential conflicts via xEdit, uninstalled some less necessary and script heavy mods (as I thought it might be due to an overloaded Papyurs VM. One mod caused the active script count in my savegames to be quite high under certain conditions) and tripple checked everything again and patched every little conflict, even those that aren't important. Then I started another fresh, new game. But the problem persisted. This led me to think about checking the game's folders, and then I figured that 13 SKSE plugins were actually not sitting in their proper directory, but in my SSE root folder. After I've moved them back, the crashes stopped immediately.

 

And one time I noticed that some SKSE plugins were just not installed - right after the installation with Vortex. I simply re-installed them, and it was fine. That's why I didn't think about it no longer. But now, with this weird behavior, I always check my SKSE plugins folder and the SSE root folder for "magically" moved plugins xD

 

On the other hand I never had such a problem with the other games I'm modding with Vortex (Fallout 4 and F:NV). I also browsed the Vortex manualls, forums and Google, but couldn't find anything related to this "problem". I'm pretty sure that it's configured the right way. I will take those logs now and hope this can help to find the cause. In case that it's something on my side, I apologize . But then I will at least have learned something new :smile:

 

Edit: I found them. They're definately from the right times, but I couldn't find anything pointing to the SKSE folder or to DLL files. And only 3 of the logs contain 1 - 3 errors, each one being a minor one about FNIS generation tool (nothing bad, really). If you want, I'll post them into a spoiler. But they don't help at all...

Edited April 28, 2019 by dtrail

[HadToRegister]

 

 

On the other hand I never had such a problem with the other games I'm modding with Vortex (Fallout 4 and F:NV). I also browsed the Vortex manualls, forums and Google, but couldn't find anything related to this "problem". I'm pretty sure that it's configured the right way. I will take those logs now and hope this can help to find the cause. In case that it's something on my side, I apologize . But then I will at least have learned something new :smile:

 

Edit: I found them. They're definately from the right times, but I couldn't find anything pointing to the SKSE folder or to DLL files. And only 3 of the logs contain 1 - 3 errors, each one being a minor one about FNIS generation tool (nothing bad, really). If you want, I'll post them into a spoiler. But they don't help at all...

 

Hmmm, I guess you'll have to write this one off as a fluke for now, unless it happens again.

If it DOES happen again, hopefully it will be caused by the same conditions as the first time, so that you can reproduce the problem, so Tannin42 can look into it and fix it if there's a problem.

 

Also, it's great to see someone willing to do some legwork in order to solve their problems :)

 

Let's hope it was a one-time thing.

 

Good Luck!

[dtrail]

Hi, it's me again :)

 

Actually my new post doesn't fit to the thread's title. And because I didn't want to open up a new one, I've posted into another thread, named "problems with Vortex". However, someone told me that I should open up a new thread to get a good answer, so I decided to continue my own thread here.

 

In the past few months using Vortex I've encountered only a few issues, moslty nothing too bad. However, there are also some things that seem to be quite odd with my Skyrim SE installation. There was the case, that Vortex moved some of my SKSE plugins, that I had installed, to the SSE root folder. This did not happen anymore. Just wanted to mention it. But now I discovered something more weird. I'm using the AGO mod (Archery Gameplay Overhaul). And I noticed that a certain feature didn't work. So I re-installed the mod multiple times and tried some things, but to no avail. It still didn't work. But today I just had a look at the scripts folder, compared it to the mod's files and figured out that a few scripts were just missing (in my SSE scripts directory). After taken a closer look I saw that Vortex only installed the scripts from that mod's translation, that I've installed afterwards and set a rule to overwrite all related files from the original mod. But instead just overwriting the necessary files and keeping the rest of them untouched, Vortex just removed those and only left the translated (overwritten) ones in the folder. Of course the mod could't work properly with several missing scripts. Well, a simple re-install of the mod fixed this. But now I'm really unsure about my entire mod setup. What if there are other files missing? And how could I figure that with an amount of more than 8000 script files (or even a few hundrets of thousands files in total, when I'm not only looking at scripts..) ?

As far as I can tell, my game runs fine and stable. I will just keep an eye on it, and if I should notice more weird behavior, I'll check the related mod and its files. In case I find more of them, I'll report it here. Also I'm thinking this "problem" might be known already and got fixed in one of the recent updates, because this time the re-installation of AGO worked fine. But when I tried this a few weeks back, it did not.

 

However, I don't know what's going on. Vortex is by far much better than NMM ever was. It's fast, super-easy to use and convenient. But sometimes weird things happen and my report hopefully will help to find such issuesd and fix them.

[HadToRegister]

Are you running Windows Defender or some other AV program?

I'm wondering if an AV program is glitching your installs because it's flagging some files and not others.

[dtrail]

I'm using ESET and MBAM. But I put my Vortex and SSE folders into the exception rules long before installing any mod. And I never noticed any of my security applications performing any action to Vortex or my games. Also there's nothing in the logs that would lead to that conclusion.

I have a theory though: SOmetimes I performed mutliple operations in Vortex, like installing, updating and removing mods. I did it one by one, but didn't always wait until it finished the current operation. In my Vortex settings I had auto-deploy enabled, so it always automatically started deploying immediately when I changed something. I suspect Vortex to confuse things when I work too fast. For example: I click on disable a certain mod - Vortex starts operating the given task - and then I click to start the installation another mod, although it was still performing the prior task. I thought that Vortex would actually kinda stack given tasks, so I wouldn't have to wait until it finishes every single action first. FInally I disabled automatic deployment and now I just finish all actions one by one and finally click deploy manually. However, my game was completely stable, and recently started to crash randomly. As mentioned one reason for crashes was a missing script, like described in my prior post. About the other crashes I'm unsure. I guess I should reinstall my entire mod setup and make sure that it deploys everything properly. Crashes still happen very rare, but they do, and I just cannot tell if there's anything missing or not. There are simply too many mods and files to cover.

 

Edit: By the way, my setup is well maintained. I'm using xEdit, CK, Wrye Bash, etc. to keep my load order clean and free of bad conlicts. I'm doing this for a very long time now and I know how to create stable mod setup. Usually when I finish a mod build, I'm able to play through the entire game without stability or crashing issues. My save files are not corrupted at all, the script instances, strings and all of that are not even close to any dangerous limit. The crashes happen - even though rare - randomly and mostly not reproducible. And because the game doesn't hit any limit, not in the savegames, not in RAM or graphical instances, etc. I think the most obvious reason could be some mods that aren't installed properly - like the last example - IF there isn't a mod containing any yet undiscovered bug that causes it. That's the problem with big mod lists. You can never really know if all f them are free of such bugs. AT the end I just might messes it up myself, because I handled Vortex wrong.

Edited June 27, 2019 by dtrail

[HadToRegister]

I'm using ESET and MBAM. But I put my Vortex and SSE folders into the exception rules long before installing any mod. And I never noticed any of my security applications performing any action to Vortex or my games. Also there's nothing in the logs that would lead to that conclusion.

I have a theory though: SOmetimes I performed mutliple operations in Vortex, like installing, updating and removing mods. I did it one by one, but didn't always wait until it finished the current operation. In my Vortex settings I had auto-deploy enabled, so it always automatically started deploying immediately when I changed something. I suspect Vortex to confuse things when I work too fast. For example: I click on disable a certain mod - Vortex starts operating the given task - and then I click to start the installation another mod, although it was still performing the prior task. I thought that Vortex would actually kinda stack given tasks, so I wouldn't have to wait until it finishes every single action first. FInally I disabled automatic deployment and now I just finish all actions one by one and finally click deploy manually. However, my game was completely stable, and recently started to crash randomly. As mentioned one reason for crashes was a missing script, like described in my prior post. About the other crashes I'm unsure. I guess I should reinstall my entire mod setup and make sure that it deploys everything properly. Crashes still happen very rare, but they do, and I just cannot tell if there's anything missing or not. There are simply too many mods and files to cover.

 

Edit: By the way, my setup is well maintained. I'm using xEdit, CK, Wrye Bash, etc. to keep my load order clean and free of bad conlicts. I'm doing this for a very long time now and I know how to create stable mod setup. Usually when I finish a mod build, I'm able to play through the entire game without stability or crashing issues. My save files are not corrupted at all, the script instances, strings and all of that are not even close to any dangerous limit. The crashes happen - even though rare - randomly and mostly not reproducible. And because the game doesn't hit any limit, not in the savegames, not in RAM or graphical instances, etc. I think the most obvious reason could be some mods that aren't installed properly - like the last example - IF there isn't a mod containing any yet undiscovered bug that causes it. That's the problem with big mod lists. You can never really know if all f them are free of such bugs. AT the end I just might messes it up myself, because I handled Vortex wrong.

 

 

Are you forcing a load order on Vortex, through WryeBash?