Jump to content

Removed SKSE due to crashes but Vortex continues to try using it


UrDollyAssasSIN

Recommended Posts

One piece of advice I do my best to give to everyone is to manually install SKSE, or any script extender. This way you don't have problems with any script extender.

Link to comment
Share on other sites

Thank you for everyone's good faith efforts to help us with running Skyrim SE directly with SKSE64 not through the Vortex dashboard.

 

We placed a shortcut to start Skyrim SE with SKSE on our desktop, and ran the game and had our first-ever CTD, after about 7 minutes of gameplay.

 

So, we returned to starting the game with running SKSE from the Vortex dashboard and played non-stop, no crashes, for 90 minutes, before quitting.

 

When we first installed Skyrim SE, 2019, and have been playing it through SKSE on the Vortex dashboard, we have not had one CTD, believe it or not, with 46 mods installed.

 

Can someone please explain why we might have crashed after trying SKSE independently? Please note when we first installed SKSE 64, we did it manually, as recommended.

Edited by Gorgopis
Link to comment
Share on other sites

Had you been playing through Vortex at the time the crash may have still happened, and you would be saying, "Ever since I switched to starting SKSE via a shortcut it has never crashed." As the saying goes, "The world may never know." :smile:

 

On a more serious note, in theory, once your configuration is set by Vortex then the \Data folder is set until you change something. IOW, starting with Vortex and starting from a desktop icon produces the same game. If you started with Vortex and it worked, and then you started from the desktop then it should also work. So as long as you didn't change any configuration files (.ini files), make graphics adjustments, etc. then it should be the same.

 

The best, "What just happened?" help you can get with scripts specifically and gaming in general is to install .NET Script Framework at Skyrim Special Edition Nexus - Mods and Community (nexusmods.com) Please note that it has a requirement that must also be installed.

 

It cannot help you with what happened before it was installed, so the crash after playing 7 minutes is water under the bridge. But from the point you install this it will generate a Crash Log in ...\Data\NetScriptFramework\Crash that has useful info. If you can't make heads or tails of its content, usually someone else can help. There is also a general error message guide (it's not a mod) being developed here: .NET Script Framework's Common Crashes and Fixes at Skyrim Special Edition Nexus - Mods and Community (nexusmods.com)

 

The author of .NET Script Framework, meh321, is not an amateur, and the code is solid. The goal has been primarily to overcome Bethesda's shortcomings (possibly the cause of your crash). His mods are generally not going to have a traditional plugin (.esm/.esl/.esp) but are directed at the game engine itself. The following are also highly recommended:

 

Bug Fixes SSE at Skyrim Special Edition Nexus - Mods and Community (nexusmods.com)

Address Library for SKSE Plugins at Skyrim Special Edition Nexus - Mods and Community (nexusmods.com) (Required by other mods/fixes you will want.)

Actor Limit Fix at Skyrim Special Edition Nexus - Mods and Community (nexusmods.com)

SSE Fixes at Skyrim Special Edition Nexus - Mods and Community (nexusmods.com)

 

And a must-have from aers, another non-amateur author:

 

SSE Engine Fixes (skse64 plugin) at Skyrim Special Edition Nexus - Mods and Community (nexusmods.com)

Link to comment
Share on other sites

That's a lot of help, and it is appreciated.

 

We are familiar with many of these listed or similar-to resources, having run Skyrim LE constantly through the SKSE shortcut--and eventually having to investigate many CTD's during our LE experience. We strangely liked seeing the crash log with LE, especially since it showed so many broken references.

 

For what it's worth, in "good scientific fashion," we decided to re-create our CTD. And we did. We started Skyrim SE with the SKSE 64 launcher, loaded the same save that led to the first CTD, and traveled to Anise's cabin, where we crashed before, and then to Solstheim, since we didn't crash at the seven-minute mark, in Anise's cabin. This time, well, we crashed at about 11-minute mark. (We were timing since we were aware of the 15-minute crash with certain PC processes.)

 

Next, to continue our test, we tried the SKSE64 run-tool on Vortex, loaded the same save, and just finished about two hours of non-crash playing, after taking the same route, and then doing some prolonged quests on Solstheim.

 

We agree, configuration should be set, and we didn't change anything. So, perhaps Vortex keeps some PC processes aside, whereas starting from the desktop allows some of our PC processes to interfere? We would enjoy understanding this.

Link to comment
Share on other sites

I'm guessing since you were doing this scientifically (avoid changing test conditions) that you did not install .NET Script Framework (and thus do not have a crash log to show for it yet). I don't know of Vortex "intentionally" keeping other processes aside, but who's to say that isn't happening as a result of general Windows 10 background functioning? Vortex is a big "boat" and when it sits in the water, it is going to displace. There are too many variables.

 

It may be that the short-time crash will still happen via the desktop icon once .NET Script Framework is installed and then you will have a crash log through which you may browse. On the other hand, the crash may be caused by a known condition that is fixed by one of the several utilities I suggested. :)

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...