Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
I would tend to think that there is something else that is causing the crash.
But can we stay on topic plz?
Two questions:
1 = Is the load order posted your complete load order, and did you sort it with LOOT?
2 = Have you tried knocking out the Jarl's quest? I know you said you have the patch and the patch is supposed to block that location for radiant quests, but I'm wondering if maybe the patch glitched on you for some reason.
Well that's not counting stuff like Skyrim.esm, Update.esm, Hearthfire.esm etc. I've also got them sorted differently on the left and right in Mod Organizer; the load order.txt says:
As for the Jarl's quest, I had done that quest earlier but it sent me to a barrow somewhere around the northern coast. I also once tried getting the quest again and using the console (Though I don't remember where I was in the quest chain when I did it) to instantly complete it to no avail.
Hmm, that is strange though, according to UESP the unofficial patch was supposed to stop it from becoming repeatable. Maybe I'll try fiddling with that again.
*EDIT*
Tried again, no luck. Finishing the helm quest again changes nothing.
Although I'm annoyed that they closed my ticket at AFKTrack before I could ask for more help, I managed to figure it out on my own. It seems the quest was starting for them for some reason, which meant it was either a mod or something else on my end.
Remember that Netimmerse Override problem I mentioned earlier? Well before I figured out THAT culprit, one of my attempts to fix it involved cleaning the files with TESV Edit. I restored the original update.esm and now the quest starts properly. I wonder if I should just restore the original .esms for the 3 addons while I'm at it...