Jump to content

[LE] Creation Kit crashing after Creating Quest? Compatibility Patch creation


Recommended Posts

((Update: I figured out this was a CK bug that goes as far back as 2012 I just have to save the esp with the empty quest after I name it before I continue editing. I thought I may have been causing the issue myself but apparently not. I wouldn't mind a quick answer to the other questions though.))


I am working on making a compatibility patch between Death Alternative and Undeath and it's "expansions" however every time I attempt to create the quests as outlined in BralorMarr's Thread below I get a crash as soon as I close the quest window.

 

 

  • Am I only supposed to have one ESP open at a time in the creation kit?
  • Is that what causes the crashes?
  • Do I need to or should I add Daymoyl and the USLEEP to Skyrim editor init file like I did for the expansions?
  • My load order when I open the CK looks funny is it okay for it to look like that? Does it matter?

 

What I load in the creation kit in order as it appears in the CK:

 

 

 

Skyrim

Update

Daymoyl

Dragonborn

Hearthfires

Dawnguard

Unofficial Skyrim Legendary Patch

Undeath.esp

da_test.esp

daymoyl_Dawngaurd.esp

Undeath Immersive Lichdom.esp

UndeathClassicalLichdom.esp

UndeathDAPatch.esp (My active file)

 

 

BralorMarr's Intructions:

https://www.nexusmods.com/skyrim/mods/45894/?tab=forum&topic_id=1557443

 

Undeath and the Expansions I have open in the creation kit with DA

 

https://www.nexusmods.com/skyrim/mods/40607

https://www.nexusmods.com/skyrim/mods/60783

https://www.nexusmods.com/skyrim/mods/84937

 

Screenshots of what I did or was trying to do before the crash happens. As soon as I close those Quest windows the creation kit crashes. Am I doing something wrong? Causing the crash to happen myself?

 

516258-1531541797.png

 

516258-1531541717.png

Link to comment
Share on other sites

  • 1 year later...

The kit doesn't have bugs.. It has policy & procedures.... You need to follow them.

 

That is quite possibly the dumbest excuse for a piece of software to crash I've ever seen in my life. Undefined behavior that causes the software to close abruptly isn't "policy & procedures." It's called bad software design. If this way of creating a quest truly is required then the developers of CK should have implemented that into CK.. not allow the software to crash because of some random software constraint that isn't enforced in the software.

Link to comment
Share on other sites

  • Recently Browsing   0 members

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