Jump to content

Photo

SKSE64 in Vortex vs MO

skse64 skyrimse skyrim se

  • Please log in to reply
8 replies to this topic

#1

    Stranger

  • Account closed
  • Pip
  • 8 posts

When installing SKSE in Mod Organizer, after adding the executables to the Skyrim folder, you had to point Mod Organizer to the Data folder or you received a "No game data on top level" error. When installing SKSE64 with Vortex, do I need to package the Scripts separately and install them, or can I just install the "mod" from the original archive and let Vortex find the scripts?

 

Edit: I simply installed it from the archive and was able to get a a version number when using the GetSKSEVersion command. Will this matter in the long run, or should I go ahead and repackage the scripts separately?



#2
rmm200

rmm200

    Faithful poster

  • Members
  • PipPipPipPip
  • 1,981 posts

After adding the executables to the base directory, I have always just added the archive to Vortex as a mod.

Works for me - and I guarantee the scripts wind up in the right place.



#3

    Stranger

  • Account closed
  • Pip
  • 8 posts

I'll probably just keep it that way then. I highly doubt it would mess anything up, but it never hurts to double check.

 

Edit: New issue. Whenever I try running Skyrim with SKSE from within Vortex I receive a "Couldn't find SkyrimSE.exe" error. I selected edit and the following is stated:

 

Target: D:\Steam\steamapps\common\Skyrim Special Edition\Data\skse64_2_00_11\skse64_loader.exe

Start In: D:\Steam\steamapps\common\Skyrim Special Edition\Data\skse64_2_00_11\src\skse64\skse64_loader

 

I've set SKSE to be default, but vanilla SkyrimSE is run whenever I use the desktop icon. I feel like one of these settings is wrong (leaning towards the Start In path).



#4
AugustaCalidia

AugustaCalidia

    Mayor of Talos Plaza

  • Premium Member
  • 2,318 posts

When installing SKSE in Mod Organizer, after adding the executables to the Skyrim folder, you had to point Mod Organizer to the Data folder or you received a "No game data on top level" error. When installing SKSE64 with Vortex, do I need to package the Scripts separately and install them, or can I just install the "mod" from the original archive and let Vortex find the scripts?

 

Edit: I simply installed it from the archive and was able to get a a version number when using the GetSKSEVersion command. Will this matter in the long run, or should I go ahead and repackage the scripts separately?

 

You may find this Vortex Knowledge Base article Interesting: https://wiki.nexusmo...cript_Extenders.

 

Personally, I like to install script extenders manually in the manner rmm200 described.



#5

    Stranger

  • Account closed
  • Pip
  • 8 posts

 

When installing SKSE in Mod Organizer, after adding the executables to the Skyrim folder, you had to point Mod Organizer to the Data folder or you received a "No game data on top level" error. When installing SKSE64 with Vortex, do I need to package the Scripts separately and install them, or can I just install the "mod" from the original archive and let Vortex find the scripts?

 

Edit: I simply installed it from the archive and was able to get a a version number when using the GetSKSEVersion command. Will this matter in the long run, or should I go ahead and repackage the scripts separately?

 

You may find this Vortex Knowledge Base article Interesting: https://wiki.nexusmo...cript_Extenders.

 

Personally, I like to install script extenders manually in the manner rmm200 described.

 

 

Thanks. I gave it a brief glance, but I don't think I like the way it explains to do it. It mentiones putting the executables in the same folder as the Scripts. I typically do it like rmm200 does as well. I added the executable to the base Skyrim SE directory, and then added the archive as a mod. I'll probably just delete the mod and executables and start from scratch.



#6
rmm200

rmm200

    Faithful poster

  • Members
  • PipPipPipPip
  • 1,981 posts

I'll probably just keep it that way then. I highly doubt it would mess anything up, but it never hurts to double check.

 

Edit: New issue. Whenever I try running Skyrim with SKSE from within Vortex I receive a "Couldn't find SkyrimSE.exe" error. I selected edit and the following is stated:

 

Target: D:\Steam\steamapps\common\Skyrim Special Edition\Data\skse64_2_00_11\skse64_loader.exe

Start In: D:\Steam\steamapps\common\Skyrim Special Edition\Data\skse64_2_00_11\src\skse64\skse64_loader

 

I've set SKSE to be default, but vanilla SkyrimSE is run whenever I use the desktop icon. I feel like one of these settings is wrong (leaning towards the Start In path).

 

Your problem is your Target and your Start In. Both of them have to point to the base game directory. Let me try an edit here:

Target: D:\Steam\steamapps\common\Skyrim Special Edition\skse64_loader.exe

Start In: D:\Steam\steamapps\common\Skyrim Special Edition\


Edited by rmm200, 08 December 2018 - 03:46 AM.


#7

    Stranger

  • Account closed
  • Pip
  • 8 posts

 

I'll probably just keep it that way then. I highly doubt it would mess anything up, but it never hurts to double check.

 

Edit: New issue. Whenever I try running Skyrim with SKSE from within Vortex I receive a "Couldn't find SkyrimSE.exe" error. I selected edit and the following is stated:

 

Target: D:\Steam\steamapps\common\Skyrim Special Edition\Data\skse64_2_00_11\skse64_loader.exe

Start In: D:\Steam\steamapps\common\Skyrim Special Edition\Data\skse64_2_00_11\src\skse64\skse64_loader

 

I've set SKSE to be default, but vanilla SkyrimSE is run whenever I use the desktop icon. I feel like one of these settings is wrong (leaning towards the Start In path).

 

Your problem is your Target and your Start In. Both of them have to point to the base game directory. Let me try an edit here:

Target: D:\Steam\steamapps\common\Skyrim Special Edition\skse64_loader.exe

Start In: D:\Steam\steamapps\common\Skyrim Special Edition\

 

 

rmm200, you're a boss! This is why I love the modding community. I knew the Start In path was wrong immediately, so I had already changed that. But I have no idea where that Target path came from. Doesn't really matter now, it works. I went ahead and created a SKSE shortcut on my Desktop and switched its icon. Everything should be relatively smooth sailing moving forward.



#8
rmm200

rmm200

    Faithful poster

  • Members
  • PipPipPipPip
  • 1,981 posts

 

 

... 

 

rmm200, you're a boss! This is why I love the modding community. I knew the Start In path was wrong immediately, so I had already changed that. But I have no idea where that Target path came from. Doesn't really matter now, it works. I went ahead and created a SKSE shortcut on my Desktop and switched its icon. Everything should be relatively smooth sailing moving forward.

 

 

:happy:



#9
AugustaCalidia

AugustaCalidia

    Mayor of Talos Plaza

  • Premium Member
  • 2,318 posts

 

Thanks. I gave it a brief glance, but I don't think I like the way it explains to do it. It mentiones putting the executables in the same folder as the Scripts. I typically do it like rmm200 does as well. I added the executable to the base Skyrim SE directory, and then added the archive as a mod. I'll probably just delete the mod and executables and start from scratch.

 

 

If you read the article closely, you'll see that it does not put the executables in the same folder as the Scripts.  Here's the key sentence: "You should now have a Data folder (containing the scripts), 2 DLL files and an EXE file on the top level" (emphasis mine).  However, a quick reading of that sentence could leave you with the impression that everything is bundled into the Scripts folder, especially if you don't understand what "on the top level" means.

 

Anyway, I think rmm200's installation method is quicker and less confusing.  That's why I use it.  I'm glad your problem's solved, thanks to his good advice.







Also tagged with one or more of these keywords: skse64, skyrimse, skyrim se

Page loaded in: 1.066 seconds