New Vortex User Stumped; "SKSE64 not running"?

[Live2sculpt]

Not my 1st day modding, but it IS my 1st day trying Vortex.

 

I thought Vortex had installed SKSE64 correctly. There are 5 SKSE64 files (dll, exe, txt, dll, txt) present in the game's root folder.

Clicked "Install" click "deploy", etc.

 

Still, I'm greeted with SkyUI Error Code 1 "SKSE is not running".

 

It's been a couple years since I used this stuff. Is this a known error or some kind? Am I forgetting to do something? Have I used Vortex incorrectly?

 

I'm assuming I'm not supposed to manage SKSE64 manually like in the old days, but I just don't know.

 

And I'm far too busy with RL to deal with modding hassles like I once did... the reason why I'm trying out "user friendly" Vortex in the 1st place.

 

I hope this is a simple head-smack "but of course" fix. Thanks in advance for any tips.

[showler]

You might just need to go to your dashboard and click the three liitle dots on the "skyrim script extender" button and choose "make primary".

 

Possibly it is still defaulting to the normal game launch.

[Live2sculpt]

You might just need to go to your dashboard and click the three liitle dots on the "skyrim script extender" button and choose "make primary".

 

Possibly it is still defaulting to the normal game launch.

Thanks.

 

But the mousover to "Make primary" currently reads "not configured". It is gtreyed out.

 

Smells like a noob user error to me.

[HeyYou]

Install SKSE manually. (directions in the archive you downloaded.) The mod managers don't always do a good job of it.

 

You also need to start the game with SKSE_loader. You should be able to convince Vortex to use that as the default.....

[Live2sculpt]

Install SKSE manually. (directions in the archive you downloaded.) The mod managers don't always do a good job of it.

 

You also need to start the game with SKSE_loader. You should be able to convince Vortex to use that as the default.....

OK. I assumed that maybe Vortex knew how to manage the SKSE files automaticaly.

 

IMO it should not even pretend to auto-manage the SKSE install if it's not 100%.

 

Manual install of SKSE is old hat. But how exactly does one instruct Vortex to open using the loader.dll?

[Live2sculpt]

When I first started up Vortex, it was giving me guff warnings about my running it via my Administrator profile (first time I ever saw something like that).

So, JIC my problems somehow stem from installing SKSE while in that state, I'm going to back up, change my profile to user, reinstall the game, manually install SKSE64, then reinstall Vortex, and try modding again.

 

Are there any other things I might be better off installing manually rather than letting Vortex manage it? Like Papyrus perhaps?

 

TBH, I'm not filled with confidence about Vortex now. I was prepared for a simpler "User friendly" program. Me being better off installing SKSE manually first isn't a good start.

Edited December 25, 2021 by Live2sculpt

[showler]

Vortex has zero issues installing SKSE. All you need to do is drop the file on the "drop files here" block at the bottom of your mod tab, then allow it to complete the install and enable.

 

If you are having problems with SKSE it is not due to an install problem with Vortex.

 

The administrator thing is weird. You don't have Skyrim installed in your Program folder do you? You should never install a game you intend to mod in a folder protected by Windows.

 

Also, check in your settings to see if Vortex has any warnings regarding mod deployment. Maybe you didn't set things up completely?

[anjenthedog]

What I think HeyYou meant is that before the SKSEloader will work properly, you'll need to start skyrim the first time using the vanilla loader. It's part of the process of "getting started"

 

I won't tell you what to do, (each to his/her own), but I'd suggest that you give vortex a chance. Once you get over the initial hump, it should become clear why many of us chose it.

 

When I install a mod, the process is this simple...With Vortex Open

1) download-install via nexus downloader/installer OR manually install from a locally saved archive (first button on left side of orange menu bar in mod tab view)

2) answer "yes" when vortex asks "Install mod?"

3) answer "yes" when vortex asks "Enable mod?"

4) answer "yes" when vortex asks "Deploy mod?"

 

Unless there's a lingering mod contention, vortex will handle everything else in the background, including both Loot operation an FNIS (not sure about the nemesis engine yet). (note I have FNIs to operate in the background during mod installation processing. by default it's visible so a new user can get acquainted and check the boxes he or she needs and following the processing, etc. I've been doing this so long that I'm confident it'll do its job virtually every time (haven't had an issue with FNIS in background mode for ~ 200 mod installations, but again, for a newb, probably best to keep it foreground for a while.)

 

If there is some lingering mod contention, vortex will notify you and eventually ask you to pick the resolution (load this new mod before, or after the mod(s) which are causing the contention). And nine times out of ten, (actually ,much better odds in my experience) vortex recommends the right solution, you just have to pick it. The only thing you have to avoid when resolving mod contentions is creating a "Cycle" where a series of load orders results in a loop condition (A loads before B, B loads before C, C loads before A)

[Live2sculpt]

Thanks good people.

 

Perhaps my problem actually lies in what I'm now learning is a recent tumult of the sudden upgrade to AE, and a popular need to revert to SE. That was unexpected, and I'll look into that too.

 

I had hoped the time I spent away from Skyrim would see Bethesda finally STOP messing with it, and screwing with community modding. But I guess it's still going on.