Jump to content
  • 0

MO Won't run SKSE


JonasB

Question

I have the skyrim script extender loaded into the mod organizer but it won't run it. Instead it always run skyrim default. I have double-checked and the skse link uses C:\Program Files (x86)\Steam\steamapps\common\Skyrim\skse_loader.exe as the 'Binary' entry. 

 

I'm not sure if this is relevant, but whenever I try to load the nexus mod manager it gives me a message saying it can't find the skyrim.ini file, which is weird because I've run the game several times without issue and my understanding is that the .ini is generated when the game is run. Again, not sure if it's relevant, but putting it out there.

 

Any help is appreciated. 

Link to comment
Share on other sites

Recommended Posts

  • 0

I followed the instructions in https://wiki.step-project.com/Skyrim_Script_Extender and the video there to install SKSE.

 

Edit: is there any way to pure SKSE from my MO executables dropdown and start again? I ask because even after uninstalling SKSE from the mod list I cannot actually get it to vanish from the dropdown.

Edited by JonasB
Link to comment
Share on other sites

  • 0

Thanks. Anyway, reinstalled SKSE again and it's still going to the loader. SKSE is selected on the dropdown and that section is linked to skse_loader.exe, yet when I click the Run button it loads the vanilla skyrim launcher. However, if I go to the skyrim folder myself and click the skse_loader.exe then it loads skse properly. 

 

My current theory is that for whatever reason MO is /not/ in fact running skse_loader.exe when I click the Run button but is in fact trying to run vanilla skyrim/the launcher. I don't know how to test for this though. My executables dropdown currently has Skyrim, Skyrim Loader, and SKSE in it. Is there any way to remove skyrim and the loader from the dropdown to eliminate any confusion that may be occuring?

Edited by JonasB
Link to comment
Share on other sites

  • 0

Paste a link to Pastebin, or here in 

[spoiler]text[/spoiler]

 tags, your ModOrganizer.ini.

 

In that file is the settings to ALL the executables.

 

EDIT:

When you say, "the command did nothing". Are you referring to the command in the console?

Edited by GrantSP
Link to comment
Share on other sites

  • 0

In MO on the upper left side, click on the COGS button, it should bring up list on your MO executables. Click on SKSE, then at the binary "..." and navigate to your Skyrim folder and select "skse_loader.exe". Check the box for "Close MO when started". Finally click "modify". Then on the right side from the drop down menu select SKSE and click the run button.  MO should close, a small window should open, and finally Skyrim should start.

Link to comment
Share on other sites

  • 0

 

[General]

gamePath=C:\\Program Files (x86)\\Steam\\steamapps\\common\\Skyrim
motd_hash=32488014
first_start=false
selected_profile=Default
mod_list_state=@ByteArray(\0\0\0\xff\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\x6\x1\0\0\0\0\0\0\0\0\0\0\0\a(\0\0\0\x2\0\0\0\x5\0\0\0\n\0\0\0\x3\0\0\0\n\0\0\x2\x13\0\0\0\a\x1\x1\0\0\0\0\0\0\x1\0\0\0\x1\0\0\0\x14\xff\xff\xff\xff\0\0\0\x81\0\0\0\0\0\0\0\a\0\0\x1\x5\0\0\0\x1\0\0\0\0\0\0\0P\0\0\0\x1\0\0\0\0\0\0\0\x41\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\x36\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0G\0\0\0\x1\0\0\0\x1)
plugin_list_state="@ByteArray(\0\0\0\xff\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\x2\x1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x1Z\0\0\0\x4\x1\x1\0\0\0\0\0\0\x1\0\0\0\x1\0\0\0\x64\xff\xff\xff\xff\0\0\0\x81\0\0\0\0\0\0\0\x4\0\0\0\x90\0\0\0\x1\0\0\0\0\0\0\0\x32\0\0\0\x1\0\0\0\0\0\0\0;\0\0\0\x1\0\0\0\0\0\0\0]\0\0\0\x1\0\0\0\x1)"
group_state=0
ask_for_nexuspw=true
window_geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x1\0\0\0\0\0\xf9\0\0\0\x19\0\0\x4\xa6\0\0\x2\xef\0\0\x1\x1\0\0\0\x38\0\0\x4\x9e\0\0\x2\xe7\0\0\0\0\0\0)
window_split=@ByteArray(\0\0\0\xff\0\0\0\0\0\0\0\x2\0\0\x3\xde\0\0\x2\xa8\x1\0\0\0\x5\x1\0\0\0\x1)
log_split=@ByteArray(\0\0\0\xff\0\0\0\0\0\0\0\x2\0\0\x2\x62\0\0\0\x64\x1\0\0\0\x5\x1\0\0\0\x2)
browser_geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x1\0\0\0\0\0\0\0\0\0\0\0\0\x3\xef\0\0\x2\xed\0\0\0\0\0\0\0\0\0\0\x3\xef\0\0\x2\xed\0\0\0\0\0\0)
filters_visible=false
manage_bsas=true
selected_executable=1
 
[PluginPersistance]
Python%20Proxy\tryInit=false
 
[customExecutables]
1\title=SKSE
1\custom=true
1\toolbar=false
2\title=Skyrim
2\custom=false
2\toolbar=false
3\title=Skyrim Launcher
3\custom=false
3\toolbar=false
size=3
1\binary=C:/Program Files (x86)/Steam/steamapps/common/Skyrim/skse_loader.exe
1\arguments=
1\workingDirectory=
1\closeOnStart=false
1\steamAppID=72850
 
[recentDirectories]
size=2
1\name=editExecutableBinary
1\directory=C:/Program Files (x86)/Steam/SteamApps/common/Skyrim
2\name=installMod
2\directory=
 
[CompletedWindowTutorials]
InstallDialog=true
 
[servers]
CDN=@Variant(\0\0\0\b\0\0\0\x5\0\0\0\xe\0p\0r\0\x65\0m\0i\0u\0m\0\0\0\x1\0\0\0\0\x12\0p\0r\0\x65\0\x66\0\x65\0r\0r\0\x65\0\x64\0\0\0\x2\0\0\0\0\0\0\0\x10\0l\0\x61\0s\0t\0S\0\x65\0\x65\0n\0\0\0\xe\0%}\xec\0\0\0\x1a\0\x64\0o\0w\0n\0l\0o\0\x61\0\x64\0S\0p\0\x65\0\x65\0\x64\0\0\0\x6\0\0\0\0\0\0\0\0\0\0\0\x1a\0\x64\0o\0w\0n\0l\0o\0\x61\0\x64\0\x43\0o\0u\0n\0t\0\0\0\x2\0\0\0\0)

 
I'm referring to the console command, yes. It said something like an answer for the command could not be found or something.
Link to comment
Share on other sites

  • 0

I am curious as to why you think SKSE is not working? Using skse_loader.exe only shows a quick cmd window before Skyrim starts. Since you reinstalled new, you do not have any plugins using SKSE. Nagivate to your "\Users\{your user name here}\My Documents\My Games\Skyrim" folder. If SKSE is working, a SKSE directory should exist that contains all your SKSE log files. They get updated anytime you start Skyrim with SKSE.


Here is an example of the skse_loader.log file

 

 

 

skse loader 01070020 01D048CAD86CE151 6.1 (7601)
runtime root = C:\Program Files (x86)\Steam\steamapps\common\Skyrim\
config path = C:\Program Files (x86)\Steam\steamapps\common\Skyrim\Data\SKSE\skse.ini
procPath = C:\Program Files (x86)\Steam\steamapps\common\Skyrim\\TESV.exe
launching: TESV.exe (C:\Program Files (x86)\Steam\steamapps\common\Skyrim\\TESV.exe)
dwSignature = FEEF04BD
dwStrucVersion = 00010000
dwFileVersionMS = 00010009
dwFileVersionLS = 00200000
dwProductVersionMS = 00010009
dwProductVersionLS = 00200000
dwFileFlagsMask = 00000017
dwFileFlags = 00000000
dwFileOS = 00000004
dwFileType = 00000001
dwFileSubtype = 00000000
dwFileDateMS = 00000000
dwFileDateLS = 00000000
version = 0001000900200000
steam exe
hook call addr = 00F56831
load lib addr = 0106B0B4
dll = C:\Program Files (x86)\Steam\steamapps\common\Skyrim\\skse_1_9_32.dll
main thread id = 7132
hookBase = 001E0000
loadLibraryAAddr = 74AF499F
hook thread complete
launching

 

 

 

Link to comment
Share on other sites

  • 0

I am curious as to why you think SKSE is not working? Using skse_loader.exe only shows a quick cmd window before Skyrim starts. Since you reinstalled new, you do not have any plugins using SKSE. Nagivate to your "\Users\{your user name here}\My Documents\My Games\Skyrim" folder. If SKSE is working, a SKSE directory should exist that contains all your SKSE log files. They get updated anytime you start Skyrim with SKSE.

 

SKSE works fine. If I click on the loader itself from the folder then it'll run perfectly. The problem is that for whatever reason, the Mod Organizer will not run SKSE properly. When I click run, the following happens:

 

- A command window for the skse loader appears then immediately closes.

- The vanilla launcher opens

- If I go to skyrim from the vanilla launcher then skse will not run and I get an error message from skyUI. Now that skyUI is running through the organizer though, I just don't get any mods active whatsoever.

 

Here's my skse loader log too:

 

 

skse loader 01070010 01D048D4087C7DE7 6.2 (9200)

runtime root = C:\Program Files (x86)\Steam\SteamApps\common\Skyrim\
config path = C:\Program Files (x86)\Steam\SteamApps\common\Skyrim\Data\SKSE\skse.ini
procPath = C:\Program Files (x86)\Steam\SteamApps\common\Skyrim\\TESV.exe
launching: TESV.exe (C:\Program Files (x86)\Steam\SteamApps\common\Skyrim\\TESV.exe)
dwSignature = FEEF04BD
dwStrucVersion = 00010000
dwFileVersionMS = 00010009
dwFileVersionLS = 00200000
dwProductVersionMS = 00010009
dwProductVersionLS = 00200000
dwFileFlagsMask = 00000017
dwFileFlags = 00000000
dwFileOS = 00000004
dwFileType = 00000001
dwFileSubtype = 00000000
dwFileDateMS = 00000000
dwFileDateLS = 00000000
version = 0001000900200000
steam exe
hook call addr = 00F56831
load lib addr = 0106B0B4
dll = C:\Program Files (x86)\Steam\SteamApps\common\Skyrim\\skse_1_9_32.dll
main thread id = 19184
hookBase = 001C0000
loadLibraryAAddr = 7523A669
hook thread complete
launching

Edited by JonasB
Link to comment
Share on other sites

  • 0

Did you rename your existing ModOrganizer.ini and let MO generate a new one? That ini doesn't look like a vanilla one.

If all the executables are configured correctly, MO will automatically find and use them with no need to change any settings at all. This will give you an ini like this one:

 

 

[General]
gamePath=C:\\Program Files (x86)\\Steam\\steamapps\\common\\Skyrim
motd_hash=32488014
first_start=false
selected_profile=Default
mod_list_state=@ByteArray(\0\0\0\xff\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\x6\x1\0\0\0\0\0\0\0\0\0\0\0\a(\0\0\0\x2\0\0\0\x5\0\0\0\n\0\0\0\x3\0\0\0\n\0\0\x2\x2\0\0\0\a\x1\x1\0\0\0\0\0\0\x1\0\0\0\x1\0\0\0\x14\xff\xff\xff\xff\0\0\0\x81\0\0\0\0\0\0\0\a\0\0\0\xb3\0\0\0\x1\0\0\0\0\0\0\0P\0\0\0\x1\0\0\0\0\0\0\0s\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0V\0\0\0\x1\0\0\0\0\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\x36\0\0\0\x1\0\0\0\x1)
plugin_list_state="@ByteArray(\0\0\0\xff\0\0\0\0\0\0\0\x1\0\0\0\0\0\0\0\x2\x1\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\x1I\0\0\0\x4\x1\x1\0\0\0\0\0\0\x1\0\0\0\x1\0\0\0\x64\xff\xff\xff\xff\0\0\0\x81\0\0\0\0\0\0\0\x4\0\0\0\x90\0\0\0\x1\0\0\0\0\0\0\0\x32\0\0\0\x1\0\0\0\0\0\0\0;\0\0\0\x1\0\0\0\0\0\0\0L\0\0\0\x1\0\0\0\x1)"
group_state=0
ask_for_nexuspw=true
window_geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x1\0\0\0\0\0\xd4\0\0\0\n\0\0\x4\x81\0\0\x2\xf5\0\0\0\xdc\0\0\0(\0\0\x4y\0\0\x2\xed\0\0\0\0\0\0)
window_split=@ByteArray(\0\0\0\xff\0\0\0\0\0\0\0\x2\0\0\x3\xde\0\0\x2\xa8\x1\0\0\0\x5\x1\0\0\0\x1)
log_split=@ByteArray(\0\0\0\xff\0\0\0\0\0\0\0\x2\0\0\x2\x62\0\0\0\x64\x1\0\0\0\x5\x1\0\0\0\x2)
browser_geometry=@ByteArray(\x1\xd9\xd0\xcb\0\x1\0\0\0\0\0\0\0\0\0\0\0\0\x3\xef\0\0\x2\xed\0\0\0\0\0\0\0\0\0\0\x3\xef\0\0\x2\xed\0\0\0\0\0\0)
filters_visible=false
manage_bsas=true
selected_executable=1
 
[PluginPersistance]
Python%20Proxy\tryInit=false
 
[customExecutables]
1\title=SKSE
1\custom=false
1\toolbar=false
2\title=Skyrim
2\custom=false
2\toolbar=false
3\title=Skyrim Launcher
3\custom=false
3\toolbar=false
4\title=Creation Kit
4\custom=false
4\toolbar=false
size=4
 
[recentDirectories]
size=0

 
Notice the SKSE setting has no path to binary set as MO just uses the defaults. This works in all instances that these executables are installed correctly.
 
I'm also curious about that SteamAppID. Are you using some form of steam_appid.txt to get around using the launcher?
I can see no reason why you will need to use that method if you are. Simply delete that file and let Skyrim start as it needs to.
Remember Steam doesn't need to check your game for mods installed anymore so there is no need to have it online either. Try it offline and see if there is anything you miss.
Link to comment
Share on other sites

  • 0

Try this:

 

Copy Skyrim.ini and SkyrimPrefs.ini from the Documents folder (Documents/My Games/Skyrim) and paste them into your Mod Organizer's profile folder (Steam/SteamApps/common/Skyrim/Mod Organizer/profiles/<Name of profile you are using>/ - overwrite when asked.

Link to comment
Share on other sites

  • 0

 

SKSE works fine. If I click on the loader itself from the folder then it'll run perfectly. The problem is that for whatever reason, the Mod Organizer will not run SKSE properly. When I click run, the following happens:

 

- A command window for the skse loader appears then immediately closes.

- The vanilla launcher opens

- If I go to skyrim from the vanilla launcher then skse will not run and I get an error message from skyUI. Now that skyUI is running through the organizer though, I just don't get any mods active whatsoever.

 

Here's my skse loader log too:

 

 

skse loader 01070010 01D048D4087C7DE7 6.2 (9200)

runtime root = C:\Program Files (x86)\Steam\SteamApps\common\Skyrim\
config path = C:\Program Files (x86)\Steam\SteamApps\common\Skyrim\Data\SKSE\skse.ini
procPath = C:\Program Files (x86)\Steam\SteamApps\common\Skyrim\\TESV.exe
launching: TESV.exe (C:\Program Files (x86)\Steam\SteamApps\common\Skyrim\\TESV.exe)
dwSignature = FEEF04BD
dwStrucVersion = 00010000
dwFileVersionMS = 00010009
dwFileVersionLS = 00200000
dwProductVersionMS = 00010009
dwProductVersionLS = 00200000
dwFileFlagsMask = 00000017
dwFileFlags = 00000000
dwFileOS = 00000004
dwFileType = 00000001
dwFileSubtype = 00000000
dwFileDateMS = 00000000
dwFileDateLS = 00000000
version = 0001000900200000
steam exe
hook call addr = 00F56831
load lib addr = 0106B0B4
dll = C:\Program Files (x86)\Steam\SteamApps\common\Skyrim\\skse_1_9_32.dll
main thread id = 19184
hookBase = 001C0000
loadLibraryAAddr = 7523A669
hook thread complete
launching

 

Based on your log SKSE is starting steam correctly. Navigate to your "MO\mods\[skyrim Script Extender}" folder, this is where you installed you SKSE Data folder. If done currently, should see a "scripts" folder, "meta.ini", and a "SKSE" folder. Note the the SKSE archive does not have a "SKSE" folder, this is something you have to create and it contains the "SKSE.ini" which you also have to create yourself. As stated by monkeycid, the Skyrim.ini and SkyrimPrefs.ini are stored in "MO\profiles\{name of your profile}". When using MO, the first thing to do is create a new profile. This will automatically copy the INI files into your new profile. Call the name profile whatever you want. After you created your profile, select the Default profile and click REMOVE and YES when ask. The name profile will have all your mods in the left pane and may need to be activated by checking the box to the left and sorting them into proper order by dragging.

 

If you have done all of the above, based on your log file, you may not be properly installing mods using MO. To verify you installed SkyUI correctly, navigate to "MO\mods\SkyUI". You should see the following:

 

interface folder

scripts folder

meta.ini

Readme - SkyUI.txt

SkyUI.esp

 

If the Readme file isn't showing *.txt, your are hiding known file extensions, and it is likely you created a SKSE.ini.txt instead of SKSE.ini when you created that file. Hope it helps.

Edited by DanimalTwo
Link to comment
Share on other sites

  • 0

Danimal: My SkyUI folder in MO has the following: meta.ini, the readme, the bsa, and the esp. I installed SkyUI by downloading it from nexus and double clicking it in the downloads section of MO and then clicking Ok.

 

GrantSP: I don't remember whether the binary line just came like that or if I did something to set it in the past. The steamapp ID is actually the same as the default one MO is using, but I put it in anyway in an attempt at earlier problem solving. I am also not doing anything to 'get around the launcher'. What I said about using skse directly from the skyrim folder was merely something I did to confirm that skse itself was working fine. My problem is still that MO keeps trying to run the skyrim launcher instead. I'm also getting kind of confused now. I'd really appreciate if you could tell me what I should do in a step by step manner (1, 2, 3, etc.) if only for my own peace of mind.

Link to comment
Share on other sites

  • 0

For step by step instructions follow this guide for Skyrim Revisited: Legendary Edition. It will take you through configuring MO, creating your first profile, etc. Instead of using 'Skyrim Revisited' as the profile name consider, using 'Skyrim Base Install'. Follow the guide carefully up until the creating the 'The Dovahkiin Comes' section. You can skip the ENB section, but you may want ENBoost. Once you have completed the install through creating the 'The Dovahkiin Comes' section, copy the 'Skyrim Base Install' creating a new profile (for example STEP, SRLE, or whatever you want) to build upon. Everytime, you want a different profile copy the 'Skyrim Base Install' as your starting point.

Edited by DanimalTwo
Link to comment
Share on other sites

  • 0

No offense but... that sounds like far more confusing than what I need. I just want some clear advice since I'm getting multiple people suggesting different things and I don't know how much overlaps with what. So far I have renamed/generated a new MO .ini file, I have created an SKSE folder and SKSE.ini in the relevant place, and have made a new profile on MO and it still keeps going to the vanilla skyrim launcher. 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.