rmm200 Posted May 27, 2022 Share Posted May 27, 2022 In my Vortex Downloads directory, I have three Skyrim directories: skyrim, skyrimse, and skyrimvr. I never had one called skyrimspecialedition.I downloaded an SE test case from Nexusmods. As expected, it went into Vortex/Downloads/skyrimse.This is with Vortex version 1.5.13, which is current as of 5/24.I am out of ideas as to where your skyrimspecialedition came from... Link to comment Share on other sites More sharing options...
GladOfWar Posted May 27, 2022 Share Posted May 27, 2022 I'm out of ideas too , noticed it also renames the moved mods to all CAPS . a strange one . but thanks for your help Link to comment Share on other sites More sharing options...
AugustaCalidia Posted May 27, 2022 Share Posted May 27, 2022 As far as I can determine from my own experience, Vortex may have done this not only for the sake of clarity but also for the sake of collections. A couple of months ago, when I updated Vortex from v1.4.16 to v1.5.6, Vortex added two new Skyrim related folders to the downloads directory, leaving me with three populated folders for SkyrimSE. In addition to the original "skyrimse" folder I now had the folders "skyrim" (even though SkyrimLE is not installed) and "skyrimspecialedition." Puzzled, I checked to see whether this new arrangement affected Skyrim SE gameplay, what mods were displayed on the mods page, and what mods were installed in the Mod Staging Folder. Nothing whatever had changed. Even more puzzled, I examined the messages on the mods page, where I discovered an icon in the "Version" column with the message that mods so tagged were lacking identification information, thus preventing them from being updated from the mods page and being added to collections. Every archive for a mod tagged with that icon remained in the "skyrimse" folder. All the others (save one) were transferred to the "skyrimspecialedition" folder. The archive not transferred to "skyrimspecialedition" was transferred to "skyrim." That archive was a SkyrimLE mod that I had optimized for SkyrimSE several years ago. The mod was never ported to SkyrimSE. I do not think this is a bug. I suspect this folder trifurcation is the result of my using an earlier version of SkyrimSE, v1.5.97.0.8, along with an older and well aged set of mod archives. There are no problems, and everything works fine. I'm happy! :smile: Link to comment Share on other sites More sharing options...
rmm200 Posted May 27, 2022 Share Posted May 27, 2022 If it is Collections related, I have never used the Collections feature. I prefer getting in trouble on my own.This might need an observation from Tannin... We haven't bugged him recently anyway. Link to comment Share on other sites More sharing options...
GladOfWar Posted May 27, 2022 Share Posted May 27, 2022 I suspect that is the same thing that is happening to me AugustaCalidia as I am also using v1.5.97.0 version of skyrimSE as a lot of my mods are for that version. Vortex seems to be finding all the mods in the different folders so I think it is working fine apart from this strange bug .thanks for your help Link to comment Share on other sites More sharing options...
showler Posted May 27, 2022 Share Posted May 27, 2022 Version 1.5 started automatically marking SE mods as compatible with both SE and VR. Perhaps it's somehow related to that? A change in the default folder structure? Link to comment Share on other sites More sharing options...
rmm200 Posted May 27, 2022 Share Posted May 27, 2022 Version 1.5 started automatically marking SE mods as compatible with both SE and VR. Perhaps it's somehow related to that? A change in the default folder structure? Well that is a surprise. The test mod I just downloaded for SE - is also tagged Skyrim VR by Vortex.Not at all sure I like that. Maybe half of the Skyrim SE mods will work in Skyrim VR. Those that include a .esl file will not. AE mods - will not. VR is an early branch of SE.On my Skyrim VR profiles I really only want to see those mods I specifically set as VR compatible.At least give us an option somewhere. Link to comment Share on other sites More sharing options...
showler Posted May 27, 2022 Share Posted May 27, 2022 I think I saw your other post about ESLs in VR. I got the impression that they didn't know that such a problem existed when the change was made. Might require a future update to the process. edit: What do you mean by "AE mods - will not"? I didn't think there was a significant enough difference in non DLL mods to cause a problem and DLL mods needed a VR specific version anyway, did they not? edit 2: I think if you double click the mod to bring up the right side expansion window you can de-select the VR listing under the "games section" heading. Link to comment Share on other sites More sharing options...
rmm200 Posted May 27, 2022 Share Posted May 27, 2022 AE mods require a specific version of SKSE. That is about the only reason to call them an AE mod.And the AE version of SKSE will not work in VR. It depends on game engine internal addresses.Like I said, VR is very much an early branch of SE. No .esl support is part of that. And yes, you can remove the VR tag.It is just that I have hundreds of SE mods, and just a few VR mods. I am very work-averse. Link to comment Share on other sites More sharing options...
showler Posted May 27, 2022 Share Posted May 27, 2022 AE mods require a specific version of SKSE.Only the DLL type. And the same is true for SE mods that are of the DLL type. All DLL type SKSE mods need to be compiled for either SKSE 2.0.20, SKSE 2.1.5 or for SKSE VR. In most cases the DLL file itself is the only difference. For SKSE mods that just use SKSE functions in scripts and don't have a DLL, they don't really care which version of SKSE is running, as long as the functions are present for them to use. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.