JediStudley Posted December 9, 2018 Share Posted December 9, 2018 After updating to the latest creation kit 1.5.3 and Skyrim SE 1.5.62, the CK crashes everytime I edit a new quest and press ok on the dialog. I've done this with the sample quest from the tutorials. I've used the CK to look into stuff before and didn't have this crash problem. I have a good machine with 16GB of memory using windows10 64 bit. Is anyone else having this problem or know what I can do to fix it? Link to comment Share on other sites More sharing options...
Lerigonith Posted December 9, 2018 Share Posted December 9, 2018 I've had the same trouble and honestly the only workaround I've found is to just edit dialogue using the 'player dialogue' tab instead. Some people have suggested running CK as an administrator, but still every other dialogue view I create causes a ctd ¯\_(ツ)_/¯ The other option would be to make your mod in the Oldrim/32bit CK since it crashes so much less often, then use some tools to convert it to SSE Link to comment Share on other sites More sharing options...
JediStudley Posted December 9, 2018 Author Share Posted December 9, 2018 Thanks for the quick response! Where can I get a copy of Oldrim or the Oldrim 32bit ck? I got into skyrim late and all I have and can find is SSE. Link to comment Share on other sites More sharing options...
Lerigonith Posted December 9, 2018 Share Posted December 9, 2018 I'm not quite sure where you would get it if you only have SSE. But if you have SSE on Steam, then you might be able to go to Library->Tools->"Skyrim Creation Kit" If that doesn't work I'll keep looking for other options Link to comment Share on other sites More sharing options...
JediStudley Posted December 9, 2018 Author Share Posted December 9, 2018 thanks, any help is appreciated. The skyrim creation kit does not show up in the steam tools listing (I only see 85 total). I did purchase SSE off of steam as it was the only option I could find to get it. Thanks again! Link to comment Share on other sites More sharing options...
JediStudley Posted December 9, 2018 Author Share Posted December 9, 2018 (edited) Some success! There are 3 things that made it better for me: (windows10, 16GB RAM) 1) The CK needs full access control.2) The CK seems to need to run in 'compatibility mode'3) The CK is...sensitive to fix 1&2, login as admin and open the properties dialog in the CreationKit executable. Put it in "Windows 8" compatibility mode (I verified this with the Win10 compatibility trouble shooter). Also select the toggle so it runs with admin privileges. to fix 3. I was working on the example demo script which uses a quest object (see Papyrus for Beginners). What caused the problem 100% of the time was to edit the basic quest info (1st tab), add the demo script, and then press ok to commit the change. I still had the problem of CTD after fixing 1&2 doing this (but still recommend the change since the trouble shooter found problems). The trick is to enter the quest info on the first tab *and then press OK*. THEN reopen the quest and associate your script with it, pressing OK again when done. Now i'm able to save the quest to a new test.esp! I'm still working out the quirks of Papyrus and the CK, but at least now I'm on my way again and I hope this is helpful to anyone reading this!(btw, I've even had the CK and SSE running at the same time :-) ) Edited December 9, 2018 by JediStudley Link to comment Share on other sites More sharing options...
cridus Posted October 20, 2020 Share Posted October 20, 2020 (edited) Some success! There are 3 things that made it better for me: (windows10, 16GB RAM) 1) The CK needs full access control.2) The CK seems to need to run in 'compatibility mode'3) The CK is...sensitive to fix 1&2, login as admin and open the properties dialog in the CreationKit executable. Put it in "Windows 8" compatibility mode (I verified this with the Win10 compatibility trouble shooter). Also select the toggle so it runs with admin privileges. to fix 3. I was working on the example demo script which uses a quest object (see Papyrus for Beginners). What caused the problem 100% of the time was to edit the basic quest info (1st tab), add the demo script, and then press ok to commit the change. I still had the problem of CTD after fixing 1&2 doing this (but still recommend the change since the trouble shooter found problems). The trick is to enter the quest info on the first tab *and then press OK*. THEN reopen the quest and associate your script with it, pressing OK again when done. Now i'm able to save the quest to a new test.esp! I'm still working out the quirks of Papyrus and the CK, but at least now I'm on my way again and I hope this is helpful to anyone reading this!(btw, I've even had the CK and SSE running at the same time :-) ) I'm super late but thank you for this. I got a crash doing that exact same thing, creating a quest and adding a script before pressing "ok" for the first time. P.S. The creation kit wouldn't open if set to run as an admin. Odd. Edited October 20, 2020 by cridus Link to comment Share on other sites More sharing options...
Recommended Posts