Creation Kit not loading through MO2 for Skyrim ae 1.6.1170

[Starlight64]

When I try and open creation kit  through Mod Organizer 2 it only loads so far and then says that it is unresponsive. I have tried changing the steamappid which I am confused which one that is for creation kit 2.0 and skyrim ae 1.6.1170. I also tried redownloading it through steam and nothing. Another thing I tried is a mod called CreationKit Platform Extended and the same result nothing. 

[traison]

9 hours ago, Starlight64 said:

I have tried changing the steamappid which I am confused which one that is for creation kit 2.0

 

Its probably the one that it was set to by Steam. I don't see why you'd change it, unless you got your copy from somewhere else. Also the number is publicly available so there shouldn't be any confusion here - legal copy or not.

 

10 hours ago, Starlight64 said:

Mod Organizer 2 it only loads so far...

 

Loads what? A plugin? And how far is far?

 

10 hours ago, Starlight64 said:

...and then says that it is unresponsive.

 

That's most likely Windows telling you its unresponsive, not the CK. That's as far as I know only based on the window message pump not responding in time; which could just mean the app was made incorrectly, and is too busy to process messages in the wndproc. Another way of putting that is to say: How long did you wait? Are you sure it doesn't resolve itself in... say 5 mins?

 

10 hours ago, Starlight64 said:

I tried is a mod called CreationKit Platform Extended and the same result nothing.

 

Does it still pop up a 2nd window with the title "Log" showing console/debug output? Did you read through that?

 

And speaking of logs, how about:

...\Skyrim Special Edition\BugFixesSSE.log

...\Skyrim Special Edition\Logs\Script\EditorPapyrus.0.log

...\Skyrim Special Edition\Logs\Script\EditorPapyrus.1.log

...\Skyrim Special Edition\Logs\Script\EditorPapyrus.2.log

...\Skyrim Special Edition\Logs\Script\EditorPapyrus.3.log

...\Skyrim Special Edition\d3dx9_42.log (SKSE)

 

And speaking of SKSE, how about plugin loader logs? SKSE, PluginPreloader, ENB, ReShade, and whatever else there might be?

 

[Starlight64]

8 hours ago, traison said:

 

Its probably the one that it was set to by Steam. I don't see why you'd change it, unless you got your copy from somewhere else. Also the number is publicly available so there shouldn't be any confusion here - legal copy or not.

 

 

Loads what? A plugin? And how far is far?

 

 

That's most likely Windows telling you its unresponsive, not the CK. That's as far as I know only based on the window message pump not responding in time; which could just mean the app was made incorrectly, and is too busy to process messages in the wndproc. Another way of putting that is to say: How long did you wait? Are you sure it doesn't resolve itself in... say 5 mins?

 

 

Does it still pop up a 2nd window with the title "Log" showing console/debug output? Did you read through that?

 

And speaking of logs, how about:

...\Skyrim Special Edition\BugFixesSSE.log

...\Skyrim Special Edition\Logs\Script\EditorPapyrus.0.log

...\Skyrim Special Edition\Logs\Script\EditorPapyrus.1.log

...\Skyrim Special Edition\Logs\Script\EditorPapyrus.2.log

...\Skyrim Special Edition\Logs\Script\EditorPapyrus.3.log

...\Skyrim Special Edition\d3dx9_42.log (SKSE)

 

And speaking of SKSE, how about plugin loader logs? SKSE, PluginPreloader, ENB, ReShade, and whatever else there might be?

 

I downloaded creation kit from steam. And yes I looked at the log, it loads most of the bsa's , the creation kit addons and then stops at the resource pack.

[traison]

6 minutes ago, Starlight64 said:

it loads most of the bsa's , the creation kit addons and then stops at the resource pack.

 

In this case I'd use Process Monitor from Sysinternals (Microsoft) and compare the files accessed by the CreationKit.exe to the log you're looking at. If it stops after opening another file after the resouce pack, then that file is likely to be related.

Edited December 25, 2024 by traison

[Starlight64]

26 minutes ago, traison said:

 

In this case I'd use Process Monitor from Sysinternals (Microsoft) and compare the files accessed by the CreationKit.exe to the log you're looking at. If it stops after opening another file after the resouce pack, then that file is likely to be related.

Ok I did that I found 4 realated creation kit files

[Starlight64]

On 12/25/2024 at 11:04 AM, traison said:

 

In this case I'd use Process Monitor from Sysinternals (Microsoft) and compare the files accessed by the CreationKit.exe to the log you're looking at. If it stops after opening another file after the resouce pack, then that file is likely to be related.

I did wait for 15 minutes and still the same thing