Jump to content

[WIPz] Skyrim Script Extender (SKSE64)


ianpatt

Recommended Posts

 

 

Gee, that's really helpful, saying "lol no it works meng".

 

I am having the same problem. Tried with both NMM, direct launch, and ModDrop even. No dice. The command box for SKSE pops up, immediately disappears, and then.....................................

 

NOTHING.

 

I can't provide much help, because I don't know anything about how the other user installed it (aside from a Gopher vid ref).

What I can do is assert it should be possible to correct, by demonstrating it working with the same build #.

I can provide info about my install, in case it helps provide clues as to what the difference could be.

 

 

In my case, it tries to launch, get the typical black box, but, the blue Win10 mini blue circle of death just keeps spinning periodically, like it is trying to load more but just can't... hey, why not type about a technical issue in poetic human terms...

 

...in the end, it'll be something simple I overlooked, reviewing Gopher's words of wisdom stll isn't helping sadly -- and the man is good.

 

 

Loaded via Nexus MM by letting NMM pull the SKSE data file in as a .rar file.

 

 

My install I have Steam installed to C:\Program Files (x86)\Steam\ but I have steam data on E:\Games\Steam\.

 

My first two thoughts are:

1\ Make sure your Skyrim build is 1.5.23 (this is the ver you can see in File Properties through Windows, 1.5.23.08 is the full build # visible inside Skyrim SE itself)

2\ Make sure you've only got the Alpha build of SKSE64 2.0.6 and didn't accidentally leave the 2.0.4 launcher exe in the Skyrim SE folder

^ if the build #'s aren't aligned then it wont work.

 

3\ Try without any mod manager 'handling' SKSE for you

^ Honestly I almost never run Beth games without using a manager, but the entirety of SKSE (of F4SE, or any other script extender) is always installed, so even if I'm running vanilla Skyrim SE the SKSE is there. When I started using SKSE64 I installed everything manually, then checked it ran with vanilla Skyrim SE, no mods or anything but just to demonstrate it had hooked in and the 'GetSKSEVersion' command would run from console. And, to be fair, the first time I tried - it did not work. The game didn't crash, or anything, it just didn't load SKSE (I'd had version mismatch between Skyrim SE and SKSE64).

 

4\ If possible move Steam data out of C:\Program Files (x86)\.

^ If you've got Steam still storing all games in that folder then there's a chance that Windows UAC or antimalware might be interfering I suppose.

 

disclaimer: I actually do software support as my day job, but I don't support SKSE64. I can provide some guidance based on things I can see that could go wrong, but honestly I've never had too much trouble personally getting SKSE working so exposure to actual issues beyond theoretical is limited.

 

1. Yes, that's correct. 1.5.23.

2. And yes, it's the correct build of SKSE64. Alpha 0.6. If I used an earlier version, the box stays up and tells me to update to a newer version. So I know this is the right version.

3. I already tried that. I specifically mentioned direct launch, as in, directly launching the executable.

4. Yes, all my games get installed in there. I don't have 2 drives. I've already tried disabling antivirus and UAC.

Edited by Falloutdude11
Link to comment
Share on other sites

  • Replies 351
  • Created
  • Last Reply

Top Posters In This Topic

 

My install I have Steam installed to C:\Program Files (x86)\Steam\ but I have steam data on E:\Games\Steam\.

4\ If possible move Steam data out of C:\Program Files (x86)\.

^ If you've got Steam still storing all games in that folder then there's a chance that Windows UAC or antimalware might be interfering I suppose.

4. Yes, all my games get installed in there. I don't have 2 drives. I've already tried disabling antivirus and UAC.

 

 

I think he means to just move it out of C:\Program Files (x86)\

 

I have mine installed in C:\Games\Steam\

Edited by jwagne51
Link to comment
Share on other sites

 

 

My install I have Steam installed to C:\Program Files (x86)\Steam\ but I have steam data on E:\Games\Steam\.

4\ If possible move Steam data out of C:\Program Files (x86)\.

^ If you've got Steam still storing all games in that folder then there's a chance that Windows UAC or antimalware might be interfering I suppose.

4. Yes, all my games get installed in there. I don't have 2 drives. I've already tried disabling antivirus and UAC.

 

 

I think he means to just move it out of C:\Program Files (x86)\

 

I have mine installed in C:\Games\Steam\

 

Isn't there a steam loader dll built in, that forces it to be in the proper steam folder?

 

EDIT: Nevermind. Didn't work.

Edited by Falloutdude11
Link to comment
Share on other sites

 

 

 

My install I have Steam installed to C:\Program Files (x86)\Steam\ but I have steam data on E:\Games\Steam\.

4\ If possible move Steam data out of C:\Program Files (x86)\.

^ If you've got Steam still storing all games in that folder then there's a chance that Windows UAC or antimalware might be interfering I suppose.

4. Yes, all my games get installed in there. I don't have 2 drives. I've already tried disabling antivirus and UAC.

 

 

I think he means to just move it out of C:\Program Files (x86)\

 

I have mine installed in C:\Games\Steam\

 

Isn't there a steam loader dll built in, that forces it to be in the proper steam folder?

 

EDIT: Nevermind. Didn't work.

 

 

What I mean is that I installed Steam, in its entirety, in the Games folder instead of Program Files (x86).

Link to comment
Share on other sites

@IanPatt

 

Hi, will try to keep this short, but if you want a long winded post on the same subject refer to this post on STEP Forum

 

Can SKSE be made to wait a little longer for SKSE plugins to load. In the case where the Steam Client is NOT being loaded as part of Windows startup, if we launch SKSE64 2.06 from a desktop icon, the chain loading of everything that needs to load (including booting up the steam client) seems to be not initiating PapyrusUTIL v3.4 in my case, quick enough for DynDOLOD to have it ready by the time its plugin loads in game.

 

(I am guessing the sequence of events, and taking a bit of a stab in the dark as to the probable cause .. But if I already have the steam client running before I load SKSE64, then there are no issues and DynDOLOD finds PapyrusUTIL resources are in place and loads fine)

 

 

Edit : Looking at the Logs -

 

If Steam Client is not running when I launch SKSE64, then only two logs are created

 

SKSE64_Loader.log

 

 

skse64 loader 02000060 01D393DEDB150C34 6.2 (9200)
config path = D:\Steam\steamapps\Common\Skyrim Special Edition\Data\SKSE\skse.ini
procPath = D:\Steam\steamapps\Common\Skyrim Special Edition\\SkyrimSE.exe
launching: SkyrimSE.exe (D:\Steam\steamapps\Common\Skyrim Special Edition\\SkyrimSE.exe)
dwSignature = FEEF04BD
dwStrucVersion = 00010000
dwFileVersionMS = 00010000
dwFileVersionLS = 00000000
dwProductVersionMS = 00010000
dwProductVersionLS = 00000000
dwFileFlagsMask = 00000017
dwFileFlags = 00000000
dwFileOS = 00000004
dwFileType = 00000001
dwFileSubtype = 00000000
dwFileDateMS = 00000000
dwFileDateLS = 00000000
productVersionStr = 1.5.23.0
version = 0001000500170000
product name = TESV: Skyrim
steam exe
dll = D:\Steam\steamapps\Common\Skyrim Special Edition\\skse64_1_5_23.dll
main thread id = 7416
hookBase = 000001FFEC440000
loadLibraryAAddr = 00007FFC9EE113F0
hook thread complete
launching

 

 

and ..

 

SKSE64_Steam_Loader.log

 

 

skse64 loader 02000060 (steam) 01D393DEDB1A30BE 6.2 (9200)
loader base addr = 00007FFC7D2D0000
exe base addr = 00007FF63E540000
found iat at 00007FF63FA62898
original thunk 00007FFC8D2B1000
patched iat
HookMain: thread = 7416 retaddr = 00007FF63F8A1DE9
runtimePath = D:\Steam\steamapps\Common\Skyrim Special Edition\SkyrimSE.exe
dwSignature = FEEF04BD
dwStrucVersion = 00010000
dwFileVersionMS = 00010000
dwFileVersionLS = 00000000
dwProductVersionMS = 00010000
dwProductVersionLS = 00000000
dwFileFlagsMask = 00000017
dwFileFlags = 00000000
dwFileOS = 00000004
dwFileType = 00000001
dwFileSubtype = 00000000
dwFileDateMS = 00000000
dwFileDateLS = 00000000
productVersionStr = 1.5.23.0
version = 0001000500170000
product name = TESV: Skyrim
steam exe
dll = D:\Steam\steamapps\Common\Skyrim Special Edition\\skse64_1_5_23.dll

 

 

 

If Steam Client is already running, then a further log is created ..

 

SKSE64.log

 

 

SKSE64 runtime: initialize (version = 2.0.6 01050170 01D393DEDB955FA2, os = 6.2 (9200))
imagebase = 00007FF63E540000
reloc mgr imagebase = 00007FF63E540000
config path = D:\Steam\steamapps\Common\Skyrim Special Edition\Data\SKSE\skse.ini
plugin directory = D:\Steam\steamapps\Common\Skyrim Special Edition\Data\SKSE\Plugins\
checking plugin D:\Steam\steamapps\Common\Skyrim Special Edition\Data\SKSE\Plugins\\PapyrusUtil.dll
plugin D:\Steam\steamapps\Common\Skyrim Special Edition\Data\SKSE\Plugins\\PapyrusUtil.dll (00000001 papyrusutil plugin 00000001) loaded correctly
dispatch message (0) to plugin listeners
no listeners registered
dispatch message (1) to plugin listeners
no listeners registered
init complete
hooked dinput
dispatch message (6) to plugin listeners
no listeners registered
Reading translations from Interface\Translations\Run For Your Lives_ENGLISH.txt...
dispatch message ( :cool: to plugin listeners
no listeners registered
save name is Save135_447A163A_1_5068616964_Tamriel_020230_20180122204116_29_1
full save path: D:\Documents\My Games\Skyrim Special Edition\Saves\\Save135_447A163A_1_5068616964_Tamriel_020230_20180122204116_29_1.skse
dispatch message (2) to plugin listeners
no listeners registered
loading co-save
Loading mod list:
(0 -> 0) Skyrim.esm
(1 -> 1) Update.esm
(2 -> 2) Dawnguard.esm
(3 -> 3) HearthFires.esm
(4 -> 4) Dragonborn.esm
(5 -> 5) Unofficial Skyrim Special Edition Patch.esp
(6 -> 6) Skyrim Project Optimization - Full Version.esm
(7 -> 7) DynDOLOD.esm
(8 -> :cool: RelightingSkyrim_SSE.esp
(9 -> 9) Ars Metallica.esp
(10 -> 10) Smilodon - Combat of Skyrim.esp
(11 -> 11) Audio Overhaul Skyrim.esp
(12 -> 12) SimplyBiggerTreesSE.esp
(13 -> 13) Run For Your Lives.esp
(14 -> 14) Inigo.esp
(15 -> 15) Keld-Nar.esp
(16 -> 16) Bashed Patch, 0.esp
(17 -> 17) DynDOLOD.esp
Loading light mod list:
Loading menu open/close event registrations...
Loading key input event registrations...
Loading control input event registrations...
Loading mod callback event registrations...
Loading crosshair ref event registrations...
Loading camera event registrations...
Loading actor action event registrations...
Loading NiNode update event registrations...
Loading SKSEPersistentObjectStorage data...
Loading SKSEDelayFunctorManager data...
dispatch message (3) to plugin listeners
no listeners registered
cleared save path

But if the steam client is not already running then this third log does not get created
And, the SKSE64_Steam_Loader.log when there is no Steam Client pre-loaded, looks like this ..
skse64 loader 02000060 (steam) 01D393E0D09049AC 6.2 (9200)
loader base addr = 00007FFC7D590000
exe base addr = 00007FF63E540000
found iat at 00007FF63FA62898
original thunk 00007FFC8D2B1000
patched iat
Edited by Guest
Link to comment
Share on other sites

Xtended Loot and Lood and Degradation mods both are able to spawn/create gear that is enchanted and distribute it to enemies. BUT when enchanting gear worn by the enemy from the start, it ALWAYS fails. The gear gets the name, but no enchant or effect.

Anyone know what this is about? (Xtended loot includes the uncomplied scripts in its download so anyone that want to check it out can do it!)

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...